[Zope3-dev] UI effort at Sprintathon

[Janko Hauser]

Thanks Joachim for this writeup, and the goals are worth it. Some
comments on this in the context of further development. I tried to start
working on this also, see a thread some weeks before, and I will follow
up to this. The most stumbling block was a description what a site
designer should do, and how this can be made simpler. In the things I
wrote up, most actions where done by the site-developer, after a
suggestion from Jim I added the InformationArchitect actor. 

In the things you wrote on the wiki, there was a complete mix of site
managment, CMS managment and templating for actual
website-presentations. In the search for the silver bullet, I thought
about a technic to 'make' interfaces for these three fields with one
logic model. And I do not believe that the PHP people have this model .
What we see there, are great UI for a CMS. No UI for TTW component
creation, no UI for the ZODB, no UI for application server managment.
And the also have not solved the problem of reusabilty

After some more discussion I got the impression, that we need to have
different layers, where each layer can have it's own logic model. With
logic model I mean for example the difference between component-,
content-object-, content-type-centric views. These different models
'can' build on each others technics, but they do not need to. For
example the schema technics can probably be reused. So perhaps it would
be good to define first these layers, although this might look
'academic' :-).

Your critic, that the Z2 managment views can not be reused is right. But
do we really want to reuse the managment views for a CMS, I think not.
What we want is to reuse some of the functionality, not the view itself.
And this functionality should be reusable in different logic models.

I can not make suggestions, what should be done during the sprint, but
from the last announcements, it seems to me that the first mentioned
focus on CMS is bluring towards general Z3 issues.

I will come back to the usecases later.

__Jank