[Zope3-dev] Re: New Software Space UI

[Tres Seaver]

Paul Everitt wrote:
> Jim Fulton wrote:
> 
>> Jadran Prodan wrote:
>>
>>> Stephan Richter wrote:
>>>
>>
>> ....
>>
>>> I know that some of those user roles were described on this list 
>>> before but I think that we need a SF document about Zope3 UI.
>>>
>>> I'm using/developing for Zope 2.X and have some understanding of have 
>>> different users use it. But I don't have much of Zope3 zen 
>>> (interfaces, adapters, utilities, views etc.) anyway I like to help 
>>> to produce such SF documentation.
>>
>>
>>
>> Great!
>>
>> I agree 100% that Sci-Fi would be the *best* next step.  I meant to
>> mention that in my other responses on this thread.
>>
>> For example, a short story on "Configuring your Site" would be a great
>> place to start.
> 
> 
> This is the main place I ran into trouble after EuroPython in Sweden:
> 
> 1) What does "Site" mean, outside of CMS?

Heh, a site is the thing a SiteManager configures ;), i.e., a "policy 
zone" whose settings control objects published at URLs "under" the site. 
  It is a likely target of a virtual hosting directive.

> 2) Does it matter?  We could focus our discussion on CMS use cases, 
> since that's 90% of our collective experience.

I would disagree somewhat.  A CMF site has relevance even outside "pure" 
CMS applications (it is the paradigm from which all this started any 
way), as a container of local tools / utilities and configuration.

>  Alternatively, someone 
> could describe a non-CMS usage of Zope 3 that they deployed (for Zope 2 
> or Zope 3).
> 
> 3) If we start by saying "Site" == "CMS Site", does that mean this 
> machinery should be adjacent to Zope 3, but not *in* Zope 3 (since Zope 
> 3 wants badly to be not-limited-to-CMS)?

In Zopd3 terms, a "Site" is already pretty well understood (I thought).

> I apologize for these rather basic questions, but I have a hard time 
> getting my mind focused on the small pile, rather than lost in the big 
> pile of use cases.
> 
> After that, I guess my big question is reflected in the back-and-forth 
> on this thread: which actor are we talking about first?  I propose that 
> we exclude the conversation to Site Manager doing configuration, not 
> development.  I think this is Jim's position as well.  (Spoken as the 
> guy who spent time thinking about a TTW type-builder, alas.)

+1 on that.  It is likely that the TTWDeveloper's "workspace" will be 
"adjacent" to the SiteManager's "policy zone", but not identical.

Tres.
-- 
===============================================================
Tres Seaver                                tseaver at zope.com
Zope Corporation      "Zope Dealers"       http://www.zope.com