Re: [Zope] [JOB][OT?] Position for a Python/ Zope developer in Pula, Cagliari (CA), Italy
On Tuesday, July 13, 2010, Marco Bizzarri wrote: > * IDE tools (emacs does not count as an IDE; vi* neither; Eclipse+PyDev is > preferred); I am usually not commenting on things like that, but: What a turn off! This is one of the worst requirements I have ever seen. ;-) Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] writing repozo messaging output to a file....
On Thursday 05 February 2009, michael nt milne wrote: > Ran the task and nothing was written to any of the files? Just specify an absolute path then. You do not have to create the file; it is created for you. Mmh, maybe the output is written stderr, in which case this would not work, but I am pretty sure that unix shell has an answer for that too; just read up on it. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter" ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] writing repozo messaging output to a file....
On Tuesday 03 February 2009, michael nt milne wrote: > repozo -BvzQ -r /foo/backup -f /foo/Data.fs repozo -BvzQ -r /foo/backup -f /foo/Data.fs > output.txt Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter" ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Zope 3.4.0 Released!
Hi everyone, It is finally here! Thanks goes to everyone who involved! January 29, 2009 - The Zope 3 development team announces the Zope 3.4.0 release. After 2 years of development, the Zope Foundation and the larger Zope community is proud to announce the release of Zope 3.4.0. The focus of the Zope 3.4 development effort has been the conversion from a monolithic source tree, to a set of many small packages (eggs), that can be used independently of each other. The core has been further stabilized through numerous bug fixes, and many new add-on packages have been developed to provide a richer development experience. With this release also comes a renewed commitment to a short and reliable release cycle of 6 months. Packages and Eggs - Zope 3 is now fully converted to an egg-based system. While some work still remains, it integrates very well with the rest of the Python community. The conversion to egg-based packaging also enables other Python developers to only have to use small bits and pieces of the complete Zope software system. The conversion means that Zope 3 developers do not use the classic Zope 3 tar-ball release anymore. However, for your convenience, Zope 3 developers will provide the classic Zope 3 tar ball releases for at least the 3.4 series and probably for 3.5 as well. So how are Zope 3 applications built using only eggs? The Known Good Set (KGS) The known good set -- or in short KGS -- is a configuration of packages and their versions that are known to work well together. The compatibility is frequently verified by running over twelve thousand tests on a daily basis [1]_. The KGS is tested against Python 2.4 and 2.5 on the 32- and 64-bit platforms. The list of controlled packages and their versions for Zope 3.4 can be found at the Zope 3 KGS site [2]_. The KGS can be used in several ways [3]_. The most common way is to "nail" the versions by downloading the version configuration file [4]_ and insert them as follows in your buildout configuration:: [buildout] versions = versions ... [versions] zope.interface = 3.4.0 ... ``zopeproject`` Project Builder ~~~ To start building a project using a common setup, a package called `zopeproject` can be used to quickly setup the boilerplate for the project. Ample documentation is provided at the `zopeproject` home page [5]_. `zopeproject` uses Paste or ZDaemon to create a working server. The following commands get you started:: $ easy_install zopeproject $ zopeproject HelloWorld $ cd HelloWorld $ bin/helloworld-ctl foreground Demo Packages ~ At this point, there is no demo package demonstrating a simple Zope 3 application setup. However, the ``z3c.formdemo`` package can be used as a fairly minimal setup. To get started with it, enter the following:: $ svn co svn://svn.zope.org/repos/main/z3c.formdemo/tags/1.5.3 formdemo $ cd formdemo $ python bootstrap.py $ ./bin/buildout -v $ ./bin/demo fg .. [1] http://zope3.pov.lt/buildbot .. [2] http://download.zope.org/zope3.4/3.4.0/controlled-packages.cfg .. [3] http://download.zope.org/zope3.4/intro.html .. [4] http://download.zope.org/zope3.4/3.4.0/versions.cfg .. [5] http://pypi.python.org/pypi/zopeproject Downloads - - Zope 3.4 KGS: http://download.zope.org/zope3.4 - Zope 3.4 Controlled Packages: http://download.zope.org/zope3.4/3.4.0/controlled-packages.cfg - Zope 3.4 Versions: http://download.zope.org/zope3.4/3.4.0/versions.cfg - The classic Zope 3 source release can be downloaded from: http://download.zope.org/zope3.4/3.4.0/Zope-3.4.0.tgz Installation instructions for both Windows and Un*x/Linux are now available in the top level `README.txt` file of the distribution. The binary installer is recommended for Windows. Zope 3.4 requires Python 2.4 or 3.5 to run. You must also have zlib installed on your system. Resources - - Zope 3 Development Web Site: http://wiki.zope.org/zope3 - Zope 3 Developers Mailing List: http://mail.zope.org/mailman/listinfo/zope-dev Retired: http://mail.zope.org/mailman/listinfo/zope3-dev - Zope 3 Users Mailing List: http://mail.zope.org/mailman/listinfo/zope-users - Bug tracker at launchpad: https://launchpad.net/zope3 - IRC Channel: #zope3-dev at irc.freenode.net About Zope 3 Zope 3 is a web application server that continues to build on the heritage of Zope. It was rewritten from scratch based on the latest software design patterns and the experiences of Zope 2. The component architecture is the very core of Zope 3 that allows developers to create flexible and powerful web applications. Compatibility with Zope 2 ~ Zope 3 is not upwards compatible with Zope 2. This means you cannot run Zope 2 applications in Zope 3. We continue to work on the transition from Zope 2 to Zope 3 by making Zope 2 use more and more of the Zope 3 infrast
Re: [Zope] When to use a relational database
On Friday 08 February 2008, Dieter Maurer wrote: > Jaroslav Lukesh wrote at 2008-2-7 22:40 +0100: > >JAvascript nor CSS cannot be dynamically generated from ZPT. > > They can be generated by ZPTs -- though it is not very natural. Have a look at z3c.zrtresource, which is a simple package allowing some variable substitution. It was designed for CSS and JS. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter" ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Zope 3.4.0 beta 2 Released!
November 5, 2007 - The Zope 3 development team announces the Zope 3.4.0b2 release. This release is the second beta release for Zope 3.4.0. It was preceded by an early beta 1 release back in July. Zope 3.4 introduces support for binary large objects in the ZODB, and provides a new postprocessing hook for publishing results. Many of the packages also provide small feature improvements that are too numerous to list at this point. Packages and Eggs - Since the first Zope 3.4 alpha and beta releases, we have finished the transition to a completely egg-based system. This largely means that most Zope 3 developers do not use the classic Zope 3 tar ball release anymore. However, for your convenience, the Zope 3 developers will provide the classic Zope 3 tar ball releases for at least the 3.4 series and probably for 3.5 as well. So how are Zope 3 applications built using only eggs? The Known Good Set (KGS) The known good set -- or in short KGS -- is a package index that derives from the official Python Package Index (PyPI) and thus contains all available packages in the Python world. But for a controlled set of packages, only certain versions that are known to work together are available. The list of controlled packages and their versions for Zope 3.4 can be found at the index page [1]_. The index can be used in several ways -- described here for `buildout`-based projects. The easiest method is to specify the index option in your ``buildout.cfg`` file:: [buildout] index = http://download.zope.org/zope3.4 ... You can also "nail" the versions by downloading the versions [2]_ and insert them as follows: [buildout] versions = versions ... [versions] zope.interface 3.4.0 ... ``zopeproject`` Project Builder ~~~ Philipp von Weitershausen has developed a package called `zopeproject` to quickly setup the boilerplate for any Zope 3 based project. Ample documentation is provided at the `zopeproject` home page [3]_. `zopeproject` uses Paste or ZDaemon to create a working server. Here are the necessary commands to get a project started:: $ easy_install zopeproject $ zopeproject HelloWorld $ cd HelloWorld $ bin/helloworld-ctl foreground Demo Packages ~ At this point, there is no demo package demonstrating a simple Zope 3 application setup. (I hope one gets developed before Zope 3.4.0 final.) However, the ``z3c.formdemo`` package can be used as a fairly minimal setup. To get started with it, do the following:: $ svn co svn://svn.zope.org/repos/main/z3c.formdemo/tags/1.5.1 formdemo $ cd formdemo $ python bootstrap.py $ ./bin/buildout -v $ ./bin/demo fg .. [1] http://download.zope.org/zope3.4/controlled-packages.cfg .. [2] http://download.zope.org/zope3.4/versions.cfg .. [3] http://pypi.python.org/pypi/zopeproject What is Zope 3? --- Zope 3 is a web application server that continues to build on the heritage of Zope. It was rewritten from scratch based on the latest software design patterns and the experiences of Zope 2. The component architecture is the very core of Zope 3 that allows developers to create flexible and powerful web applications. Compatibility with Zope 2 -- Zope 3 is not upwards compatible with Zope 2. This means you cannot run Zope 2 applications in Zope 3. We continue to work on the transition from Zope 2 to Zope 3 by making Zope 2 use more and more of the Zope 3 infrastructure. This means that new code written in Zope 2 can benefit from Zope 3 technology. Also, with care, code can be written that works in both Zope 3 and Zope 2. This allows a Zope 2 application to slowly evolve towards Zope 3. Unchanged Zope 2 applications are never expected to work in Zope 3, however. Downloads - - Zope 3.4 Egg Index: http://download.zope.org/zope3.4 - Zope 3.4 Controlled Packages: http://download.zope.org/zope3.4/controlled-packages.cfg - Zope 3.4 Latest Versions: http://download.zope.org/zope3.4/versions.cfg - The classic Zope 3 source release can be downloaded from: http://zope.org/Products/Zope3 Installation instructions for both Windows and Un*x/Linux are now available in the top level `README.txt` file of the distribution. The binary installer is recommended for Windows. Zope 3.4 requires Python 2.4.4 to run. You must also have zlib installed on your system. Resources - - Zope 3 Development Web Site: http://wiki.zope.org/zope3 - Zope 3 Developers Mailing List: http://mail.zope.org/mailman/listinfo/zope-dev Retired: http://mail.zope.org/mailman/listinfo/zope3-dev - Zope 3 Users Mailing List: http://mail.zope.org/mailman/listinfo/zope3-users - Bug tracker at launchpad: https://launchpad.net/zope3 - IRC Channel: #zope3-dev at irc.freenode.net Acknowledgments --- Much thanks to everyone who contributed to this release. Since all contributions are now sprea
[Zope] Static Zope 3 APIDOC available!
Hi everyone, I am happy to announce that the second Foliage sprint task is completed. Julian Bonilla, Graham Stratton and I worked on the outstanding issues on creating a functional version of the APIDOC, which comes with Zope. Thanks to Jens Vagelpohl, the static APIDOC is now available at: http://apidoc.zope.org I have also uploaded a TGZ archive to: http://download.zope.org/distribution/static-apidoc.tgz I hope that this development will spark renewed interest in the tool. In the future I plan to make more packages available in APIDOC and make it work with eggs. If you are interested, please let me know! Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] New set of z3c.form* releases!
Hi everyone, in the past month more project-related work, user feedback/requests and Javascript work has driven the development of the z3c.form framework. There are many new exciting features. There were also some small refactoring changes, which might require your CSS and tests to be adjusted. Please read the changes section below carefully! As always, the demos can be run using: $ svn co svn://svn.zope.org/repos/main/z3c.formdemo/tags/1.4.0 formdemo $ cd formdemo $ python bootstrap.py $ ./bin/buildout -N $ ./bin/demo fg Thanks to Roger, Windows users should be able to run the demos this way now as well! Visually, not much has happened; there are no new demos. However, just wait until the next round of z3c.formjs* releases! Changes --- - Feature: An event handler for ``ActionErrorOccurred`` events is registered to merge the action error into the form's error collectors, such as ``form.widgets.errors`` and ``form.widgets['name'].error`` (if applicable). It also sets the status of the form. (Thanks to Herman Himmelbauer, who requested the feature, for providing use cases.) - Feature: Action can now raise ``ActionExecutionError`` exceptions that will be handled by the framework. These errors wrap the original error. If an error is specific to a widget, then the widget name is passed to a special ``WidgetActionExecutionError`` error. (Thanks to Herman Himmelbauer, who requested the feature, for providing use cases.) - Feature: After an action handler has been executed, an action executed event is sent to the system. If the execution was successful, the event is ``ActionSuccessfull`` event is sent. If an action execution error was raised, the ``ActionErrorOccurred`` event is raised. (Thanks to Herman Himmelbauer, who requested the feature, for providing use cases.) - Feature: The ``applyChanges()`` function now returns a dictionary of changes (grouped by interface) instead of a boolean. This allows us to generate a more detailed object-modified event. If no changes are applied, an empty dictionary is returned. The new behavior is compatible with the old one, so no changes to your code are required. (Thanks to Darryl Cousins for the request and implementation.) - Feature: A new ``InvalidErrorViewSnippet`` class provides an error view snippet for ``zope.interface.Invalid`` exceptions, which are frequently used for invariants. - Feature: When a widget is required, HTML-based widgets now declare a "required" class. - Feature: The validation data wrapper now knows about the context of the validation, which provides a hook for invariants to access the environment. - Feature: The BoolTerms term tokens are now cosntants and stay the same, even if the label has changed. The choice for the token is "true" and "false". By default it used to be "yes" and "no", so you probably have to change some unit tests. Functional tests are still okay, because you select by term title. - Feature: BoolTerms now expose the labels for the true and false values to the class. This makes it a matter of doing trivial sub-classing to change the labels for boolean terms. - Feature: Exposed several attributes of the widget manager to the form for convenience. The attributes are: mode, ignoreContext, ignoreRequest, ignoreReadonly. - Feature: Provide more user-friendly error messages for number formatting. - Refactoring: The widget specific class name was in camel-case. A converntion that later developed uses always dash-based naming of HTML/CSS related variables. So for example, the class name "textWidget" is now "text-widget". This change will most likely require some changes to your CSS declarations! - Documentation: The text of ``field.txt`` has been reviewed linguistically. - Documentation: While reviewing the ``form.txt`` with some people, several unclear and incomplete statements were discovered and fixed. - Bug (IE): In Internet Explorer, when a label for a radio input field is only placed around the text describing the choice, then only the text is surrounded by a dashed box. IE users reported this to be confusing, thus we now place the label around the text and the input element so that both are surrounded by the dashed border. In Firefox and KHTML (Safari) only the radio button is surrounded all the time. - Bug: When extracting and validating data in the widget manager, invariant errors were not converted to error view snippets. - Bug: When error view snippets were not widget-specific -- in other words, the ``widget`` attribute was ``None`` -- rendering the template would fail. Enjoy! ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Zope 3 Foliage Sprint
Hi everyone, it has been over a year, since we had a conference-independent fully Zope 3 focused sprint. And I think it is time to have one! :-) Thanks to JSA Tech, there will be a sprint between September 24-28, 2007 right in the center of historical Concord, Massachusetts. We have reserved a big room where we can easily fit 35 people. For details, go to the link below: http://wiki.zope.org/zope3/FoliageSprint Now that some fairly large Zope 3 projects are in production, this will be a great opportunity to share our experiences, to learn from each other and discuss new directions that we would like to go. Upon request, I will also give some of my Zope 3 training sessions during the sprint. So I envision the sprint to be interesting for any level of Zope 3 developer, from the beginner to the expert. So sign up now! Just add yourself to the list of participants in the Wiki or send me an E-mail, if you can't. Regards, Stephan ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] z3c.form 1.5.0 and z3c.formdemo 1.3.0 released!
Hello everyone, I am pleased to announce new releases for z3c.form and z3c.formdemo. The latest changes were mainly driven by Paul Carduner's work on z3c.formjs and z3c.formjsdemo, but also by continued customer work. Again for the curious and impatient ... --- This time there is no new demo available, but the old ones still work as expected. To run the demos do the following:: $ svn co svn://svn.zope.org/repos/main/z3c.formdemo/trunk formdemo $ cd formdemo $ python bootstrap.py $ ./bin/buildout -v $ ./bin/demo fg Now you can access the demo under: http://localhost:8080/ We now also have functional tests that check all the demos: $ ./bin/test -vp1 On the Javascript Front --- A lot more progress has been made on this front. Look out for Paul's announcement! It will make up for the missing new demo in formdemo! Changes --- z3c.form - Feature: Added a span around values for widgets in display mode. This allows for easier identification widget values in display mode. - Feature: Added the concept of widget events and implemented a particular "after widget update" event that is called right after a widget is updated. - Feature: Restructured the approach to customize button actions, by requiring the adapter to provide a new interface ``IButtonAction``. Also, an adapter is now provided by default, still allowing cusotmization using the usual methods though. - Feature: Added button widget. While it is not very useful without Javascript, it still belongs into this package for completion. - Feature: All ``IFieldWidget`` instances that are also HTML element widgets now declare an additional CSS class of the form "-field". - Feature: Added ``addClass()`` method to HTML element widgets, so that adding a new CSS class is simpler. - Feature: Renamed "css" attribute of the widget to "klass", because the class of an HTML element is a classification, not a CSS marker. - Feature: Reviewed all widget attributes. Added all available HTML attributes to the widgets. - Documentation: Removed mentioning of widget's "hint" attribute, since it does not exist. - Optimization: The terms for a sequence widget were looked up multiple times among different components. The widget is now the canonical source for the terms and other components, such as the converter uses them. This avoids looking up the terms multiple times, which can be an expensive process for some applications. - Bug/Feature: Correctly create labels for radio button choices. - Bug: Buttons did not honor the name given by the schema, if created within one, because we were too anxious to give buttons a name. Now name assignment is delayed until the button is added to the button manager. - Bug: Button actions were never updated in the actions manager. - Bug: Added tests for textarea widget. z3c.formdemo - Feature: Created functional tests for the demos. - Feature: Moved all application ZCML declarations into a ZCML file called ``application.zcml``. Enjoy! Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: [Zope3-Users] z3c.form 1.4.0, z3c.formui 1.1.0, and z3c.formdemo 1.2.0 released!
On Friday 29 June 2007 05:43, Darryl Cousins wrote: > > Again for the curious and impatient ... > > --- > > > > There is also a new demo, of course! The "Questionnaire" demo provides a > > form for filling out a simple questionaire about someones Zope community > > involvement and then provides a very simple results page. Technically > > this demo (available for the DIV- and Table-based layouts) demonstrates > > the usage of groups, a new feature of this release, as well as writing > > attribute value adapters. > > The questionnaire returned with errors (because groups return > RequiredMissing errors). Should fields be selected to name and age only? > If not, then is there a template registration missing perhaps for the > fieldsets? Does this problem still persist? I have worked with the packages the last days and everything seems to work just fine. > > Paul has made some great progress recently and we have now two demos > > working, including a fully Javascript-driven calculator. I'll leave it up > > to Paul to decide whether he wants to make an announcement, but he will > > be definitely promoting his work at EuroPython! > > > > To see the demos: Replace "formdemo" with "formjsdemo" and follow > > the instructions above. > > Amazing. It sent me diving into jquery packages. You all have provided a > wonderful set of tools. Thank you. Thank you. Very cool! I think the jquery stuff is very nice and coming along well. Paul will be working on form validation the next days, so stay tuned! Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: z3c.form 1.4.0, z3c.formui 1.1.0, and z3c.formdemo 1.2.0 released!
On Wednesday 04 July 2007 14:21, Jeff Kowalczyk wrote: > --- Stephan Richter <[EMAIL PROTECTED]> wrote: > > I accidently checked in my development buildout.cfg. I fixed that now and > > everything should be fine. > > Thanks, after the API update there is one class of errors remaining in > AddressBook, with each FormClass occurrence of: > > def updateWidgets(self): > super(AddressForm, self).updateWidgets() > for name, widget in self.widgets.items(): > widget.addClass(name) ... > AttributeError: 'TextWidget' object has no attribute 'addClass' This is a new API call. :-) In the next release notes I will ask the users to checkout the release tags, so that issues like this do not occur. I just released new packages, so you have to run buildout without the "-N" option, so that it picks up the latest z3c.form and z3c.formui code. > BTW, is the mailing list the right place to report minor issues with zope3 > packages or add-ons like formdemo? This thread was also started > crossposted, should it be zope3-users only? I think zope3-users is the correct mailing list to address issues with Zope 3 packages, just to keep the zope mailing list less busy. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: z3c.form 1.4.0, z3c.formui 1.1.0, and z3c.formdemo 1.2.0 released!
On Wednesday 04 July 2007 01:09, Jeff Kowalczyk wrote: > Something in z3c.formdemo r77305 gives the following error (r77253 builds > and runs): I accidently checked in my development buildout.cfg. I fixed that now and everything should be fine. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: [Zope3-Users] z3c.form 1.4.0, z3c.formui 1.1.0, and z3c.formdemo 1.2.0 released!
On Wednesday 04 July 2007 10:32, Gary Poster wrote:
> This currently fails.
>
> :~/Dev/formdemo gary$ ./bin/buildout -N
>
> Develop: '/Users/gary/Dev/formdemo/.'
> Develop: '/Users/gary/Dev/formdemo/z3c.form'
> Traceback (most recent call last):
> File "/tmp/tmp-58J2C", line 10, in ?
> execfile('/Users/gary/Dev/formdemo/z3c.form')
> IOError: [Errno 2] No such file or directory: '/Users/gary/Dev/
> formdemo/z3c.form'
> While:
> Installing.
> Processing develop directory '/Users/gary/Dev/formdemo/z3c.form'.
>
> An internal error occured due to a bug in either zc.buildout or in a
> recipe being used:
>
> AssertionError:
>
> Should I just check out z3c.form and put a symlink in there?
I accidently checked in my development setup making z3c.form and z3c.formui
develop eggs. I just checked in the fix.
Regards,
Stephan
--
Stephan Richter
CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student)
Web2k - Web Software Design, Development and Training
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] z3c.form 1.4.0, z3c.formui 1.1.0, and z3c.formdemo 1.2.0 released!
Hello everyone, again thanks to the great feedback we received -- especially from David Pratt, Roy Mathew, and Joachim Werner -- we were able to fine-tune our new form framework even more to make it as robust of a foundation as possible for your projects! New features include group support, fully internationalized widgets for number and calendar fields, a richer select widget, refined form templates, and of course a new demo! BTW, congratulations to Roger who became father for the third time last weekend! Again for the curious and impatient ... --- There is also a new demo, of course! The "Questionnaire" demo provides a form for filling out a simple questionaire about someones Zope community involvement and then provides a very simple results page. Technically this demo (available for the DIV- and Table-based layouts) demonstrates the usage of groups, a new feature of this release, as well as writing attribute value adapters. To run the demos do the following:: $ svn co svn://svn.zope.org/repos/main/z3c.formdemo/trunk formdemo $ cd formdemo $ python bootstrap.py $ ./bin/buildout -N $ ./bin/demo fg Now you can access the demo under: http://localhost:8080/ On the Javascript Front --- Paul has made some great progress recently and we have now two demos working, including a fully Javascript-driven calculator. I'll leave it up to Paul to decide whether he wants to make an announcement, but he will be definitely promoting his work at EuroPython! To see the demos: Replace "formdemo" with "formjsdemo" and follow the instructions above. Changes --- z3c.form - Feature: The select widget grew a new ``prompt`` flag, which allows you to explicitely request a selection prompt as the first option in the selection (even for required fields). When set, the prompt message is shown. Such a prompt as option is common in Web-UIs. - Feature: Allow "no value message" of select widgets to be dynamically changed using an attribute value adapter. - Feature: Internationalized data conversion for date, time, date/time, integer, float and decimal. Now the locale data is used to format and parse those data types to provide the bridge to text-based widgets. While those features require the latest zope.i18n package, backward compatibility is provided. - Feature: All forms now have an optional label that can be used by the UI. - Feature: Implemented groups within forms. Groups allow you to combine a set of fields/widgets into a logical unit. They were designed with ease of use in mind. - Feature: Button Actions -- in other words, the widget for the button field -- can now be specified either as the "actionFactory" on the button field or as an adapter. - Bug: Recorded all public select-widget attributes in the interface. z3c.formui ~~ - Feature: Registered all defined macros for each form template. Also, added more slots to the templates providing more hooks for customization. - Feature: Added a macro/slot for the "required info", which explains how required fields are marked. - Feature: Added support for form labels. - Feature: Added support for groups to templates. z3c.formdemo - Feature: Added new field "promptChoiceField" to the "All Widgets" demo demonstrating the prompt message of the select widget. - Feature: Increased the integer default value of "All Widgets" demo to show off our new internationalized converter. - Feature: Made ``bytesField`` and ``passwordField`` non-required, since they do not show their default values prohibiting the form to successfully submit, which can be annoying when playing around. - Feature: New "Questionnaire" demo shows how to use groups effectively. It also demonstrates how the label of buttons and widgets can be changed using attribute value adapters. Enjoy! Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] z3c.form 1.3.0, z3c.formui 1.0.1, and z3c.formdemo 1.1.0 released!
On Sunday 24 June 2007 23:11, Jeff Kowalczyk wrote: > On Sun, 24 Jun 2007 22:42:35 -0400, Stephan Richter wrote: > > Yes, thanks for the report. Cheeseshop was slow on Friday, so I could not > > try the package. I just released formdemo 1.1.1, which fixes the problem. > > Thanks for the z3c.form package and the demo. > > There is an optionalChoiceField addition to browser.py which fixes an > error on the 'All Widgets' demos: Thanks, I already have released zc.formdemo 1.1.2, which fixes the problem. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] z3c.form 1.3.0, z3c.formui 1.0.1, and z3c.formdemo 1.1.0 released!
On Saturday 23 June 2007 01:44, David Pratt wrote: > Hi Stephan. This is some really awesome work and some great new examples > as well. There is more to explore and to anticipate with ajax - it is > all really very excellent. Thanks for looking at the packages seriously. BTW, over the weekend I fleshed out some thoughts on the group subforms. I will try something tomorrow. > When running the demo, I needed to add > zope.rdb to the setup.py and its corresponding meta and configuration > files to site.zcml. Yes, thanks for the report. Cheeseshop was slow on Friday, so I could not try the package. I just released formdemo 1.1.1, which fixes the problem. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] z3c.form 1.3.0, z3c.formui 1.0.1, and z3c.formdemo 1.1.0 released!
ork for the id either. Converted the codebase to use dashes in ids instead. - Bug/Feature: The ``IWidgets`` component is now an adapter of the form content and not the form context. This guarantees that vocabulary factories receive a context that is actually useful. - Bug: The readonly flag within a field was never honored. When a field is readonly, it is displayed in "display" mode now. This can be overridden by the widget manager's "ignoreReadonly" flag, which is necessary for add forms. - Bug: The mode selection made during the field layout creation was not honored and the widget manager always overrode the options providing its value. Now the mode specified in the field is more important than the one from the widget manager. - Bug: It sometimes happens that the sequence widget has the no-value token as one element. This caused ``displayValue()`` to fail, since it tried to find a term for it. For now we simply ignore the no-value token. - Bug: Fixed the converter when the incoming value is an empty string. An empty string really means that we have no value and it is thus missing, returning the missing value. - Bug: Fix a slightly incorrect implementation. It did not cause any harm in real-world forms, but made unit testing much harder, since an API expectation was not met correctly. - Bug: When required selections where not selected in radio and checkbox widgets, then the conversion did not behave correctly. This also revealed some issues with the converter code that have been fixed now. - Bug: When fields only had a vocabulary name, the choice terms adaptation would fail, since the field was not bound. This has now been corrected. - Documentation: Integrated English language and content review improvements by Roy Mathew in ``form.txt``. z3c.formui ~~ - Bug: Make sure we use the id for the "for" attribute of the "label" element and not the name. This has worked until recently, because the name and id were the same, but they are different now. z3c.formdemo - Feature: New "SQL Message" demo shows how ``z3c.form`` can be used with non-object data. Specificically, this small application demonstrates using a Gadfly database using pure SQL calls without any ORM. - Feature: New "Address Book" demo that demonstrates more complex use cases, such as subforms, composite widgets, and mappings/lists Enjoy! Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] z3c.rml 0.5 released!
Hi everyone, I am very proud to announce the release of z3c.rml version 0.5, an independent implementation of the ReportLab Markup Language (RML). RML is a XML dialect that describes the generation of a PDF using the ReportLab PDF generation library. This release focuses on compatibility with the RML version developed by ReportLab, Inc. In the future, however, the plan is to divert from the original API to fix inconsistencies between the RML Specification and the ReportLab API and to extend beyond the original functionality. Features - Full support of all common RML directives. - Support for merging in pages from external PDF files thanks to pyPdf. - Directives are fully documented using an extension to Zope's interfaces and schemas. - Code-generated DTD file. - Code-generated RML Reference document, of course as PDF built with z3c.rml. - Optional integration of page templates, allowing dynamic RML documents to be created. - Support for charts. - Test suite with 90 files. Roadmap to 1.0 -- - Fix inconsistencies between ReportLab and RML APIs. - Finish the documentation of the chart support. - Finish the page insert and merge functionality. - Improve the DTD generator and possibly write a generator for RelaxNG. - Integration of a hyphenation support, if a proper package can be found. Installation z3c.rml has been uploaded to the Python cheese shop. Thus you should only need to say: easy_install z3c.rml Unfortunately, easy install will not install the ``reportlab`` dependency, since it is not available in the cheese shop. This will have to be done by hand. Also, by default the pagetemplate support is not enabled, because of the many dependencies. However, if you want the pagetemplate support, you can simply install it or install the "zope.pagetemplate" egg. Questions and Comments -- If you have any questions or comments, please feel free to contact the Zope 3 Users mailing list at zope3-users@zope.org or E-mail me directly at [EMAIL PROTECTED] Enjoy! Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: [Zope-dev] Re: [Warning] Zope 3 component architecture (CA) not reliably usable for registrations from Python
On Thursday 11 January 2007 16:03, Dieter Maurer wrote: > Stephan Richter wrote at 2007-1-11 03:12 -0500: > > ... > >If you are populating the CA before ZCML is fully parsed, then: > > > >DO NOT POPULATE THE CA WHILE IMPORTING!!! > > > >This is so bad on so many levels. Dieter, your problem is just one > > example. Another is that unit tests have no chance to work reliably > > either. > > How do you solve the unit test issues when the CA is initialized > and populated by ZCML only? Do you fully parse the ZCML configuration > file before any unit test? For unit tests we do not use ZCML, we use the zope.component API. In those cases, however, we still do not have side-effects from importing. The unit test case is much easier, since you only test a unit and within this units conflicts of declarations are highly unlikely. > In my specific case, tests would make no problems (as we have > only a single thread) -- but of course, you had the general > case in view. Yes, I tried to make a general statement to the generall developer. My intent was not going to make a detailed discussions of all the pros and cons. After all, this was the zope@zope.org mailing list and not zope3-users or zope3-dev. ;-) Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: [Zope-dev] Re: [Warning] Zope 3 component architecture (CA) not reliably usable for registrations from Python
On Thursday 11 January 2007 05:59, Chris Withers wrote: > Stephan Richter wrote: > > If you are populating the CA before ZCML is fully parsed, then: > > Why is the CA predicated on ZCML?! Because that's how it works by default. Another way of saying this is: Collect all registrations before executing them! Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: [Zope-dev] Re: [Warning] Zope 3 component architecture (CA) not reliably usable for registrations from Python
On Wednesday 10 January 2007 05:45, Martijn Faassen wrote: > I'm a bit surprised why the huge [warning] is necessary. What I > understand you're saying is that you cannot use the component > architecture before it's done initializing. You also assert that you > need a registration to happen at Python import time. I'm curious to hear > more about why you need to do this - after all, you're talking about > listening to request start and end, and this happens after import time. If you are populating the CA before ZCML is fully parsed, then: DO NOT POPULATE THE CA WHILE IMPORTING!!! This is so bad on so many levels. Dieter, your problem is just one example. Another is that unit tests have no chance to work reliably either. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: Will Zope Run On Iron Python In Mono?
On Friday 15 September 2006 10:33, Tres Seaver wrote: > Here is an overview of the scope of such an effort: > > [/home/tseaver/projects/Zope-CVS/Zope-trunk] > $ find . -name "*.c" I have read that there is a list of other incompatibilities between C Python and Iron Python, so this is definitely not all of the work that needs to be done. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] ONE MORE TIME MAILBOXER!!!!!!!!
On Wednesday 23 August 2006 15:36, beno wrote: > > You're really not going to win any friends, or get any help, with this > > approach. > > > > Sometimes it's the only way to get past the arrogant belligerent list > subscribers who choose to make miserable the lives of those of us who > ask questions they consider stupid :) And it worked, didn't it? I think you are totally out of line. Both Andreas and Jens have contributed alot to the community, including being often the only ones to respond to mails on this list at all. Maybe you have a problem with their characters, but that's really your problem. They are both Germans and Germans tend to be direct and less socially soothing -- I am speaking out of experience. But that's just another part of Open Source Communities. You have to deal with mentalities and social behavior of people from all places on this planet. BTW, if you want really friendly help, pay someone to give it to you. ;-) Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: [Zope3-Users] Zope 3.3.0 beta 1 released!
On Monday 08 May 2006 17:07, Lorenzo Gil Sanchez wrote: > Is there a small document or howto explaining how to migrate from the > old skins/layers to the new system? I migrated by reading the deprecation messages and following their advice. :-) Unfortunately, we do not have the resources to write migration guides or new feature how-tos. I hope that someone (thinking specifically of Jeff Shell here) will blog on the new features and changes. :-) Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Zope 3.3.0 beta 1 released!
Hello everyone, The Zope 3 development team is proud to announce Zope 3.3.0 beta 1. Zope 3 is the next major Zope release and has been written from scratch based on the latest software design patterns and the experiences of Zope 2. Cleanup of the Zope 3 packages has continued to ensure a flexible and scalable platform. We continued the work on making the transition from Zope 2 to Zope 3 by making Zope 2.10 use even more of the Zope 3 packages. But we're not there yet. **You can't run Zope 2 applications in Zope 3.** Downloads http://zope.org/Products/Zope3 Installation instructions for both Windows and Un*x/Linux are now available in the top level "README.txt":http://www.zope.org/Products/Zope3/3.3.0b1/README.txt file of the distribution. The binary installer is recommended for Windows. Zope 3.3 requires Python 2.4.1 to run. You must also have zlib installed on your system. Most Important Changes Since 3.2 - Provided a new component registry API that allows multiple component registries to be combined more flexibly than before. See 'zope.component.interfaces.IComponentRegistry' for more information. - Greatly simplified local-component registration. See 'zope.component.interfaces.IComponentRegistry' for more information. - Moved many packages out of zope.app to make them easier to use outside of Zope. - Change the session credentials plugin to make it configurable in which fields it looks for the credentials. - Added a new API for collating text. You can now adapt a locale to 'zope.i18n.interfaces.ILocales.ICollator'. You can then use that to sort strings, such as menu entries, in a locale-specific fashion. - A new 'zope.annotation.factory' helper function that makes it easier to create annotations. Also added a README in 'zope.annotation' which explains how to use it. - Added a more complete set of widgets for fields that use iterable sources. These widgets now mirror the set provided by vocabulary-based fields. - Added a cleaner and more robust API to testbrowser for setting file-upload data. - Deprecated several ZCML directives: * factory * vocabulary * content (as an alias to the class directive) * modulealias * renderer:renderer - The 'browser:layer' directive and the 'ILayer' interface has been deprecated. Registering layers has become obsolete, layers should be created as interfaces extending 'IBrowserRequest'. - The 'browser:skin' directive has been deprecated. Skins should be created as interfaces extending 'IBrowserRequest' and can be registered using a simple 'utility' directive. - The 'ISkin' interface has been renamed to 'IBrowserSkinType'. For a complete list of changes see the 'CHANGES.txt' file. Resources - "Zope 3 Development Web Site":http://dev.zope.org/Zope3 - "Zope 3 Dev Mailing List":http://mail.zope.org/mailman/listinfo/zope3-dev - "Zope 3 Users Mailing List":http://mail.zope.org/mailman/listinfo/zope3-users - IRC Channel: #zope3-dev at irc.freenode.net Acknowledgments Thanks goes to everyone that contributed. Enjoy! The Zope 3 Development Team ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] errors building zope 3
On Thursday 16 March 2006 18:06, David Bear wrote: > this happens when I run make test as root as well. Don't run tests as root. I thought the test produces a warning when run as root, mhh. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope3-Users] Re: [Zope] Debugging doctests
On Thursday 23 February 2006 17:18, Chris McDonough wrote: > On Feb 23, 2006, at 4:51 PM, Stephan Richter wrote: > > So, I take it that you are a second voter in favor of not requiring > > all tests > > to be doctests. > > If the ZSCP thing takes off, I think test/doc req'ts should be > somewhat looser than mandating a particular test/doc framework > (something along the lines of "must have good test coverage and > appropriate narrative documentation", maybe with examples of what > this means that could be in doctest format by default). Would that > be acceptable? If there is enough outcry by developers, then yes. ;-) The problem is that it becomes hard to verify that documentation does not deteriorate over time. That means we need certification manager overhead to check that; and it would actually be a difficult task. With doctests I can at least force the developer to update the documentation examples, and if s/he is interested in his package at all, s/he will update the text around it as well. BTW, I have no problem to make the requirements tool independent. I could do the following changes: Doctest-based Testing --> Documentation-based Testing Actually I just did. Maybe I should also change:: Minimal Documentation --> Minimal, Testable Documentation Complete Documentation --> Complete, Testable Documentation Mmmh, now that I look at the matrix, I really think I should have a small explanatory snippet for each metric (below the matrix). Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: [Zope3-dev] The Zope Software Certification Program and Common Repository Proposal
On Thursday 23 February 2006 20:29, Jim Fulton wrote: > This is quite a document and vision. I hope we can pull something > like it off. (Like many, I recognize the daunting size of the task.) I have already working parsers and writers for all file formats. I have also a preliminary (but tested) implementation of registering, managing, unregistering a package in the repository with the ZSCP. Kamal Gill has agreed to do some initial artwork for the site, which should be done mid-March. We will see how it proceeds. Roger suggested to maybe even do some of the work during the Swiss Eastern Spring. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope3-Users] Re: [Zope] Debugging doctests
On Thursday 23 February 2006 14:16, Chris McDonough wrote: > (e.g. high- > level overview of purpose, how to install it, what other packages it > depends upon, which versions of Python/Zope it works with, who is > responsible for maintaining the package, where to report bugs, and so > on). I suppose this is really a packaging issue, but it would be > nice if more packages in the zope namespace package were treated as > "islands" like this that could be installed separately from Zope > proper. The ZSCP tries to exactly capture this information and provide it via its site. So, I take it that you are a second voter in favor of not requiring all tests to be doctests. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope3-Users] Re: [Zope] Debugging doctests
On Thursday 23 February 2006 13:37, Lennart Regebro wrote: > Not to mention, doctests are not debuggable from WingIDE. Maybe we should have a WingIDE sprint in Boston at some point. This would be a good topic. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Debugging doctests
On Thursday 23 February 2006 08:13, Lennart Regebro wrote: > As you see, I can't even step into that next line. And even if I > could, the necessity of having to step through the doctestrunning > would be a major pain in the ass. Ok, I have never needed this. And I can see why it does not work. Every doctest line is its own expression. I personally can live with that limitation. As I said, I have never needed this. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Debugging doctests
On Thursday 23 February 2006 06:53, Lennart Regebro wrote: > Ah, not in Zope 2.9 it seems. Is this expected, or an I doing something > wrong? I'm running the Five tests with bin/zopectl test --dir Products/Five > as usual, and having a set_trace() in the doctests behaves exactly as with > the old test runner, where you have to debug though the doctest running as > well, which makes it pretty useless... How do you want to use the debugger? I run the tests, if the set_trace() occurs it throws me to the prompt and all is fine. I can use the debugger as usual. There used to be an issue with the debugger not displaying anything, since doctests mess with stdout and that has been fixed. This is what Benji and I were talking about. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: The Zope Software Certification Program and Common Repository Proposal
On Wednesday 22 February 2006 10:37, Maik Ihde wrote: > However I doubt that it is possible to to do all that Certification Stuff - > afaik the core developers are all very busy people, and judgement of code > quality doesn't seem that simple to me. I should know. :-) The process is designed in a way that up to level 2 most of the tasks can be automated. Thus it should only require some human interaction. We have to try, otherwise we will not know. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: [Zope3-Users] Re: [Zope3-dev] The Zope Software Certification Program and Common Repository Proposal
On Tuesday 21 February 2006 09:48, Chris McDonough wrote: > I hate to cross-post this, but would it be possible to limit this > discussion to a single list (e.g. zope3-dev, maybe)? I'm interested > in this topic, but my mail client isn't smart enough to filter it out > to only one place and I'm sure there are a lot of other people with > the same issue. Sure, so if people are interested, the discussion will continue on zope3-dev. I only cross-posted this, so as many people are reached as possible. This is a very important proposal to the whole community. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: [Zope3-dev] The Zope Software Certification Program and Common Repository Proposal
On Tuesday 21 February 2006 05:59, Reinoud van Leeuwen wrote: > This seems to me a great step forward but I am missing something. > The quality is measured by a number of metrics, but it seems nowhere is > actually measured if the software does what it is supposed to do, if it is > clear how it works and whether it is something you would advise other > people to use. > This is one of the major problems I've had in the past with things like > the Perl CPAN repository: you can find lot's of modules that seem to solve > your problem, but usually you discover what a module is really about when > you've invested a lot of time in it. Right, I hear you. In fact, this is one of the reasons that we decided against a name like "Zope Software Quality Program". With the proposed process, we cannot guarantee 100% that the package is good. However, there are a couple of safe guards: (1) If you write doctests as a narrative text file, you really have to think hard about the functionality your package provides. I cannot stress it enough, doctest text files are *key* to the success of the certification program. (2) At least in the Common Repository, people will read check-in messages. (3) At higher certification levels, other people must support the package. This is also not 100% bullet proof, but it is something. Overall, I also expect that the community has little tolerance for malicious attempts to break the system. If someone detects foul play all he has to do is complain on the mailing lists. > Would there be room for a voting or feedback step in the process where > people that have tried the module could enter a rating? Ah, rating and feedback. :-) This was discussed in the pre-proposal phase as well. The problem with feedback and rating is that to do it right, it requires a lot of resources that we do not have. Here is a scenario: 1. A user U trashes a package because an important feature F is missing in package P. So far so good. It is his right to do so. 2. The package P authors see the comment and fix it in the code. Very cool, the process works. 3. But then the user U of the post, must retract his comment. What if he is not available? Not so good. The alternative would be to ask a certification manager, who might know nothing about the issue and will need a lot of time reviewing the complaint and solution. Not so good. While rating and feedback is good, to do it right in a process like the ZSCP costs a lot of resources. Having said that, I see the need to address the issue. Here are two suggestions: 1. Add a "Future Possibilities" section to the proposal collecting ideas for later iterations of the process. This would allow us to address some of the common concerns and say: If we have time and resources, this can be done. 2. There is already a provision in the process that a package can receive a warning. Currently the ZSCP states that the warning can only be issued when a package does not fulfill the quality metrics for a given release. I could add another provision that a warning can be issued, if X community members and 1 certification manager verified a bad package. Each warning carries an arbitrary comment that could describe the reason of the warning. This way we can use the existing communication channels (mailing list and IRC) for feedback and still have a way to formalize feedback. I guess in this case we would also need a "resolve" action that could resolve a warning. What do you think? Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: [Zope3-dev] Re: [Zope3-Users] Re: The Zope Software Certification Program and Common Repository Proposal
On Tuesday 21 February 2006 05:38, Stefane Fermigier wrote: > However, I believe like you Philipp, that both initiatives should be > decoupled. The two things are decoupled as section 2 does not require section 3. I decided to leave it in the same document for several reasons: (1) Bandwidth. Discussing two proposals of this size separately requires a lot of time. (2) I fear that the ZSCP would be talked to death and stay dead. My experience in the Open Source world has shown that if something does not have practicality, it dies unless someone is getting paid. I am certainly not getting paid for this. By biggest interest here is to bring the sub-communities together and define communication means on the code level. (3) If the ZSCP is discussed in too much abstraction, it will distance itself from what we can and want to do. While writing I have always used the Common Repository as reality check. (4) If the two were talked about separately, I think we would go back and forth on what information and process is needed. Right now, with the Common Repository in mind, I know exactly that the steps of the ZSCP will work. Overall, once we have a general agreement, section 2 will be lifted out of the proposal anyways to represent the first set of rules for the ZSCP. This document is proposal not just the rules. BTW, I am sorry for the confusion. I should have documented this better. I know I had in the earlier version, but it must have got lost. I have now added a section right at the beginning of section to communicate the separation better. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: [Plone-developers] Re: The Zope Software Certification Program and Common Repository Proposal
On Tuesday 21 February 2006 08:47, whit wrote: > what hopefully zscp would do is allow a code commons at one end (ala > collective, easy entry, friendly to experimentation) and a fully > certified set of components at the other. > > In between, there would be well defined process for how software moves > from the primordial ooze to canon. Well said. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: The Zope Software Certification Program and Common Repository Proposal
On Tuesday 21 February 2006 07:15, Andrew Milton wrote: > The proposal currently requires 3rd party code to be handed over to Zope > Foundation[1] AND checked into the ZF svn repository in order to be > 'certified'. You indicated this was indeed the case. That's not true. Phillip and I both negated this assertion. Where did you read this? The quotes you had earlier were totally out of context. Nothing in Section 2 requires anything of section 3. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: The Zope Software Certification Program and Common Repository Proposal
On Tuesday 21 February 2006 05:30, Philipp von Weitershausen wrote: > Anyways, you're welcome to contribute code to the z3base if you'd prefer > a public repository that doesn't require IP handover/sharing. Who knows, > perhaps we'll even manage to implement the ZSCP for some packages there :). That would be very cool! :-) Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: The Zope Software Certification Program and Common Repository Proposal
On Tuesday 21 February 2006 05:13, Andrew Milton wrote: > Why should Mark Shuttleworth who has plenty of means, hand over IP for > (parts of) SchoolTool? I'm sure he has more than enough ways to protect his > IP. Or are you saying that it makes sense for ZF/ZC to protect him? The reason the SchoolTool project would be interested in putting a couple packages in the common repository would be so they are moved into the Zope 3 core pr are part of the distribution. It would mean that the SchoolTool developers have to maintain less code. However, we do not need to put all of SchoolTool into the repository just to get certified. We can ask for certification with the SchoolTool code living in another repository. In fact, I think SchoolTool might be one of the first outside projects to gain certifications, since it is the only large project that I know of that fulfills the level 2 requirements (I think it could even get level 3). Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: The Zope Software Certification Program and Common Repository Proposal
Okay, this discussion is off-topic. I will not respond to it, unless I read about something that relates directly to the proposal. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: The Zope Software Certification Program and Common Repository Proposal
On Tuesday 21 February 2006 03:57, Philipp von Weitershausen wrote: > Putting stuff into svn.zope.org *does* have advantages: > > * it's easy to feed packages upstream to Zope for a later inclusion into > a Zope distribution. > > * putting a project/package under the wings of the ZF ensures long-term > IP protection > > * code in svn.zope.org will be under the common control of the Zope > developers which makes long-term maintenance easier to ensure. > > * the common license (ZPL) and the common ownership of the ZF do away > with some legal headaches... Very good summary. Better than mine. :-) Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: The Zope Software Certification Program and Common Repository Proposal
On Monday 20 February 2006 23:55, Andrew Milton wrote: Wow, you took the following two quotes out of context. > > The Common Repository is *not* a replacement for other high-level > repositories like Plone's or ECM's. It does not aim at assimilating > everything in the wider Zope community. It is merely a place for > high-quality packages that are supported by the Zope development team. > ^^^ This is from section 2, which defines the ZSCP. > Code in the Common Repository *must* also use the license stated in > section 3.5 and developers *must* sign the contributor agreement. The > ^ > agreement is necessary to ensure that contributions originated from the > contributing developer. > This is from section 3, which defines *one possible implementation* of the ZSCP. But I see where your confusion stems from and I have added a paragraph to section 3.1 stating that the Common Repository is one implementation of the ZSCP but not the only one: The Common Repository is only *one* implementation of the ZSCP. While the Common Repository implements the ZSCP guidelines and suggested automation tools, the ZSCP process itself does *not* require the Common Repository. > The license for the code should also be irrelevant, since it's just a > repository right? Just a convenient one stop shop for packages. So each > package should be able to have its own license, no need for a common > license. For the ZSCP, the license is irrelevant. For the Common repository it is not. > Having to sign the agreement serves no purpose unless there's some other IP > issue involved other than simply storing the code. The following does *not* concern the ZSCP, but the code and repository: Right, the other issue is upstream movement. Let's say you have a package that has many contributors, like zope.interface, and the Python developers would like to put the interface package into the Python standard library. Since zope.interface is ZPL and Python has its license, you need to change that. If you do not have a contributor agreement that assigns half of the rights to an organization, then you have to ask *all* developers whether the license change is okay. If you cannot find a developer anymore you can never change that license. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: The Zope Software Certification Program and Common Repository Proposal
On Monday 20 February 2006 23:16, Philipp von Weitershausen wrote: > No. The common repository under the wings of ZC/ZF is just *a* > repository that implements the ZSCP. There can be others, for example > the Plone repository, the collective repository (perhaps), etc. Correct. > I had earlier suggested to Stephan that we should keep the common > repository separate from ZSCP and there out of this proposal. IMO there > should be a separate proposal for the common repository. I guess he > didn't agree. I did agree that the two were too intermingled and thus clearly separated them. However, I personally do not have the resources to push two separate proposals on this, since I think the two are so closely related; in fact at the beginning I thought of them as one. If the common repository would not be part of the proposal, I would feel that people would dismiss it as "nice to have, but it ain't gonna happen". It is very important to me that we will be able to implement the process quickly and get on our way certifying packages. > I think both the ZSCP and the common repository (in the context of the > ZF) are a great idea. We should try to have as much stuff as possible in > the common repository, but we shouldn't make the process dependent on it. Correct. The latest revision clearly separates the two. To show their independence, I have (a) placed the two subjects into two separate main sections, (b) made sure that none of section 2 (ZSCP) requires anything from section 3 (the repository), and (c) made sure that the process does not depend on Open Source licenses or information that would only be known in public projects. I have spent a lot of time trying to be *very careful* rereading the sections over and over again. If you find that anything in the document contradicts those 3 points above, let me know! I am very interested in fixing those type of "bugs"! :-) Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] The Zope Software Certification Program and Common Repository Proposal
On Monday 20 February 2006 20:09, Andrew Milton wrote: > So in order to even get your Open Source package LISTED, you have to sign > over the rights of your code to Zope Corp (currently, Zope Foundation > later), and then check it into the svn respository. > > Is this is correct? NO! ABSOLUTELY NOT! The ZSCP is totally disconnected from the Common Repository. Note that the ZSCP does not talk about any repositories or technical implementation. It only talks about the certification goals, requirements and data. > So you're proposing that the Zope Foundation will not > even mention other Open Source code that isn't actually owned and > controlled by the Zope Foundation? Huh? Where did you get this idea from? Did you actually read the proposal? > Having a standard Zope package format would be far far more useful to the > users at large, along with the associated tools (so developers can create > compliant zope packages, and users can install packages actually using > Zope). Packaging tools can then enforce certain restrictions automatically > and create a manifest. We cannot require something that we do not have. Thus I did not address packaging or strong dependency meta-data in the proposal. I think once we investigated eggs and have some initial implementation, the proposal will be updated in light of this. > If you had that, then that would certainly ease adding 'stuff' to the > 'certified' repository, getting to LISTED level would be automatic. Becoming listed will be a nearly automated process. Also receiving level 1 and 2 will be quick decisions. This is clearly stated in section 2.8. I have added a questions to the Q&A section clearly stating that the ZSCP does not require packages in the Common Repository. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: [Zope3-dev] Re: The Zope Software Certification Program and Common Repository Proposal
On Monday 20 February 2006 19:24, Martin Aspeli wrote: > My immediate concern is about resources: Who will have the time or > incentive to police the common repository and grant certification? It > seems to be a non-trivial process that may end up being quite > time-consuming. It may be perceived as too much red tape. Please read section 2.8 carefully. Here is the most relevant part: Both, the requirements and process, are developed in a way that it should be also simple and fast to receive certification level 1 and level 2. The turn-around time of a request for being granted a certification level 1 or level 2 should be about 1 day. The certification of level 3 will usually take some more time, since it requires the certification manager to inspect the code in much more detail. However, the certification time should not exceed a couple of weeks. Overall, it is very important for the process to have as little overhead as possible and make the certification process a quick, easy and fun experience. > It may be perceived as too much centralised control, especially around > licensing. In the sense that the Zope Foundation is giving out the certifications, yes, it is centralized. But this is necessary, to make the process seem valuable/legitimate. All other certifications are centralized too, such as the TÜV controls the C2 security certification process. In terms of license, the ZSCP makes no assumptions. Even commercial projects can be certified if they show a certification manager their code. All of section 2 does not talk about a required license. A particular license will only be asserted on the Common Repository, like the ZPL is now for svn.zope.org or the GPL for the Plone core. > Secondly, and partly because I'm expecting this to come up in my absence: > your proposal is eerily simlar to Alan's two-level Plone collective post > to plone-dev, about having an "approved" list of contributors and packages > in a fenced-off repository, in addition to the collective. Yes, I am surprised he posted that. He was on the pre-proposal committee and knew for a while this was coming. As you can see in Appendix 3, there were several Plone developers involved in the recent discussion. > One obvious parallel here, by the way, is with the svn.plone.org/plone > repository. That one is controlled by the Plone Foundation, requires a > contributor agreement, and imposes restrictions on license and quality > (albeit not as formally as you do). I think this is possibly a more valid > comparison than with the Collective. Yeah, probably. As far as I understand the Goldegg protocol, the goal is to develop generic components that could be under a different license. So ideally I would like to have those components live in the Common Repository, but they do not have to. I have mentioned that at various places in the repository. > I'm actually +1 on your proposal in spirit (if it can be shown to work, > and if there is a broad consensus in the community to support it - in > fact, this is important: if there is too much division, the proposal would > likely be self-defeating) and -1 on his. Great! I agree with your reservation; but we have to try and from the comments I got from the pre-proposal committee (which represent a wide range of Zope sub-communities) I was encouraged that we would find a general agreement. > eltism and a raised bar to entry. I think that balance is different in > Plone than it is in Zope 3. Yes, I agree. Thus the proposal clearly states in section 3.2: The Common Repository is *not* a replacement for other high-level repositories like Plone's or ECM's. It does not aim at assimilating everything in the wider Zope community. It is merely a place for high-quality packages that are supported by the Zope development team. > Put differently, I think that *some* Plone components ought to move lower > down the stack, target re-usability in different systems, and thus be > subject to somewhat different rules. Perhaps these components shouldn't > have been Plone components in the first place, or perhaps their evolution > would start in Plone and move down the stack. But I think it would be > damaging for the Plone community, given its current shape and culture, to > impose those rules across the types of components that are higher up the > stack - arguably those components which should be "Plone" components still. I would never try to do this. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Off Topic: Good linux editors?
On Sunday 29 January 2006 00:14, David wrote: > I'm fairly new to Linux (ubuntu server version) and simply hate VIM. Nor > do I want to mind meld with the complex EMACS. I just wonder what > Editors some of you prefer as you write stuff like external scripts, etc. I see many people use Wing IDE, Eclipse and Boa Constructor. Of course, if you use KDE, then Kate is a nice option as well. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Zope 3.2.0 released!
Hello everyone, The Zope 3 development team is proud to announce Zope 3.2.0. Zope 3 is the next major Zope release and has been written from scratch based on the latest software design patterns and the experiences of Zope 2. It is our opinion that Zope 3 is more than ready for production use, which is why we decided to drop the 'X' for experimental from the name. We will also continue to work on making the transition between Zope 2 and Zope 3 as smooth as possible. As a first step, Zope 2.8 includes Zope 3 features in the form of Five. This is a long term effort. We're not there yet. **You can't run Zope 2 applications in Zope 3.** Downloads http://zope.org/Products/Zope3 Installation instructions for both Windows and Un*x/Linux are now available in the top level 'README.txt' file of the distribution. The binary installer is recommended for Windows. Zope 3.2 requires Python 2.4.2 to run. You must also have zlib installed on your system. Most Important Changes Since 3.1 - The ZServer has been replaced with the Twisted server. The Twisted server supports all that the ZServer supporting has well has HTTP over SSL natively and SFTP (disabled for now because of error handling problems). Also in the future it brings a better chance of other non-HTTP related protocols from being implemented for Zope3, like SMTP-in and IMAP. ZServer is still supported and will be used if you use the --zserver when you run mkzopeinstance. - Added a test browser. The test browser simulates a real Web browser as much as possible as a Python object. This allows us to write functional tests the same way the site would be experienced by the user. This greatly simplifies functional tests, makes documentation better and even helps analyzing usability. And of course, it can be used in functional doctests. - Changed the way returning large results is handled. The response.write method is no longer supported. Applications can now simply return files to the publisher. - Implemented the password managers proposal. Main idea beside the proposal is a standard way to implement password encoders/checkers, see zope.app.authentication.interfaces.IPasswordManager for details. + Added basic password managers: Plain Text, MD5, SHA1. + Support for password managers added for ZCML principals and principals saved in local PrincipalFolers. + Added bin/zpasswd command line script which helps to create ZCML principals. + Password managers support integrated into bin/mkzopeinstance. + New database generation created for convert local principals to new format. - Implemented the language namespace proposal. Now you can override the browser preferred language through the URL, like this: http://site.org/++lang++ru/path Note: If you want to use a custom IUserPreferredLanguages adapter and the '++lang++' feature together you should use zope.app.publisher.browser.CacheableBrowserLanguages adapter as a base class or at least as example. - Implemented a new object introspector. Instead of just providing information of the object's class, the new introspector focuses on providing information that is specific to the instance, such as directly provided interfaces and data, for example attribute values and annotation values. - Implemented the `devmode` switch for `zope.conf`. When turned on a ZCML feature called `devmode` is provided. Packages can then register functionality based on this feature. In Zope 3 itself, the devmode is used to only load the API doc is devmode; turning off the devmode thus closes a potential security hole and increases the start time by more than a second. - addMenuItem directive supports a `layer` attribute. - Added a re-implementation of i18n message IDs (now simply called ``Message``) that is immutable and thus can be treated like unicode strings with respect to security proxying. This implementation will replace the old one in upcoming versions. - Added "test" message catalog for testing i18n. If you specify ++lang++test in a URL, then all translated strings will be translated to [[domain][message_id], as in "[[zope][Preview]]". Text without the domain marker isn't translated. For a complete list of changes see the 'CHANGES.txt' file. Resources - "Zope 3 Development Web Site":http://dev.zope.org/Zope3 - "Zope 3 Dev Mailing List":http://mail.zope.org/mailman/listinfo/zope3-dev - "Zope 3 Users Mailing List":http://mail.zope.org/mailman/listinfo/zope3-users - IRC Channel: #zope3-dev at irc.freenode.net Acknowledgments Thanks goes to everyone that contribut
[Zope] Zope 3.2.0 beta 2 released!
The Zope 3 development team is proud to announce Zope 3.2.0 beta 2. Zope 3 is the next major Zope release and has been written from scratch based on the latest software design patterns and the experiences of Zope 2. It is our opinion that Zope 3 is more than ready for production use, which is why we decided to drop the 'X' for experimental from the name. We will also continue to work on making the transition between Zope 2 and Zope 3 as smooth as possible. As a first step, Zope 2.8 includes Zope 3 features in the form of Five. This is a long term effort. We're not there yet. **You can't run Zope 2 applications in Zope 3.** Downloads http://zope.org/Products/Zope3 Installation instructions for both Windows and Un*x/Linux are now available in the top level 'README.txt' file of the distribution. The binary installer is recommended for Windows. Zope 3.2 requires Python 2.4.2 to run. You must also have zlib installed on your system. Most Important Changes Since 3.2b1 New features - Added an option to mkzopeinstance to create instances that use ZServer, rather than Twisted. - Changed the way returning large results is handled. Applications can now simply return files to the publisher. Bug Fixes - Added input buffering to the twisted integration - Fixed the plumbing in ZServer so that attempts to return large output efficiently using iterators can actually succeed. For a complete list of changes see the 'CHANGES.txt' file. Resources - "Zope 3 Development Web Site":http://dev.zope.org/Zope3 - "Zope 3 Dev Mailing List":http://mail.zope.org/mailman/listinfo/zope3-dev - "Zope 3 Users Mailing List":http://mail.zope.org/mailman/listinfo/zope3-users - IRC Channel: #zope3-dev at irc.freenode.net Acknowledgments Thanks goes to everyone that contributed. Enjoy! The Zope 3 Development Team ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] where to put openflow in Zope3.1.0
On Thursday 22 December 2005 15:59, Martijn Pieters wrote: > On 12/22/05, adeline nombre <[EMAIL PROTECTED]> wrote: > > Can somebody tell me where I have to put my openflow directory . I use > > Zope3.0.1. > > In the readme.txt file, it is said I have to put it in > > lib/python/Products of my zope installation. but this directory does not > > exist. so where do I have to put it? > > OpenFlow is a Zope 2 Product and I doubt it'll work with Zope 3. Zope > 3 indeed does not have a Products directory. Right. Additionally, if you use Zope 3.2 or the trunk then you can download the zope.wfmc and zope.app.wfmc packages from the repository, which are activity-based workflows a la WfMC too. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Zope 3.1.0 released!
Hello everyone, The Zope 3 development team is proud to announce Zope 3.1.0 final. Zope 3 is the next major Zope release and has been written from scratch based on the latest software design patterns and the experiences of Zope 2. It is in our opinion that Zope 3.1 is more than ready for production use, which is why we decided to drop the 'X' for experimental from the name. We will also continue to work on making the transition between Zope 2 and Zope 3 as smooth as possible. As a first step, Zope 2.8 includes Zope 3 features in the form of Five. Now that we have a release that we would like to declare stable next week, we are looking for translators, who translate Zope 3 into their favorite language! We are utilizing the Rosetta system from Ubuntu for managing those translations. If you are not familiar with Rosetta, please send us a mail to zope3-dev@zope.org and we get you set up. Downloads http://zope.org/Products/Zope3/ Installation instructions for both Windows and Un*x/Linux are now available in the top level 'README.txt' file of the distribution. The binary installer is recommended for Windows. Zope 3.1 requires Python 2.3.5 or 2.4.1 to run. You must also have zlib installed on your system. Most Important Changes Since 3.0 - New Pluggable Authentication Utility (PAU), which is similar in philosophy to the Zope 2 PAS. The following features are available in the in the basic PAU facility: + Credentials Plugins: Basic HTTP Auth, Session + Authenticator Plugins: Principal Folder, Group Folder For a detailed description of the pluggable authentication utility, see 'zope/app/authentication/README.txt'. - Major simplifications to the component architecture: + Removal of the concept of a service. All outstanding services were converted to utilities: Error Reporting, FSSync, Authentication. + Site Managers are global and local now; adapters and utilties are directly registered with the site manager. Now global and local component registration and lookup behaves very similar. + Local registrations can now only have two states: active and inactive. This simplified the code so much, that 'zope.app.utility', 'zope.app.registration' and 'zope.app.site' were all merged into 'zope.app.component'. + Implemented menus as utilities. The API also supports sub-menus now. + Implemented views as adapters. Skins and layers are now simply interfaces that the request provides. - Added an integer-id facility for assigning integer identifiers to objects. - Added basic catalog and index frameworks. - Added "sources", which are like vocabularies except that they support very large collections of values that must be searched, rather than browsed. - Created a new granting UI that allows advanced searching of principal sources. - Implemented a generic user preferences systsem that was designed to be easily used in TALES expressions and via Python code. Preferences can be edited via 'http://localhost:8080/++preferences++/'. A demo of the preferences can be found at:: http://svn.zope.org/Zope3/trunk/src/zope/app/demo/skinpref/ - ZCML now supports conditional directives using the 'zcml:condition' attribute. The condition is of the form "verb argument". Two verbs, 'have feature' and 'installed module' are currently implemented. Features can be declared via the 'meta:provides' directive. - Improved API doctool: Code Browser now shows interfaces, text files and ZCML files; the new Book Module compiles all available doctext files into an organized book; the new Type Module lets you browser all interface types and discover interfaces that provide types; views are shown in the interface details screen; views and adapters are categorized into specific, extended and generic; user preferences allow you to customize certain views; 3rd party modules can now be added to the Code Browser. - Improved I18n-based number and datetime formatting by integrating 'pytz' for timezone support, implementing all missing format characters, and reinterpreting the ICU documentation to correctly parse patterns. - Added '++debug++' traversal adapter that allows you to turn on debugging flags in 'request.debug'. Currently the following flags are defined: source, tal, errors. - Improved logout support. - Developed a generic 'browser:form' directive. It is pretty much the same as the 'browser:editform' directive, except that the data is not stored on some context or adapted context but sent as a dictionary to special method (by default). For a complete list of changes see the 'CHANGES.txt' file. Resources - "Zope 3 Development Web Site":http://dev.zope.org/Zope3 - "Zope 3 Dev Mailing List":http://mail.zope.org/mailman/listinfo/zope3-dev - "Zope 3 Users Mailing List":http://mail.zope.org/mailman/listinf
[Zope] Zope 3.1.0 RC 3 released!
The Zope 3 development team is proud to announce Zope 3.1.0 candidate 3. Zope 3 is the next major Zope release and has been written from scratch based on the latest software design patterns and the experiences of Zope 2. It is in our opinion that Zope 3.1 is more than ready for production use, which is why we decided to drop the 'X' for experimental from the name. We will also continue to work on making the transition between Zope 2 and Zope 3 as smooth as possible. As a first step, Zope 2.8 includes Zope 3 features in the form of Five. Now that we have a release that we would like to declare stable next week, we are looking for translators, who translate Zope 3 into their favorite language! We are utilizing the Rosetta system from Ubuntu for managing those translations. If you are not familiar with Rosetta, please send us a mail to zope3-dev@zope.org and we get you set up. Downloads http://zope.org/Products/Zope3/ Installation instructions for both Windows and Un*x/Linux are now available in the top level 'README.txt' file of the distribution. The binary installer is recommended for Windows. Zope 3.1 requires Python 2.3.5 or 2.4.1 to run. You must also have zlib installed on your system. Changes Since 3.1.0c2 - Fixed several bugs that were considered critical. * Ported Stuart Bishop's work in ``pytz`` and ``zope.i18n`` to address broken and misleading timezone code (i.e., one issue was broken and another was misleading). * Fixed apidoc to handle extended paths, so that zope packages could be installed in software instances without apidoc losing knowledge of the core zope code. * Added custom ``executemany()`` method for cursors created through GadflyAdapter. See http://www.zope.org/Collectors/Zope3-dev/445 for discussion. - Updated ZODB to 3.5.1b2. Most Important Changes Since 3.0 - New Pluggable Authentication Utility (PAU), which is similar in philosophy to the Zope 2 PAS. The following features are available in the in the basic PAU facility: + Credentials Plugins: Basic HTTP Auth, Session + Authenticator Plugins: Principal Folder, Group Folder For a detailed description of the pluggable authentication utility, see 'zope/app/authentication/README.txt'. - Major simplifications to the component architecture: + Removal of the concept of a service. All outstanding services were converted to utilities: Error Reporting, FSSync, Authentication. + Site Managers are global and local now; adapters and utilties are directly registered with the site manager. Now global and local component registration and lookup behaves very similar. + Local registrations can now only have two states: active and inactive. This simplified the code so much, that 'zope.app.utility', 'zope.app.registration' and 'zope.app.site' were all merged into 'zope.app.component'. + Implemented menus as utilities. The API also supports sub-menus now. + Implemented views as adapters. Skins and layers are now simply interfaces that the request provides. - Added an integer-id facility for assigning integer identifiers to objects. - Added basic catalog and index frameworks. - Added "sources", which are like vocabularies except that they support very large collections of values that must be searched, rather than browsed. - Created a new granting UI that allows advanced searching of principal sources. - Implemented a generic user preferences systsem that was designed to be easily used in TALES expressions and via Python code. Preferences can be edited via 'http://localhost:8080/++preferences++/'. A demo of the preferences can be found at:: http://svn.zope.org/Zope3/trunk/src/zope/app/demo/skinpref/ - ZCML now supports conditional directives using the 'zcml:condition' attribute. The condition is of the form "verb argument". Two verbs, 'have feature' and 'installed module' are currently implemented. Features can be declared via the 'meta:provides' directive. - Improved API doctool: Code Browser now shows interfaces, text files and ZCML files; the new Book Module compiles all available doctext files into an organized book; the new Type Module lets you browser all interface types and discover interfaces that provide types; views are shown in the interface details screen; views and adapters are categorized into specific, extended and generic; user preferences allow you to customize certain views; 3rd party modules can now be added to the Code Browser. - Improved I18n-based number and datetime formatting by integrating 'pytz' for timezone support, implementing all missing format characters, and reinterpreting the ICU documentation to correctly parse patterns. - Added '++debug++' traversal adapter that allows you to turn on debugging flags in 'request.debug'. Currently the fo
Re: [Zope] Zope3 i18n
On Monday 29 August 2005 02:47, Pascal Peregrina wrote: > I am starting to have a look at Zope3 (I am a Zope 2 product developper). > > In Zope2, I currently use MessageCatalogs/Localizer/TranslationService for > i18n. > > Where can I find documentation about the corresponding functionality in > Zope3 (which appears to be i18n enabled) ? I would suggest you get my book :-) and read the chapters on internationalization and localization. The I18n support in Zope 3 is much more extensive than in Zope 2. > I would be intersted in particular about i18n tags in TAL. Zope 2's I18n TAL support was ported from Zope 3, which means that it is the same. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Zope 3.1.0 RC 2 released!
The Zope 3 development team is proud to announce Zope 3.1.0 candidate 2. Zope 3 is the next major Zope release and has been written from scratch based on the latest software design patterns and the experiences of Zope 2. It is in our opinion that Zope 3.1 is more than ready for production use, which is why we decided to drop the 'X' for experimental from the name. We will also continue to work on making the transition between Zope 2 and Zope 3 as smooth as possible. As a first step, Zope 2.8 includes Zope 3 features in the form of Five. Now that we have a release that we would like to declare stable next week, we are looking for translators, who translate Zope 3 into their favorite language! We are utilizing the Rosetta system from Ubuntu for managing those translations. If you are not familiar with Rosetta, please send us a mail to zope3-dev@zope.org and we get you set up. Downloads http://zope.org/Products/Zope3/ Installation instructions for both Windows and Un*x/Linux are now available in the top level 'README.txt' file of the distribution. The binary installer is recommended for Windows. Zope 3.1 requires Python 2.3.5 or 2.4.1 to run. You must also have zlib installed on your system. Changes Since 3.1.0c1 - Removed an untested missfeature that can cause infinite loops in principalfolder's Principal class. - Switch to METAL 1.1, which solved a serious bug. - Grant view cleaned up. - Add missing id attribute to select widget. - pytz has been updated. - Some code optimization in the HTTP factory of the publisher and ftesting framework. - Multiple headers having the same name are correctly handled now. - Now SQL operation parameters will be properly encoded before executing. - More carefully handle case when SQL parameters is a tuple or a list of a tuples. - All request factories can now be configured. - Script and Installation documentation improvements. - Fixed several bugs in API doc. Also provided some flexibility with the UI. - Fix to source widget hasInput and associated changes - Updated Build System. - Fix I18n bugs. Updated Russian and German translations. Most Important Changes Since 3.0 - New Pluggable Authentication Utility (PAU), which is similar in philosophy to the Zope 2 PAS. The following features are available in the in the basic PAU facility: + Credentials Plugins: Basic HTTP Auth, Session + Authenticator Plugins: Principal Folder, Group Folder For a detailed description of the pluggable authentication utility, see 'zope/app/authentication/README.txt'. - Major simplifications to the component architecture: + Removal of the concept of a service. All outstanding services were converted to utilities: Error Reporting, FSSync, Authentication. + Site Managers are global and local now; adapters and utilties are directly registered with the site manager. Now global and local component registration and lookup behaves very similar. + Local registrations can now only have two states: active and inactive. This simplified the code so much, that 'zope.app.utility', 'zope.app.registration' and 'zope.app.site' were all merged into 'zope.app.component'. + Implemented menus as utilities. The API also supports sub-menus now. + Implemented views as adapters. Skins and layers are now simply interfaces that the request provides. - Added an integer-id facility for assigning integer identifiers to objects. - Added basic catalog and index frameworks. - Added "sources", which are like vocabularies except that they support very large collections of values that must be searched, rather than browsed. - Created a new granting UI that allows advanced searching of principal sources. - Implemented a generic user preferences systsem that was designed to be easily used in TALES expressions and via Python code. Preferences can be edited via 'http://localhost:8080/++preferences++/'. A demo of the preferences can be found at:: http://svn.zope.org/Zope3/trunk/src/zope/app/demo/skinpref/ - ZCML now supports conditional directives using the 'zcml:condition' attribute. The condition is of the form "verb argument". Two verbs, 'have feature' and 'installed module' are currently implemented. Features can be declared via the 'meta:provides' directive. - Improved API doctool: Code Browser now shows interfaces, text files and ZCML files; the new Book Module compiles all available doctext files into an organized book; the new Type Module lets you browser all interface types and discover interfaces that provide types; views are shown in the interface details screen; views and adapters are categorized into specific, extended and generic; user preferences allow you to customize certain views; 3rd party modules can now be added to the Code Browser. - Improved I18n-b
[Zope] Zope 3.1.0c1 released!
- Added '++debug++' traversal adapter that allows you to turn on debugging flags in 'request.debug'. Currently the following flags are defined: source, tal, errors. - Improved logout support. - Added the HTTP request recorder, which lets you inspect raw HTTP requests and responses. It can be used to create functional doctests without requiring third-party tools such as TCPWatch. - Developed a generic 'browser:form' directive. It is pretty much the same as the 'browser:editform' directive, except that the data is not stored on some context or adapted context but sent as a dictionary to special method (by default). For a complete list of changes see the 'CHANGES.txt' file. Resources - "Zope 3 Development Web Site":http://dev.zope.org/Zope3 - "Zope 3 Dev Mailing List":http://mail.zope.org/mailman/listinfo/zope3-dev - "Zope 3 Users Mailing List":http://mail.zope.org/mailman/listinfo/zope3-users - IRC Channel: #zope3-dev at irc.freenode.net Acknowledgments Thanks goes to everyone that contributed. Jim Fulton, Fred Drake, Philipp von Weitershausen, Stephan Richter, Gustavo Niemeyer, Daniel Nouri, Volker Bachschneider, Roger Ineichen, Shane Hathaway, Bjorn Tillenius, Garrett Smith, Marius Gedminas, Stuart Bishop, Dominik Huber, Dmitry Vasiliev, Gary Poster, Brian Lloyd, Julien Anguenot, Albertas Agejevas, Benji York Enjoy! The Zope 3 Development Team ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Zope 3 Bug Day Summary
Hello everyone! I just wanted to let everyone know that we had a very successfull Zope 3 Bug Day today! I would like to thank Zope Corporation, POV, Nuxeo and the other community members for supporting this event by providing the manpower we needed! We were able to fix all outstanding bugs that prohibited us from making the first release candidate of Zope 3.1. As a result, I will create the 3.1 branch today, lift the feature freeze, and make a release later this weekend or first thing on Monday. Here is a list of participants and their contributions: - Gary Poster (Gary Poster): Fixed 397. Postponed 372. Removed XXX's. - Benji York (benji_work): Postponed 296, 316. Removed XXX's. Fixed 411. - Jim Fulton (J1m): Closed 344. Fixed 384. - Marius Gedminas (mgedmin): Removed duplicate tests. Fixed up forms. Fixed 302! Closed 327. - Albertas Agejevas (alga): Closed 336. Fixed 381. - Julien Anguenot (anguenot): Fixed 307. (Julien also fixed many bugs in recent weeks.) - Garrett Smith (garrett-smith): BBB code removal. Fixed 414. - Stephan Richter (srichter): Closed 302, 413, 415, 416, 419, 421. Additionally I want to thank Dmitry Vasiliev (hdima) who was not able to attend today, but was the most active community members in the last weeks to fix bugs and ensure the full internationalization of Zope 3. Thanks again to everyone for participating! Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Zope 3.1.0 beta 1 released!
or a complete list of changes see the 'CHANGES.txt' file. Resources - "Zope 3 Development Web Site":http://dev.zope.org/Zope3 - "Zope 3 Dev Mailing List":http://mail.zope.org/mailman/listinfo/zope3-dev - "Zope 3 Users Mailing List":http://mail.zope.org/mailman/listinfo/zope3-users - IRC Channel: #zope3-dev at irc.freenode.net Acknowledgments Thanks goes to everyone that contributed. Jim Fulton, Fred Drake, Philipp von Weitershausen, Stephan Richter, Gustavo Niemeyer, Daniel Nouri, Volker Bachschneider, Roger Ineichen, Shane Hathaway, Bjorn Tillenius, Garrett Smith, Marius Gedminas, Stuart Bishop, Dominik Huber, Dmitry Vasiliev, Gary Poster, Julien Anguenot Regards, Stephan ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope3 DTML in Filesystem ZSQL
On Wednesday 18 May 2005 16:50, David Pratt wrote: > Wow. This could really simplify things however I am still operating > within the CMF framework so until there is more this way, I don't know > what I can use now in this context? What would really be great is the > form generation etc from the zope schema since I am not using > Archetypes or Plone. I could really use that now. I haven't used Five > before. Would this allow me to use the zope schema to autogenerate my > forms with the validation but run it through Zope2? Yep, Five will give you those features. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope3 DTML in Filesystem ZSQL
On Wednesday 18 May 2005 10:45, David Pratt wrote: > Can someone advise whether Zope3 with continue to use DTML for > filesystem zsql or is there something else? I am starting something > and concerned about compatibility say a year or more from now when > Zope3 will become the standard. Zope 3's SQL script supports DTML and will keep supporting it. However, note that Zope 3 does not encourage this line of development. Many people dealing with SQL decide to use sqlos; see http://codespeak.net/z3/. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Seeking advice on Zope implementation
On Wednesday 18 May 2005 10:13, Dan Pozmanter wrote: > So there is only one service then? Well, in Zope 3.0 there are many services. But by definition services cannot be simply removed, since they are essential to the system. However, other componets can be removed more easily. In Zope 3.1 we removed the concept of services. All existing services were implemented using utilities. > >From the book, it seemed like there was a service for services, utilities, > > etc. > > Will much of the functionality from cmf being added to the core be > implemented via utilities? Utilities map to the CMF concept of Tools. Certain ideas from CMF were migrated into Zope 3, but I doubt that all of them will be ported into the core, since Zope 3 is an application server, not a CM framework. However, z3lab.org was just created to discuss a framework on top of Zope 3 that will provide CM-related features. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Seeking advice on Zope implementation
On Tuesday 17 May 2005 18:25, Dan Pozmanter wrote: > "In Zope 3 you can turn off as many unwanted features as you like" > > That sounds really cool. How so? > (Is there a tentative list of all zope 3 services? Do you need to run > all of them?) No, there is just one network service. But there are many utilities (in the context of a component architecture) that you can simply turn off by not loading the configuration files. Zope 3 registers new functionality using a configuration language called ZCML. You can decide which configuration files you want to load and which ones you do not. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Seeking advice on Zope implementation
Hi, it all depends what your app is like. Can you describe it some more? On Tuesday 17 May 2005 10:03, pythonic wrote: > 1. Startup custmization: How can one configure zope to load instance > of this as product > (my application) on the startup but not the ZMI and other zope stuff. In Zope 3 you can turn off as many unwanted features as you like. So from this point of view Zope 3 would be good. > 2. We want to generate xml using ZPTs and then apply xsl. Is the server > side transformation supported? Why? You first use ZPT to create XML and then an XSLT engine to create HTML. This seems like a slow approach to me. ZPT can generate HTML right away, which is much faster. Unless you already have your content in XML, an XSLT engine is total overkill. > 3. Is there any good doc available that describes how to do things you do > in ZMI programmatically? Zope 3 does not rely as heavily on the ZMI as Zope 2 and in fact all code is developed on the filesystem, so in this case it might be better for you. > 4. Zope 2.7 / 3 ? I think you should go with Zope 3. Several projects have already successfully integrated their Pyton code into Zope 3. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] developer docs
On Tuesday 12 April 2005 11:47, Milos Prudek wrote: > > Yes. In Zope X3.0 you can only develop filesystem-based Python packages, > > so in > > Well, then your book debuted at number 1 on my book shopping list. Cool. :-) Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] developer docs
On Tuesday 12 April 2005 11:01, Milos Prudek wrote: > > I'll note that we *try* to answer questions on the zope3-users mailing > > list in a timely fashion. If noone response to your question there, it is > > usually because it is a harder problem. ;-);-) > > I found out that you wrote a book about Zope 3 that gather raving > reviews on Amazon. Does the book contain all info required to develop > products (or whatever are they called in Zope 3) for Zope 3? Yes. In Zope X3.0 you can only develop filesystem-based Python packages, so in fact this is all the book covers. Section C has a fairly complex example of a message board application, complete with simple and containerish content objects. Other sections of the book cover the development of different components using filesystem-based development. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] developer docs
On Tuesday 12 April 2005 09:47, Cliff Ford wrote: > Faced with the same problem (conversion of ZClasses to file system > Products), I decided to have a look at Zope3X. There are a couple of > good new books with worked examples - but as soon as I stepped off the > guided path I found myself struggling. Still, I think I can see how to > go from 2.7 to 3 and not bother with ZClasses. I'll note that we *try* to answer questions on the zope3-users mailing list in a timely fashion. If noone response to your question there, it is usually because it is a harder problem. ;-) Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] "The Zope Book"
On Friday 08 April 2005 11:22, Paul Winkler wrote: > The primary problem with the Zope Book is still the relative scarcity of > resources (i.e. editors with time to work on it). > > The secondary problem with the Zope Book is that it's showing its age: > the choice and organization of topics is IMHO less than ideal, but that > can't be sufficiently addressed on a chapter-by-chapter basis, one needs > to have a good overview of the whole project. This vastly increases the > scope of the task. Note that my Zope 3 book is published under CC license. I could ask SAMS whether it would be okay to include parts (with proper reference and copyright notice) in the online version of the Zope 2 book. That will not document Five, but some of the component architecture. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Does anyone care whether we deprecate ZClasses?
On Wednesday 06 April 2005 16:52, Dieter Maurer wrote:
> For new projects, you should investigate the new options.
> Product development will get much simpler with Zope3 technology
> (and its schemas and views). Currently, there is no TTW
> ("Through The Web") development in Zope3 land, but that is planned.
> In about 2 to 4 years, we may have new ZClass like
> functionality implemented with Zope3 technology.
> And I am quite confident that the old ZClasses will live til
> then...
Note that I prototyped such functionality a couple years ago. One could create
TTW (Persistent) schemas and then declare a Content Component Definition
based on this schema. People could then create instances of those content
components. The Content Component Definition utility took care of doing all
the security and basic menu/view setup. One can then write views and adapters
for the content component to give it functionality.
Unfortunately, persistent schemas got broken at some point, so the code is not
that useful anymore. I really need to get together with Jim and force him to
fix the problem with me, since I constantly forget what the problem is. ;-)
Regards,
Stephan
--
Stephan Richter
CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student)
Web2k - Web Software Design, Development and Training
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Creating a namespace
Hello everyone,
I want to make my own name space with the following situation:
class X:
attributes = {'foo': 'bar'}
x = X()
Then I want to use it like that:
The result should be : bar
I found out that I have to somehow use TemplateDict and InstanceDict, but I
have no clue how to use itOf course there is no documentation on any
web site or in the Zope code itself
Thanks for you help!!!
Regards,
stephan
--
Stephan Richter
CBU - Physics and Chemistry Student
Web2k - Web Design/Development & Technical Project Management
___
Zope maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope-dev )
RE: [Zope] Python Products and ZODB Transactions
At 12:27 PM 1/23/01 +, Toby Dickenson wrote: >If your method changes data then it will always get saved. The only way is >to make sure your method never modifies a persistent object. Mmmhh, so my answer is not to derive my classes from Persistent. Will it then actually store the object in the ZODB? How does that work? That is the C part of Zope and I am not too efficient with C. Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Student Web2k - Web Design/Development & Technical Project Management ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
[Zope] Python Products and ZODB Transactions
Hello everyone, wow, I haven't posted here for a while now, but now I came to a bigger problem and I hope someone of you will have some suggestions: I built a Python Product that saves and gets data from a RDB. Whenever a method is called from my Python Product, the ZODB saves the transaction, even though the object was not modified at all. I really would like the ZODB to never save any of my Products actions. Any ideas? Reagrds, Stephan -- Stephan Richter CBU - Physics and Chemistry Student Web2k - Web Design/Development & Technical Project Management ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Transparent Folders
> Sadly its not working though, am I correct in thinking that this > functionality > exists? Am I missing a patch or something? No, that should work. I use Transparent Folders all the time. The current version has a little acquisition bug, but this should not affect you. I think the Transparent Folder Patch is not applied. When you start Zope, does it say: Applying TransparentFolders patch version 0.2. If not, you have to make the following adjustment in lib/python/OFS/__init__.py: try: # Apply the TransparentFolders patch. import Products.TransparentFolders.TransparentFolderPatch except: pass # The patch may have been removed. These lines may not exist, if you did not install the product properly. Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Student Web2k - Web Design/Development & Technical Project Management ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Is it Possible 2: Get resolution!
Q: Is it posible to get the current users SCREEN-RESOLUTION (without using Javascript!)..? Since Zope is a server-side application, it is completely ignorant to client settings. It can get only variables from the HTTP environment settings. Since Javascript is a client side language, it can get client-specific information. Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Student Web2k - Web Design/Development & Technical Project Management
[Zope] Re: [ez] Re: [Zope] A new Zope Product for the documentationof databases... of databases...
>I think that "Open Source" really means nothing if people start to use it >that way. Check the Open Source Definition, item 6 ><http://www.opensource.org/osd.html>. I completely agree. I think open-source is just becoming a buzz word. People heard it sounds cool, so let's use it! It seems like companies companies only release code, so other people will fix it for them Regards, Stephan -- Stephan Richter PlanDepot.com - Senior Application Developer and Technical Project Lead cell: (901) 230-ZOPE (9673) ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Running Mailman CGI under Zope ZServer
At 09:55 AM 11/17/00 -0500, you wrote:
> >Any chance I could take a look at your code?
1. Make a soft link from HOME/OF/MAILMAN/Mailman to HOME/OF/PYTHON/LIBS
(usually /usr/lib/python1.5).
2. Now you are able to use all the Mailman Python modules in all of you
Python programs including Zope.
3. The methods (External Methods) I used:
from Mailman import MailList
def addMember(email, passwd):
mlist = MailList.MailList('members')
mlist.ApprovedAddMember(email, passwd, 0)
mlist.Unlock()
def delMember(email):
mlist = MailList.MailList('members')
mlist.DeleteMember(email)
mlist.Unlock()
Note: If you go and read the Mailman source code, you can figure out many
more functions, that are just the 2 I used to add/delete members.
4. As I mention before, you should run Mailman and Zope as the same user to
not conflict with the DB permissions. I never fully tested that though.
Regards,
Stephan
--
Stephan Richter
CBU - Physics and Chemistry Student
Web2k - Web Design/Development & Technical Project Management
___
Zope maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Running Mailman CGI under Zope ZServer
>Second, is Mailman going to be integrated with Zope? It seems like a >natural fit. It would be nice to move away from the pipermail archiving >and use the Zope object database for archiving messages instead. I wrote once my own Python Product for Zope that simply imported the important methods and wrote my own little scripts on top. It is really easy. The only difficulty is to keep the Mailman database permissions straight, since they adjust to the executing user after every access. So the best is to run Zope and Mailman from the same account. Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Student Web2k - Web Design/Development & Technical Project Management ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
[Zope] RedHat site mentions Zope
Hello everyone, I just saw on www.redhat.com the following: Features for the developer: ... "Popular web application development tools like PHP and Zope" Link: http://www.redhat.com/products/software/linux/rhl7_standard.html Wow, pretty cool. It is only a five bullet list! I guess Zope is winning acceptance rapidly. Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Student Web2k - Web Design/Development & Technical Project Management ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] SQL
At 02:14 PM 9/20/00 +0200, Tom Deprez wrote: >Hi, > >Somebody experience with a parent code table and how to implement it in >Zope (with dtml-tree)? >Or is a PArent-Code table not SQL-like and is there a better solution? No, it is a good solution. I used it many times for threaded message boards. But I do not know how to handle it with the tree tag. If you write your own Zope Product, it should be possible. Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Student Web2k - Web Design/Development & Technical Project Management ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] db newbie
>I feel strange, asking such basic questions, but I don't really know where >to get started. I know a little bit about relational databases, but only a >little. I've seen in the zope tutorial that you can send an SQL query to the >database and use it to populate a list, but where do you build the initial >database? I have MS Access. Do I build something in that on my desktop and >upload it somewhere? Do I create a form to create the db from scratch? Well, I don't think you will find a step-by-step "How do I build a DB and use it in Zope", since Zope really does not deal with the issue. If you have a Linux box (please tell me you do), you can install postgres and follow their instructions of how to get PostGreSQL running. Then you create a database in Linux. Now, the rest we can handle with Zope. So you now need to install the PyGreSQLDA, which will allow you to connect to postgres (please run Zope on Linux, it will save you a lot of grieve). Now you connect to the DB using the connection string "DBNAME@localhost postgres", where 'postgres' is the DB user. Now that you are connected you can create a SQL method and create your tables, functions, sequences, triggers and so on. Well, now you can create other SQL Methods that will add, edit and delete records. You are done! I know my instructions are very short, but I don't have enough time to write many details, but I want to get you started. BTW, please do yourself a favor and do not run anything serious on Windoze and especially Access. :-) Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Student Web2k - Web Design/Development & Technical Project Management ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
RE: [Zope] 2d list manipulation
At 03:40 PM 9/9/00 -0500, Tim Russell wrote: >That's the thing -- It doesn't give any errors, it just doesn't have any >effect on the value in the array. Weird, no? > >--Tim > > >Nope, still nothing... > > > > > > > > > > > > > > > > Just try it without the single quotes: > > > > > > > > > > > > Can you send me the traceback? Thinking about it again makes me realize that it will not work, since set just sets a variable, but does not take care of assignments. It is a little bit hard to explain, maybe someone else can do a better job. Here is what you would have to do: This code is tested and works. But you will see that this is far too complicated, thats why I would suggest you use a Python Method or an Eternal Method to solve the issue. Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Student Web2k - Web Design/Development & Technical Project Management ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
[Zope] Optimization and speed
Hello everyone, I write this mail, because I could not find anything useful in the archives: I have a pretty big site with quiet a big database (PostGreSQL) in the background. When a site loads I can tell that after about 5 seconds the site is ready to download. The site downloads quickly thereafter if I am on a T1, DSL or Cable Modem connection. But since most of our users have 28.8k and 56k modem connection, we have to optimize for them too. When accessing the site over a modem, it takes a long time to load the site and then it pops up all at once (in IE (AOL) and Netscape). Is there a way that I can send parts of the HTML as it is generated, so that the customer starts seeing information before the entire site is loaded. Our site is about 50% slower than our competitors sites (we are serving 62kB and the competitor has up to 203kB and is 50% faster!!!) which use PHP and ColdFusion. I know that Zope is not slower. I strongly believe it is the HTML output which is not optimized (we are going to speed up the DB connection very soon by dedicating a NIC only for the DB communication). Technical Facts: - Zope 2.1.6+PCGI+Apache - Virtual Hosts for HTTP and HTTPS - PostGreSQL 7.0 (DB size: 50MB), ZPyGreSQLDA, UserDB - ZODB threads: 4 - Web Server: Pentium 500, RH 6.1, 322MB RAM (not all used), 100 MBit NIC - DB Server: Pentium 500, RH 6.1, 322MB RAM (plenty left to use), 100 MBit NIC - dedicated subnet If someone could give me some tips where I should start looking for speed holes, please let me know. Do you think it is the DB which could be so slow and I should cache search results more, are there ZServer/Apache options I can set or anything else in Zope I should have a look at? Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Web2k - Web Design/Development & Technical Project Management ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
RE: [Zope] newbie changingover to zope from html/cgi??
At 12:12 AM 6/18/00 +0530, you wrote: >can i replace javascript with python/DTML. I have used drop down menus in >the pages using javascript. Is these available in Zope or is there some >way of using these. Javascript is client based, whereby Zope handles only server-side activities similar to CGI. You usually have no way to replace Javascript, except in a few places. >Is there some book released on zope/DTML for reference. There is the ZDP (http://zdp.zope.org), which includes the ZQR (Zope Quick Reference) that lists all the tags, but is outdated. We are currently working on a model to include a DTML reference into the Zope Online Help System. That should appear at the end of the summer in the Zope distributions. >Does this mean a complete rewrite of the code is required of all the >javascript and cgi files , or is there some method to convert them to >DTML. Yes, you have to convert everything to DTML by hand. If you understand Zope well, you will find that you can do many thing easier and shorter in Zope. For most everyday tasks you have usually already a product written for you. I think before converting the entire site you should first learn Zope and Python till you feel comfortable and then redesign your site from scratch, since Zope's advanced features and object model will allow you to do things differently (read: The right way!). Regards, Stephan -- Stephan Richter @ Digital Creations Zope Documentation Since you cannot reach this mailbox from the world yet, please reply to [EMAIL PROTECTED] ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] zope as program
At 11:58 AM 6/14/00 +0900, George Donnelly wrote: >as a newbie myself i can say that i experienced some considerable >frustration in getting zope up and going and using it. (i still am!) the >documentation and mailing list support is mediocre so far at best, >especially when it comes to newbie questions. > >so i can understand where you're coming from. People are usually annoyed about newbie questions, since they have been answered a thousand times, but noone is willing to search the mailing list archives. I usually find 70% of the time the answers to my questions there. Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Web2k - Web Design/Development & Technical Project Management ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
[Zope] Folderish Objects and their contained objects
Hello everyone, I am writing a folderish class (in Python) that gets its objects from a database using SQL. I want to call the object as follows: WEBURL/FolderishClassInstance/ObjectID What needs to be done? The Folderish class should contain something like a getObject class that is automatically called when an ObjectID is passed. The getObject method then executes a SQL statement getting the object from the DB and does an R2O (relational to object) mapping, which is trivial. So what am I asking? Is there such a method already defined, that gets an object from a folderish object? What is its name, so I can redefine it? I found two potential methods called __getitem__ and _getObj in the Zope code. Is it one of them? That let's me ask: How does the URL traversal get objects inside other objects? Right now I am developing that Product for a specific purpose, but I see great potential in generalizing it, so that all types of Zope objects can be saved in a database table. This would be different from the current SQLStorage product though, since it does not save pickle files in the DB, but the actual values with their correct type, which would make it much faster. Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Web2k - Web Design/Development & Technical Project Management ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Current date in DTML
At 12:14 PM 6/6/00 -0400, Ivan Raikov wrote: >Hey all, > >How can I get the current date & time (preferably as a >DateTime.DateTime object) in DTML? I cannot instantiate a DateTime >object, because the DateTime module is not imported. Maybe a lower case 't'. Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Web2k - Web Design/Development & Technical Project Management ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] I18N
>I can explain my schema if some of you want to. Would you like to come to the Linuxtag and talk about it? Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Web2k - Web Design/Development & Technical Project Management ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: [Zope-dev] [ANN] Zope at Linuxtag 2000 in Stuttgart
At 11:45 AM 6/6/00 +0200, Gregor Hoffleit wrote: >I'll try very hard to be able to show up at least one day at the LinuxTag; >I'm going to try to help out at the Debian booth as well. > >How about I18N as a topic for one of the discussions ? I guess many European >sites and developers struggle with problems of I18N. > >Another topic I'm very interested in is packaging and distribution of Zope >extensions: keywords are Distutils, packages, zexp's, a package/dependency >tool like Debian's APT, distribution etc. pp., cf. Simon Michael's recent >rant about ZWiki/ZWikiWeb. Please check http://www.zope.org/Members/Linuxtag. Simon Cole may come and talk about ZWiki. They are not 100% sure yet. Would you be willing to give a talk on I18N? Or one of your developers? I don't know what I am going to talk about, so I can talk a little about packaging. Are the Distutils really necessary. Zope handles that inside. If you update the .py files, it updates all the object's instances respectively. Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Web2k - Web Design/Development & Technical Project Management ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
[Zope] Linuxtag update
I just got this mail from Martin Schulze, our contact at Linuxtag. >Moin, > >die Raumfrage ist geklaert, es stehen Raeumlichkeiten zur Verfuegung, >genaueres schreibe ich euch morgen oder uebermorgen. Ihr koennt also >mit den Planungen fuer die ZopeCon beginnen. > >Kurz noch: 1 Raum mit Stuehlen und Tischen: 28 Plaetze, 1 Raum mit >nur Stuehlen: 50 Plaetze. Moeglicherweise gibt's noch einen groesseren >Raum, dazu muss ich aber erst wieder wach sein. Translation: Mornin, The question about the rooms is answered, and there will be rooms for your usage. More details will come tomorrow and on Sunday. So you can start with your preparations for the ZopeCon [Zope Conference]. Pretty fast: 1 room with chairs and tables: 28 seats; 1 room only with chairs: 50 seats. It is possible that there will be another bigger room, but to confirm that I have to be awake again [message was sent 1:00 am his time]. He also just replied that we will have Internet access in the rooms. Regards, Stephan -- Stephan Richter PlanDepot.com - Senior Application Developer and Technical Project Lead Cell: (901) 573-3308 ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
[Zope] [ANN] Zope at Linuxtag 2000 in Stuttgart
Hello everyone, A couple of days back Martijn Faassen and I had the idea to organize a European Zope conference. Maik Roeder reminded me of the upcoming Linuxtag 2000 in Stuttgart. So I contacted the Linuxtag staff and we will have a booth. Martin Schulze, my main contact, will also try to get a Zope Conference setup for us, which would give us 2 rooms for one day fitting 50 people per room, where we can have talks and discussions. The Linuxtag will be from June 29th (Thursday) to July 2nd (Sunday). It will be in the Exhibition Center (Messegelaende) in Stuttgart, Germany. I know we have little time to organize the conference (26 days). We have one day to fill with speeches and discussions, so please let me know if there are people willing to give some talks or want to have "Special Interest Group" discussions, like E-commerce, XML or Portals in Zope. I would also like to know, who would be able to come, so I can give the Linuxtag staff some feedback. Here are some subjects I thought we could have: The ZDP Portal (Maik Roeder, ), XML in Zope (I know Martijn F. did a lot of work there. ;-), An Introduction to Zope for newbies (Stephan Richter -- me), ZClasses, Python Products for Zope and so on. I also would like to hear some talks and discussions about Python products that Zope uses, such as PyGres, PIL, mxDateTime and other modules. I would be very glad, if some Python-only people would show some interest too. :-) The speeches and discussion can be held in German and English (preferred, since we expect people from other countries). So, everyone who is interested in preparing a talk or discussion, please send me an E-Mail and I will compile it to a schedule. The rooms will be open for us between 9:00 am - 8:00 pm on Thursday the 29th. Let's make this a successful event! Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Web2k - Web Design/Development & Technical Project Management ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] DTML tags
At 10:07 AM 6/1/00 -1000, you wrote: >I was just wondering why the new style dtml tags don't seem to follow the >XML standard. For example, There was a lot of discussion about this last year in August, when Zope 2.0 was released. You will find that the mailing archives probably give you many answers. Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Web2k - Web Design/Development & Technical Project Management ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Site Access Counter
At 06:26 PM 5/31/00 +0900, George Donnelly wrote: >http://www.zope.org/Members/srichter/Products/ZCounter > >here is a product that someone created to do just what you are saying. > >i'm a newbie as well, only been using zope for a few weeks. Doh, this product does not work well. I have to update it somewhen...saying that for 6 month now. But I really willI promise :) Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Web2k - Web Design/Development & Technical Project Management ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] newbie question: parameter passing for ZSQL Object
>With , Zope gives me following error message: If the parameters are from another SQL statement, then the SQL method will not find them, since not the entire namespace is sent. Try: pvalueX can be also a variable. If your variables are called paramX, then the following will work: That is typical Python syntax. So in case you want to know why and how that works, read a little in the Python documentation (which is btw excellent.) Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Web2k - Web Design/Development & Technical Project Management ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Cookies
> > )"> > Try: > Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Web2k - Web Design/Development & Technical Project Management ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] ANN: Perl For Zope
> >Well, I can see good points here. Perl methods probably will attract >more users. But I can see bad points, too. What if my perl developer >resigned? Should I pick up his code? I don't want, I want Python. Should I >spent a lot of time manually converting his code to Python Method and debug >it? "There is always too many ways to do it" - it is Perl motto, not >Python. I am pretty sure Zope shouldn't has too many scripting languages. >Many protocols - yes, it is very good. But many languages? No, that's bad. I was thinking about the announcement for a while as well. I do not like Perl. I think your point is very good though. Right now I am using Zope for a client and everything is fine. If Zope supports Perl, they may hire Perl people. And you are right, what if they quit? It may happen that the market to find qualified Zope programmers becomes even tighter, since Zope programmers are now required to speak both, Python and Perl well. From a technological and development point of view, I think implementing Perl is great and very excitingimagining making this "scribble" language object-oriented. But at the end I like my good looking object-oriented Python code. :) Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Web2k - Web Design/Development & Technical Project Management ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Some newbie questions
Well, reading your mail tells me that you are looking at Zope for the first time today. :) You have the typical Zope newbie syndrom, but that will quickely change if you just spent a little bit more time. :) What can you do with REQUEST? RESPONSE? AUTHORIZED_USER? REQUEST - contains all cookies, form data and HTTP variables. You can see what it contains using . It acts like a python dictionary. RESPONSE - allows you to send non HTML HTTP responses, like setting cookies or sending redirects. >It looks like when you say it's plain >Python. What's the context? What do I need to do to call some function Yes, everything inside " " is a Python expression. It is evaluated and the result is then returned and displayed. >in a product class? What about a function in a class under some other >folder (ie. corresponding to some arbitrary URL)? > > From a product class function, is there a way to do a server redirect? I am confused. To better understand Zope, download all the guides and read them. When you are done, read them again. Then you should start playing around, trying simple tasks. Here is what happened to me: The first day I sat around and wrote 5 lines of code. I had no clue. The second day I wrote some samples and started on a Web site. The third day, I had a complete user management system, a message board and a news section implemented (back then I did not know about all the existing products for Zope.) >What should I use for managing users (seems to be GUF, LoginManager, maybe >others)? How about a threaded message board? There seem to be a number >of products planning not to continue from their current codebase. I use UserDB right now and it works fine for me. But I have read many times that GUF is good. >Can anyone explain ZClasses? Where's all the code? Is that the future of >Zope? There is a guide to ZClasses as well as a tutorial published by beehive. >Just hoping to find the road. Thanks a lot! Me too, but I am sure you will. Feel free to contact me any time. :) Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Web2k - Web Design/Development & Technical Project Management ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Really dumb newbie question
At 05:01 PM 5/23/00 +0100, you wrote: >This one is so dumb you'll be laughing, but any help would be greatly >appreciated. > >I need to evaluate an IF. That's all. I have a variable called Action >that's a string, and it can be null, "Add", "Update" etc. > >I try something along the lines of: > > blah > Just try: Inside the " " is a python expression that is evaluated and returns true or false. In case you do not know Python, I would suggest you learn the basic logic, since in Zope all expressions " " are evaluated as Python syntax expressions. Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Web2k - Web Design/Development & Technical Project Management ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
