RE: [Zope3-Users] zalchemy integration
Hi David [...] Hi Roger. This is really interesting. It would be good to see a very small demo of these nice packages you have been contributing - something that would put together the minimal layer, menu package, and a few basic viewlets just to give folks a basic idea of what can be acheived 'minimally'. Also a clearer understanding of where to use trusted over the basic layer. I would seem that this is the road to some very dynamic skinning flexibility. That whould be nice, but right now I don't have time for doing such a *how to* sample. Let me know if somebody likes to doing this. Perhaps I can help a little bit. The one thing perhaps missing from this is a mechanism for storing and manipulating viewlets and selecting a template on a container. Perhaps a template manager is also needed. What I am missing from Zope2 is the simple ability to drop an index.html or different template into a folder as a simple way to make folder views that are based on site context. Sites can be pretty terrible otherwise if they are not sensitive to where you are and display the same organization of viewlets. If viewlets/viewlet managers and a template can be maintained as annotations on a container and the weighting of viewlet managers manipulated through a form instead of zcml then we'd be cooking with gas. :-) I agree on that, at least on the functionality. Stephan and I will implement a portlet like concept some time in the future. Such a concept will support to build standalone applications as viewlets with own urls and states etc. This should be enough base for all future concepts where I can think about. Regards Roger Ineichen Regards, David Roger Ineichen wrote: Hi Jeff [...] With the ZMI, I end up asking is this the UI I want to deliver to my customer? And the answer is rarely yes! I feel like I have to arm wrestle a lot more to turn off and hide features. I still don't really understand how the 'Add' menu works. Did you see the layer package I commited to the z3c repos the last days? There is now a minimal layer which allows you to build very easy a own administration interface. This isn't a criticism of the ZMI skin. It just hasn't been a fit for any of our customers or applications, which makes it very hard to support. Fortunately, it's fairly easy to do away with. But it also feels very hard to migrate away from if that's where ones initial work is. We really should use the Boston skin which offers much more flexibility for such customized ZMI's because of it's viewlet/manager concept and drop the Rotterdam skin. [...] Having developed on and for Zope for nearly ten years now, I can say that there is no such thing as traditional zope development :). There are a lot of ways to get things done. ;-) Regards Roger Ineichen _ Projekt01 GmbH -- Jeff Shell ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
RE: [Zope3-Users] z3wingdbg 0.1.0: Wing IDE debugger integration forZope3
Hi Martijn Thanks for that. Sounds really cool. Regards Roger Ineichen _ END OF MESSAGE -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martijn Pieters Sent: Sunday, August 13, 2006 5:32 PM To: zope-announce@zope.org; WingIDE; zope3-users@zope.org Subject: [Zope3-Users] z3wingdbg 0.1.0: Wing IDE debugger integration forZope3 I'm pleased to announce the first alpha release of z3wingdbg, a Zope3 package integrating debug support for the Wing IDE into Zope3. z3wingdbg sets you up with a seperate single-threaded HTTP server through which all requests are under the control of the Wing Debugger. This initial release provides the almost the same functionality as it's Zope2 equivalent. Only accepting connections (have the IDE initialize the connection) has not been implemented. Future releases will include a more user-friendly interface to configuring the package and other server types, such as FTP and SSH. Project homepage (including downloads) http://www.zopatista.com/projects/z3wingdbg Development http://trac.zopatista.com/zopatista/z3wingdbg Subversion Repository https://svn.zopatista.com/zopatista/z3wingdbg http://trac.zopatista.com/zopatista/browser/z3wingdbg Reporting bugs, feature requests http://trac.zopatista.com/zopatista/ Martijn Pieters ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: zalchemy integration
Stephan Richter wrote: Lovely Systems, Roger and I have all been in agreement to publish generic components as we go; if you are subscribed to all check-in messages, you probably saw already a bunch of packages landing in the z3c and lovely namespace. We have tasks setup for this week to open/publish even more packages and extensions. While we are at it, 'lovely' packages do not show up in http://mail.zope.org/pipermail/checkins until now. Michael -- http://zope.org/Members/d2m http://planetzope.org ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: zalchemy integration
On Sunday 13 August 2006 08:35, Philipp von Weitershausen wrote: Yeah, I'm not convinced. At least not by the current Boston skin. I find its code over-structured (subpackages just for the sake of subpackages, it seems). Also, it isn't as flexible as one would think it is. It claims it uses viewlets but it has lots of stuff still hammered into a huge template. I don't find it that much more flexible than Rotterdam. It is a lot more flexible than Rotterdam. It is however constrained by the slots Rotterdam provides, since all the default ZMI views are in reality written for Rotterdam. Roger has developed much more flexible skins that do not conform to Rotterdam slots that have tiny main templates and do everything with viewlets (similar to what Jeff described in his response). 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] Re: zalchemy integration
On Monday 14 August 2006 04:30, Michael Haubenwallner wrote: Stephan Richter wrote: Lovely Systems, Roger and I have all been in agreement to publish generic components as we go; if you are subscribed to all check-in messages, you probably saw already a bunch of packages landing in the z3c and lovely namespace. We have tasks setup for this week to open/publish even more packages and extensions. While we are at it, 'lovely' packages do not show up in http://mail.zope.org/pipermail/checkins until now. Mmh, right. Unfortunately I do not have the permissions to fix this. 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] Re: zalchemy integration
On Monday 14 August 2006 05:27, Philipp von Weitershausen wrote: [EMAIL PROTECTED] gets messages to *all* checkins, no matter which package. THe problem is that you guys aren't subscribed to [EMAIL PROTECTED] so your postings don't show up. Yes, I am. I switched on the day the list was created. 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] Re: zalchemy integration
On Monday 14 August 2006 05:56, Stephan Richter wrote: On Monday 14 August 2006 05:27, Philipp von Weitershausen wrote: [EMAIL PROTECTED] gets messages to *all* checkins, no matter which package. THe problem is that you guys aren't subscribed to [EMAIL PROTECTED] so your postings don't show up. Yes, I am. I switched on the day the list was created. On the other hand, I have been told that my E-mail account is going crazy right now, i.e. rejecting mails. 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[2]: [Zope3-Users] zalchemy integration
Hello Stephan, Monday, August 14, 2006, 12:08:27 PM, you wrote: SR We were on schedule and delivered an application above expectations. SR BTW, I hope I will get a case study out in the next few weeks. Great, I'd love to read that. -- Best regards, Groszer Adam -- Quote of the day: Ah, but a man's reach should exceed his grasp, Or what's a Heaven for? - Robert Browning ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] zalchemy integration
Roger Ineichen wrote: Hi David [...] Hi Roger. This is really interesting. It would be good to see a very small demo of these nice packages you have been contributing - something that would put together the minimal layer, menu package, and a few basic viewlets just to give folks a basic idea of what can be acheived 'minimally'. Also a clearer understanding of where to use trusted over the basic layer. I would seem that this is the road to some very dynamic skinning flexibility. That whould be nice, but right now I don't have time for doing such a *how to* sample. Let me know if somebody likes to doing this. Perhaps I can help a little bit. Hi Roger. I'd be willing to give this a try. Perhaps the Boston skin can be broken into smaller viewlets as a means of providing this howto so that I don't have to create everything. I you are happy with this, I will keep in touch offlist. The one thing perhaps missing from this is a mechanism for storing and manipulating viewlets and selecting a template on a container. Perhaps a template manager is also needed. What I am missing from Zope2 is the simple ability to drop an index.html or different template into a folder as a simple way to make folder views that are based on site context. Sites can be pretty terrible otherwise if they are not sensitive to where you are and display the same organization of viewlets. If viewlets/viewlet managers and a template can be maintained as annotations on a container and the weighting of viewlet managers manipulated through a form instead of zcml then we'd be cooking with gas. :-) I agree on that, at least on the functionality. Stephan and I will implement a portlet like concept some time in the future. Such a concept will support to build standalone applications as viewlets with own urls and states etc. This should be enough base for all future concepts where I can think about. CPSSkins does this from a portlet perspective but its implementation is not yet complete. I not clear of how viewlets fit into CPSSkins at this point as a result. Perhaps this will come to light. I have made crude themes and portlets but have not yet been able to assign the theme/theme page to a path. This will be part of the Site Manager functionality. JM has been away for a bit but I have been following this closely for some time. It can create a theme and a theme page but the css is very tightly integrated into the WYSIWYG interface and auto-generates the css classes and ids. Though it has all sorts of potential, I am much more at home writing and testing stylesheets than going back to my days with Dreamweaver. The autogeneration of classes and ids would make it difficult to style writing your own css in resource files. I'd rather just hang the css on the structures, breaking it only into a small number of files and be done with it. Regards David Regards Roger Ineichen Regards, David Roger Ineichen wrote: Hi Jeff [...] With the ZMI, I end up asking is this the UI I want to deliver to my customer? And the answer is rarely yes! I feel like I have to arm wrestle a lot more to turn off and hide features. I still don't really understand how the 'Add' menu works. Did you see the layer package I commited to the z3c repos the last days? There is now a minimal layer which allows you to build very easy a own administration interface. This isn't a criticism of the ZMI skin. It just hasn't been a fit for any of our customers or applications, which makes it very hard to support. Fortunately, it's fairly easy to do away with. But it also feels very hard to migrate away from if that's where ones initial work is. We really should use the Boston skin which offers much more flexibility for such customized ZMI's because of it's viewlet/manager concept and drop the Rotterdam skin. [...] Having developed on and for Zope for nearly ten years now, I can say that there is no such thing as traditional zope development :). There are a lot of ways to get things done. ;-) Regards Roger Ineichen _ Projekt01 GmbH -- Jeff Shell ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: zalchemy integration
Jeff Shell wrote: 2. There's an 'add to cart' form that is in this page's main template (or other) code, and the user has added something to the cart. The 'update' action of the form adds the item on a post-back. But because it comes *after* the 'cartContents' content provider, the 'cartContents' provider won't show an incremented number until the next stage. We've been calling those update bugs. -- Benji York Senior Software Engineer Zope Corporation ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: Re: [Zope3-Users] Re: zalchemy integration
On 8/14/06, Stephan Richter [EMAIL PROTECTED] wrote: Right, so you fixed the problem with the provider TALES expression, which has to do update()/render() at the same time. My question is: How do you know which content providers are used by a view? Do you manually list them? A Page class (or any provider manager) may optionally list names. The names also provide some ordering support (ensuring that provider A is updated before provider B). If no names are listed in the class, then all Content Providers registered for the page are looked up:: self._content_providers = dict(zapi.getAdapters( (self.context, self.request, self), IContentProvider )) I was thinking about implementing a way to inspect TAL code to determine all the providers that should be looked up before rendering. I even talked to Fred about it already; but it is non-trivial, if I understand him correctly. I wouldn't want to be bound to TAL though. As I mentioned, we use a STAN-inspired system for generating HTML in many places where there's no desire to maintain a separate file just to render something simple - or even moderately complex. As we've also started implementing a system inspired by Rails Helpers which eases some generation of common tasks from formatting to link/URL generation, our need to TAL has decreased. It's still useful in design heavy sites, but I'm really starting to wish for some simplified expressions (even TALES expressions would be nice) to do structured inserts with a helluva-lot-less typing. We still use page templates fairly heavily. I just wouldn't want to depend on TAL code so heavily that any other template/html/xml generation system one wants to plug in really becomes a second or third class citizen at that point. Right, I see you use viewlets/providers heavily; at least we are not the only ones. :-) I would be interested in a lot more dialog here to share best practices and code. We haven't gone into super-heavy usage, but that should start changing this week as we push for the front end UI of this project. Then we'll see if my theories worked :). BTW, another part of the UI power tools is zc.table. I will publish a bunch of extensions later this week. I haven't had too much time to look at `zc.table`. It was a little overwhelming last time I looked at it... I think because of the 'resource library' system being kindof scary. While I haven't pushed my full-Page system concept to its extremes yet, I'm hoping that it can - perhaps - deal with the issues of 'A widget in some form on the page wants to add some javascript or css to the head' issue without badgering the response; something similar to Seaside's `updateRoot` method. -- Jeff Shell ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] How does the static-apidoc script works?
Hello, how does that script works? Executing gives an error: [EMAIL PROTECTED] ~/Zope3 $ python utilities/static-apidoc /home/florian/z3-doc/ Traceback (most recent call last): File utilities/static-apidoc, line 37, in ? main() File /home/florian/Zope3/src/zope/app/apidoc/static.py, line 504, in main maker.start() File /home/florian/Zope3/src/zope/app/apidoc/static.py, line 200, in start self.browser._links_factory.urltags = urltags File /home/florian/Zope3/src/mechanize/_mechanize.py, line 505, in __getattr__ raise AttributeError( AttributeError: class 'zope.app.apidoc.static.PublisherBrowser' instance has no attribute _links_factory (perhaps you forgot to .select_form()?) and the z3-doc directoy is empty. Thanks, Florian ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
