AOrbit is a multiuser Virtual Hosting system...customer capabilities are
diverse.
What AOrbit brings is a standard set of tools (php code) that the users of
any capability can use. For novice users they can use our interface to use
predefined styles and insert pages one at a time. But for sophisticated
users, they will want to create complex sites and still use the AOrbit
tools.
Any WYSIWYG HTML development suite develops WHOLE pages, not "styles". With
a lack of a WYSIWYG style developer in Midgard...we have to allow an
integration mechanism between complex development suite created pages, and
midgard "style" generated pages.
I really believe in Midgard and have a around 1000 pages, as well as that
many or more elements created in it. But, if the only way that we can use
midgard elements and functionality is if the page resides in the DB then we
are hosed because nobody except geeks code HTML by hand any more. (I'm one
of the geeks).
I'm contemplating some sort of "import utility" which will take a site
uploaded by a customer and programmatically import each page into midgard.
But what a "pain". I still maintain that a mgd_create_midgard() routine
that would set up the midgard environment for an external page is the better
solution. As I said in my previous emails, we do know the host, style, etc.
for the page being called.....the page is just not in the midgard DB.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
