Thank you for your reply.
In fact, I am working on an intranet frontend.
Some of the demands are:
modularisation for the creation of several distributions
(overloading/fallback strategies)
flexible storyboard, including a wizard-template structure
and active, personalized context help
internationalization (all text elements encapsulated)
skins (skin definition files are used to create css, buttons, etc.)
personalized preferences
application-like functionality (without javascript)
synchonization with backend server processes (actions, status etc.)
integration of freely availabe PHP packages
version control (I use CVS)
structured documentation (I use POD)
Though I managed most of these, I feel the need for having a
structured map of the whole system, to not be personally chained
to the coding. A central document containing all script interfaces and
dependencies, think of it as an engine.
Things are going more and more complex. The only way to handle this
abstraction.
Anyone?
Daniel Hopp