If you make the call generic, then it is contingent upon the developer to
supply the correct information.
In our case we are using the virtualdocumentroot Apache method to
dynamically allocate virtual hosts....by parsing the requested file (with
full path) we know the NAME of what we call an orbit, so we have our HOST
name and can look that up to get the ID. We also know that the orbit (or
host) will either have the default style "orbits" or a child style based
upon the style "orbits" that we track. A far as the rest of the information
(author, auth, user, admin) we can get those easily. The only thing I'm
confused about is argv and argc....are you passing data after the "?" via
these parameters?
As far as the page is concerned, we can create a generic page that basically
has nothing in it but the include statement to get the external HTML (as
discussed previously).
I REALLY think that this would give midgard a level of interoperability that
would help make it into a premier CMS, without having to digress into
developing WYSIWYG tools (which everyone uses to some degree).
As I said earlier, the biggest benefit that we have seen in using Midgard is
the management, reusability, and inheritance issues.
We have developed a core of hundreds of routines under one style, but can
quickly create a child style and only recode/redefine the elements which
need to be changed to accomodat the needs of the new site.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
