Re: [Zope3-Users] Simple Acquisition
On 2/4/06, David Johnson <[EMAIL PROTECTED]> wrote: > If I understand correctly, a non-technical web designer would not be able to > do much design work with Zope 3 unless they understand how to program > interfaces also or they would have to design the old-fashioned way by > creating a separate page for each item/folder they want to display? A web application platform is not something you design "with". Teaching the web designer interfaces an python probably does not help, you still can't design it "with" Zope 3. You design *for* Zope 3, which is an altogether different issue. Zope 2 was a way to create web sites, that was too good at it and got used as an application server instead. Zope 3 is an application server. http://blogs.nuxeo.com/sections/blogs/lennart_regebro/2005_10_04_zope2-vs-zope3-faq ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Simple Acquisition
On Saturday 04 February 2006 15:46, ksmith99 (sent by Nabble.com) wrote: > I believe after Zope2, acquisition was determined to be more of a liability > than a feature, as such, it doesn't exist in Zope3. TTW skin development is > not supported at this time and has moved to the filesystem. From the > filesystem with a little zcml you can create much richer and easier to > follow behavior. I'll add that some of the WebDev work we did this week will allow simple skin development via the Web. But other than that development, you have to know some minimal programming. Now that the Plone community is interested in Zope 3 , we will have to do more for the designer, so I expect improvements will come in the next releases. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
RE: [Zope3-Users] Simple Acquisition
> Repeat after me: "Zope 3 is not a replacement for Zope 2." Yes, I think that's my problem. I will be patient and contribute as much as I can; overall it's definitely worth it. ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Simple Acquisition
I believe after Zope2, acquisition was determined to be more of a liability than a feature, as such, it doesn't exist in Zope3. TTW skin development is not supported at this time and has moved to the filesystem. From the filesystem with a little zcml you can create much richer and easier to follow behavior. Look for the skin development section of Stephan and/or Phillip's book Kevin Smith View this message in context: Re: Simple Acquisition Sent from the Zope3 - users forum at Nabble.com. ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Simple Acquisition
В Сбт, 04/02/2006 в 21:01 +0100, Jean-Marc Orliaguet пишет: > > David Johnson wrote: > > >>>I have created a ZPT Page which I have no trouble accessing: > >>> > >>>http://localhost/index.html > >>> > >>> > >>> > >>>However, if I try to access it from the following URL, I see the > >>>contents of MyFolder instead of the index.html. > >>> > >>>http://localhost/MyFolder/index.html > >>> > >>>What is the proper way to acquire "index.html" in other contexts? > >>> you can overwrite traverse-behavior for 'your folders': write simple Traverse-adapter for you folders. What is 'your folders'? It's folders implements 'IMyAcquisitionBehavior'. This adapter will has 'traverse'-method. example(only idea): class MyAcquisitionTraverse: __used_for__ = myproduct.interfaces.IMyAcquisitionBehavior def traverse(self, name): my_folder = self.context parent_folder = my_folder.__parent__ return zapi.traverse(parent_folder, name) ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Simple Acquisition
David Johnson wrote: I have created a ZPT Page which I have no trouble accessing: http://localhost/index.html However, if I try to access it from the following URL, I see the contents of MyFolder instead of the index.html. http://localhost/MyFolder/index.html What is the proper way to acquire "index.html" in other contexts? Zope 3 dropped implicit acquisition. You could write a traverser that did this trick, I suppose. The standard "Zope 3" way is to define the views explicitly, though: connecting them through interfaces does everything I've wanted in this regard, but YMMV. If I understand correctly, a non-technical web designer would not be able to do much design work with Zope 3 unless they understand how to program interfaces also or they would have to design the old-fashioned way by creating a separate page for each item/folder they want to display? you can specify "*" as an interface, then you don't have to write an interface. /JM /JM ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
RE: [Zope3-Users] Simple Acquisition
> > I have created a ZPT Page which I have no trouble accessing: > > > > http://localhost/index.html > > > > > > > > However, if I try to access it from the following URL, I see the > > contents of MyFolder instead of the index.html. > > > > http://localhost/MyFolder/index.html > > > > What is the proper way to acquire "index.html" in other contexts? > Zope 3 dropped implicit acquisition. You could write a traverser > that did this trick, I suppose. The standard "Zope 3" way is to > define the views explicitly, though: connecting them through > interfaces does everything I've wanted in this regard, but YMMV. If I understand correctly, a non-technical web designer would not be able to do much design work with Zope 3 unless they understand how to program interfaces also or they would have to design the old-fashioned way by creating a separate page for each item/folder they want to display? ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
