Re: [Zope-dev] Reasons for the current API reference docs implementation?

2004-04-05 Thread Dieter Maurer
Chris McDonough wrote at 2004-4-4 13:56 -0400: ... I think the real answer would be to go and create interfaces for all API classes and turn that into an API reference *BEWARE* however, that interfaces lack information *VITAL* for an API reference: the constructor description! Look at the

Re: [Zope-dev] Re: ZPT for CSS, anyone?

2004-04-05 Thread Chris Withers
Shane Hathaway wrote: I think it would be pretty neat. :-) And YET ANOTHER thing the poor Zope user has to learn when they start: Hardly. You're confusing a fun little project with the Zope core platform. Please don't put down people's ideas so quickly. Indeed, my mistake, I do apologise :-)

Re: [Zope-dev] ZODB with twisted web.

2004-04-05 Thread Chris Withers
Syver Enstad wrote: I am checking out how to use ZODB with twisted web. Not sure, but you could check the SchoolTool project, which I know uses ZODB and twisted, just not sure if it uses twisted.web or not... Chris -- Simplistix - Content Management, Zope Python Consulting -

Re: [Zope-dev] Reasons for the current API reference docs implementation?

2004-04-05 Thread Chris Withers
Paul Winkler wrote: I'm not sure that exposing the docstrings of the classes themselves would be much better than the current situation, well, it would arguably make it marginally more likely that the api reference is updated when the code is updated. Indeed. I think using interfaces and

Re: [Zope-dev] Reasons for the current API reference docs implementation?

2004-04-05 Thread Stephan Richter
On Monday 05 April 2004 03:49, Dieter Maurer wrote: Chris McDonough wrote at 2004-4-4 13:56 -0400: ... I think the real answer would be to go and create interfaces for all API classes and turn that into an API reference *BEWARE* however, that interfaces lack information *VITAL* for an API

Re: [Zope-dev] Reasons for the current API reference docs implementation?

2004-04-05 Thread Stephan Richter
On Monday 05 April 2004 06:50, Chris Withers wrote: Indeed. I think using interfaces and docstrings would be good, as twisted does: http://www.twistedmatrix.com/documents/current/api/index.html http://www.twistedmatrix.com/documents/current/api/twisted.application.serv ice.Service.html Who

[Zope-dev] Unique ID generation with ZODB.

2004-04-05 Thread Syver Enstad
How does one implement a unique id generator in ZODB. The id's should be strictyl ascending and be a an int. Would opening a temporary connection increment a persistent counter and commit do the trick? ___ Zope-Dev maillist - [EMAIL PROTECTED]

Re: [Zope-dev] Unique ID generation with ZODB.

2004-04-05 Thread Andreas Jung
The simplest solution is to keep the counter as file in the filesystem. Access to the file must be synchronized through a lock object (- Python docs). Just a few lines of Python code. -aj --On Montag, 5. April 2004 14:18 Uhr +0200 Syver Enstad [EMAIL PROTECTED] wrote: How does one implement

[Zope-dev] Re: Proposal: Sanitize HelpSys API Reference, was Re: Reasons for the current API reference docs implementation?

2004-04-05 Thread Casey Duncan
On Sun, 4 Apr 2004 17:50:13 -0400 Paul Winkler [EMAIL PROTECTED] wrote: I've posted my proposal: http://dev.zope.org/Wikis/DevSite/Proposals/SanitizeHelpSysAndAPIReference I am 100% for this proposal and I have been thinking on and off about the same thing for years. I agree that we need to

Re: [Zope-dev] Reasons for the current API reference docs implementation?

2004-04-05 Thread Paul Winkler
On Mon, Apr 05, 2004 at 06:56:40AM -0400, Stephan Richter wrote: I think the Zope 3 API docs are much nicer than the Twisted ones above. I have put a lot of time into Zope 3's version, so that it is as usable as possible. You should check it out. Start Zope 3 and go to:

Re: [Zope-dev] Re: Proposal: Sanitize HelpSys API Reference, was Re: Reasons for the current API reference docs implementation?

2004-04-05 Thread Paul Winkler
On Mon, Apr 05, 2004 at 09:44:30AM -0400, Casey Duncan wrote: On Sun, 4 Apr 2004 17:50:13 -0400 Paul Winkler [EMAIL PROTECTED] wrote: I've posted my proposal: http://dev.zope.org/Wikis/DevSite/Proposals/SanitizeHelpSysAndAPIReference I am 100% for this proposal and I have been thinking

Re: [Zope-dev] Reasons for the current API reference docs implementation?

2004-04-05 Thread Paul Winkler
On Mon, Apr 05, 2004 at 06:52:07AM -0400, Stephan Richter wrote: On Monday 05 April 2004 03:49, Dieter Maurer wrote: Chris McDonough wrote at 2004-4-4 13:56 -0400: ... I think the real answer would be to go and create interfaces for all API classes and turn that into an API reference

[Zope-dev] Re: Proposal: Sanitize HelpSys API Reference, was Re: Reasons for the current API reference docs implementation?

2004-04-05 Thread Casey Duncan
On Mon, 5 Apr 2004 11:00:59 -0400 Paul Winkler [EMAIL PROTECTED] wrote: On Mon, Apr 05, 2004 at 09:44:30AM -0400, Casey Duncan wrote: On Sun, 4 Apr 2004 17:50:13 -0400 Paul Winkler [EMAIL PROTECTED] wrote: I've posted my proposal:

Re: [Zope-dev] Re: Proposal: Sanitize HelpSys API Reference, was Re: Reasons for the current API reference docs implementation?

2004-04-05 Thread Stephan Richter
On Monday 05 April 2004 11:00, Paul Winkler wrote: - If we create examples that they be runnable doctests, which are executed by test.py The latter may mean we need a better integration test framework, I don't know. I think we'd need to try out a few and see. I can certainly help here.

Re: [Zope-dev] Reasons for the current API reference docs implementation?

2004-04-05 Thread Stephan Richter
On Monday 05 April 2004 11:38, Paul Winkler wrote: I'm not sure if that's what Dieter meant, but in any case, there is another thing we need documented for zope 2: product constructors. These are factory functions, e.g.: def manage_addPythonScript(self, id, REQUEST=None, submit=None):    

[Zope-dev] External Editor and Archetypes 1.3

2004-04-05 Thread Christian Heimes
Hi! I tested the External Editor integration with the last version of AT Document from my AT Content Types. When saving the changes I'm getting this exception: Traceback (innermost last): Module ZPublisher.Publish, line 100, in publish Module ZPublisher.mapply, line 88, in mapply Module

[Zope-dev] Next bug: base_edit and webdav lock

2004-04-05 Thread Christian Heimes
The base_edit template of archetypes doesn't take care of webdav looks. It's possible to save a file while it's looked. Christian ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML