skip to main content

kiesler.at
FutureOfPhpWebSite
Back to Page | Back to History

Difference between revisions

Version 2, 2005-04-06 22:31 Version 3, 2005-04-06 22:38
Lines 46 - 48 Lines 46 - 66
Not hacked ones like seen all over phpWebSite which implement centralized features all over again. Not hacked ones like seen all over phpWebSite which implement centralized features all over again.
   
   
   
  ++ Module developement guidelines
   
  It would be great, if modules would APIs themselves. With callbacks. One could then extend modules very easily and recycle their methods. Take for example "Add one entry to calendar", "Store one photo into the photoalbum" or "Resize one photo to a certain size".
   
  Right now, it is impossible to reuse these methods. The code is very confusing, again, there is no way of accessing these methods outside the module itself.
   
  It would be great to have some kind of developer forum. One that is not only open to geeks like Sourceforge. But more a classic web forum that would also encourage hobby-developers to write modules. Again: The more modules, the more flexible, the more people will find useful modules.
   
  How about for example webmail, webalizer for phpWebSite, phpmyadmin for phpWebSite, phpldapadmin for phpWebSite, and so on.
   
  +++ Central Method repository
   
  Such APIs could be maintained from a central instance dedicated to doing so. One would enter "photo" and get all the APIs providing photo-methods in return.
   
  Including photo-uploads to a forum, for example, would be as easy as a single method call. As soon as the photo-upload in photoalbums would be improved, the forum-photo-upload would be improved as well.
   
  No need to reinvent the wheel all over again.