skip to main content

kiesler.at
FutureOfPhpWebSite
Back to Page | Back to History

Difference between revisions

Version 5, 2005-04-06 22:49 Version 6, 2005-04-06 23:52
Lines 31 - 37 Lines 31 - 37
   
Developing new modules is a tendious task. For the most basic functions, like showing tabular data in lists, there are a lot of different APIs that are incompatible to each other. You want to do a html-form? Choose one of three different approaches. The not-yet-scheduled 1.0 release of phpWebSite will be incompatible to the current apis but have a compatibility layer. Developing new modules is a tendious task. For the most basic functions, like showing tabular data in lists, there are a lot of different APIs that are incompatible to each other. You want to do a html-form? Choose one of three different approaches. The not-yet-scheduled 1.0 release of phpWebSite will be incompatible to the current apis but have a compatibility layer.
   
The APIs is not final, so technically speaking phpWebSite is still Alpha (not even Beta) -- far away from a productive release. Am I unpatient? Maybe. The APIs is not final, so technically speaking phpWebSite is still Alpha (not even Beta) -- far away from a productive release. Am I impatient? Maybe.
   
Fact is, no API means a discouraging of module developement. And applications are -- in a similar manner like ease of use -- what most people want to use software for. Fact is, no API means a discouraging of module developement. And applications are -- in a similar manner like ease of use -- what most people want to use software for.
   
Lines 64 - 66 Lines 64 - 72
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. 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. No need to reinvent the wheel all over again.
   
  +++ Development and the End User
   
  Remembering first that this should be designed with the technically challenged at best. The staff assistant. The department head. The person that needs content displayed on the web, but has no web design or html skills. So it needs to be intuitive. Users assigned to groups. Categories assigned to groups. Groups restricted to the categories assigned to them. Menus associated with groups. etc. etc.
   
  Development should always keep the end user in mind. Sometimes it is better to take a few steps back to see the larger picture. Since 9.2, there han't been a major change in the way content has been handled. (It could be even longer, but I started with 9.2.) Many of the management questions seen in forums about phpWebsite deal with the lack of intuitiveness concerning menus, categories, blocks etc. This results not in new modules being developed, but rather hacking existing modules to make them more intuitive not only to the content editor/manager, but to the viewer of the site.