[Zope3-Users] How does the static-apidoc script works?

2006-08-14 Thread Florian Lindner
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", li

Re: Re: [Zope3-Users] Re: zalchemy integration

2006-08-14 Thread Jeff Shell
On 8/14/06, Stephan Richter <[EMAIL PROTECTED]> wrote: On Monday 14 August 2006 01:00, Jeff Shell wrote: > If things slow down... uhm, ever... for us, I'd like to see if I can > get us to open up some of the more generic toolkits we've built up in > recent months, as they've been very empowering.

Re: Re: [Zope3-Users] zalchemy integration

2006-08-14 Thread Jeff Shell
On 8/14/06, Carlo Cardelli <[EMAIL PROTECTED]> wrote: > I think that my company's recent experiences with Zope and SQLAlchemy > show that the fundamentals of Zope can be terrific toolkit for rich > object oriented RDBMS / Business Object backed applications that have > nothing to do with content

Re: Re: [Zope3-Users] Re: zalchemy integration

2006-08-14 Thread Jeff Shell
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

Re: [Zope3-Users] Re: zalchemy integration

2006-08-14 Thread Benji York
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 'cart

Re: [Zope3-Users] Re: zalchemy integration

2006-08-14 Thread Philipp von Weitershausen
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 switch

Re: [Zope3-Users] zalchemy integration

2006-08-14 Thread David Pratt
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 ide

Re[2]: [Zope3-Users] zalchemy integration

2006-08-14 Thread Adam Groszer
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, bu

Re: [Zope3-Users] zalchemy integration

2006-08-14 Thread Stephan Richter
On Monday 14 August 2006 05:08, Carlo Cardelli wrote: >  > I think that my company's recent experiences with Zope and SQLAlchemy > > > show that the fundamentals of Zope can be terrific toolkit for rich > > object oriented RDBMS / Business Object backed applications that have > > nothing to do with

Re: [Zope3-Users] Re: zalchemy integration

2006-08-14 Thread Stephan Richter
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'

Re: [Zope3-Users] Re: zalchemy integration

2006-08-14 Thread Stephan Richter
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 creat

[Zope3-Users] Re: zalchemy integration

2006-08-14 Thread Philipp von Weitershausen
Roger Ineichen wrote: > Hi Mailman > > [...] >>> 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. > > If you add lovely to the checkin massages, please add also

Re: [Zope3-Users] zalchemy integration

2006-08-14 Thread Carlo Cardelli
Jeff, Before everything else, thank you very much for sharing your thoughts and experience: as a newcomer, I found them very valuable. Hm. It seems like a NameChooser should *somehow* be giving you a usable name. That pair:: container[name] = content return container[name] seems redun

RE: [Zope3-Users] Re: zalchemy integration

2006-08-14 Thread Roger Ineichen
Hi Mailman [...] > > > > 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. If you add lovely to the checkin massages, please add also the *z3c* top level namesp

Re: [Zope3-Users] Re: zalchemy integration

2006-08-14 Thread Stephan Richter
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 th

Re: [Zope3-Users] Re: zalchemy integration

2006-08-14 Thread Stephan Richter
On Monday 14 August 2006 01:00, Jeff Shell wrote: > I (mildly) agree. In my `WebPageSupport` mix-in, I've added a method > `renderProvider`. Primarily it was to get around calling the provider > a second time and having its `update` method called again, although > I've now added some a `hasUpdated`

Re: [Zope3-Users] Re: zalchemy integration

2006-08-14 Thread Stephan Richter
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

[Zope3-Users] Re: zalchemy integration

2006-08-14 Thread Michael Haubenwallner
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/p

Re: [Zope3-Users] Re: zalchemy integration

2006-08-14 Thread Stephan Richter
On Monday 14 August 2006 01:00, Jeff Shell wrote: > If things slow down... uhm, ever... for us, I'd like to see if I can > get us to open up some of the more generic toolkits we've built up in > recent months, as they've been very empowering. You should really do this as you code. Not only do you

Re: [Zope3-Users] Re: zalchemy integration

2006-08-14 Thread Stephan Richter
On Monday 14 August 2006 01:00, Jeff Shell wrote: > Skinning aside, it's nice to be able to componentize the page. We've > already made some common Viewlets that can be used in a project with > very little fuss, such as Menu renderers. CSS applies most of the > visual styles. The standard template,

RE: [Zope3-Users] z3wingdbg 0.1.0: Wing IDE debugger integration forZope3

2006-08-14 Thread Roger Ineichen
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.or

RE: [Zope3-Users] zalchemy integration

2006-08-14 Thread Roger Ineichen
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 c