On Thu, 20 Apr 2000, Jean-Pierre Arneodo wrote:
> My mental image of a Content Developer view of his site/host/content
> is similar to an IDE for the tree section, (in a seperate frame), editor
> windows, and a browser window to view editing. Also, when an object in
> the tree window is moused over or clicked on once, it shows all the
> attributes i.e. static page, dynamic script source, creation date,
> retirement date, creator, etc. Elements of the content could be accessed
> via the tree, via the style view, by database view sorted by whatever
> including permisisions.
> Does Midgard do all this?
Does Midgard do all this: no. _Can_ Midgard do all this: yes.
Midgard is intself much like the X credo: mechanism, not policy. All the
plumbing is here to make your very own content management system. One
comes with the package in the form of the admin site, but as far as the
Midgard core is concerned it's just another Midgard application.
> I couldn't find a way on the demo to get
> to the tree. Honestly, I'd like the demo to have an easy link to a page
> like Microsoft Interdev,or VC++ with the tree showing immediately on the
> left and two windows opening immediately, the code and the browser view,
> or all browser views that are resident on the local environment.
I would like this too. But I don't think this is a good match for an
http/html based interface: the controls available are primitive, and the
statelessness is a performance killer.
Once the xml-rpc interface, or a similar access method, allows
fine-grained access to the core data structures, it'd be a great project
to build what you describe above as a standalone application. Or a Java
applet.
Emile
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
