AW: AW: [Zope3-dev] role (contextual) services?l

[Roger ineichen]

Mit freundlichen Grüssen
Roger Ineichen
_____________________________
END OF MESSAGE 

> -----Ursprüngliche Nachricht-----
> Von: Stephan Richter [mailto:srichter at cosmos.phy.tufts.edu] 
> Gesendet: Sonntag, 4. April 2004 18:55
> An: zope3-dev at zope.org; dev at projekt01.ch
> Betreff: Re: AW: [Zope3-dev] role (contextual) services?l
> 
> 
> On Sunday 04 April 2004 10:47, Roger ineichen wrote:
> > Our idea: A instance is just a location and is persistent. 
> The models 
> > in this instance can be easy replaced and enhanced. We can 
> provide old 
> > models and new models at the same time in different context's.
> >
> > This means a customer whould like to have new
> > functions in a content type, but some users of the
> > system whould like to have the old functions provided.
> >
> > Sometimes if the new model and the old model are
> > inconsitent there is a hard way to bring this whishes together and 
> > needs big changes or a new content type which works totaly 
> different.
> 
> I think what you are looking for are TTW adapters and other 
> components.
> 
> You simply create two sites called "new" and "old" and 
> register different 
> components with the same semantics in each site. You would 
> then just need a 
> way to share the data; maybe something like that:
> 
> /root
>   /data
>   /new
>   /old
> 
> BTW, just thinking out loud...

Thanks,
Yes, I think there are many ways to do somthing like we try.

We are looking for a way that give the developers a simply 
api for to work with. That's our reason for to pack this 
into a content type. Otherwise you have a lot to know
about the structure of you components. Our content types should
handle this complexity and abstract this to a usable level where
administrator can define such content types.

Develpers can define/develope models and give this models
to administrators. Then it's up to the administrators how
they fit/model the content types together.

And if this types are defined they work like other Zope3
components. No new concepts on this level.
This allows us to build very, complex content types (splited
in simply models in different context's) which can easy disributed. 
The people can just make instances of such a content type. 
They have nothing more to know about our concept. 
(e.g. Archetypes, just use it)

And we can provide a good api if somebody will develope
parts of a content type, like other models.

I'm looking forward to give a working example. That 
whould make things more concrete for to disscuse.

Regards Roger
 
> 
> Regards,
> Stephan
> -- 
> Stephan Richter
> CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. 
> student) Web2k - Web Software Design, Development and Training
>