[commits] [Wiki] changed: Doc/Dev/NewAppBestPracticesH6

[Wiki Guest]

guest [95.90.223.65]  Wed, 26 Sep 2018 18:22:07 +0000

Modified page: https://wiki.horde.org/Doc/Dev/NewAppBestPracticesH6
New Revision:  3
Change log:  issues with using controllers for basic page display

@@ -16,8 +16,15 @@
  Use horde registry->call API for inter-app, horde-internal calls or  
use callAppMethod?

  Use routes and per-resource/page controllers by default instead of  
actual paths?
  If so, we should provide some example how to go about it
+
+TODO: Horde 5's rampage.php currently cannot handle unauthenticated requests.
+Would be handy both for REST and page controllers (for non-loggedin).  
rpc.php has this. services/ajax.php looks like it has this.
+
+TODO: Substitute for PageOutput:
+The Horde Rampage Controller wants responses as strings or streams in  
the response object, but the handy core PageOutput class echoes  
headers and footers to stdout. A controller should have easy access to  
some substitute solution for header, topbar, sidebar, addscriptfiles,  
footer. The existing PageOutput should not be broken for existing apps.
+

  +++ PHP Namespaces
  Use php namespaces for new libraries and apps?