- Zope-Announce - Zope lists

Zope 3.4.0 beta 2 Released!
by Stephan Richter 06 Nov '07

06 Nov '07

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 spread over a multitude of packages, listing all contributors is not feasible anymore.

1 0

[ANN] Zope 2.10.5 released
by Andreas Jung 29 Oct '07

29 Oct '07

The Zope developer community I is pleased to announce the release of Zope 2.10.5. You can download Zope 2.10.5 from: http://www.zope.org/Products/Zope/2.10.5/ This release uses unicode as internal representation for ZPT. For this reason you are strongly encouraged to read <http://www.zope.org/Products/Zope/2.10.5/Zope-2.10.5-released> carefully. Some new features of Zope 2.10: - ZPT implementation based on Zope 3 - experimental WSGI and Twisted integration - Zope 3.3, Five 1.5 integration - clock server - lots of minor improvements and fixes - replaced several Zope 2 modules with their sister implementation of Zope 3 For more information on what is new in this release, see the CHANGES.txt files for the release: http://www.zope.org/Products/Zope/2.10.5/CHANGES.txt Please bring all the bugs you have found to the Zope bugtracker: http://collector.zope.org/Zope For more information on the available Zope releases, guidance for selecting the right distribution and installation instructions, please see: http://www.plope.com/Books/2_7Edition/InstallingZope.stx Supported Python versions: Zope 2.10 requires Python 2.4.3+ (Python 2.4.2 is still acceptable). Older Python versions are no longer supported. Using Python 2.5 is also *unsupported*. - -- Andreas Jung -- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: info(a)zopyx.com - Phone +49 - 7071 - 793376 E-Publishing, Python, Zope & Plone development, Consulting

1 0

[Zope-Annce] Reminder: Zope Foundation annual meeting (Oct 31, 2007, 14:00 UTC)
by Tres Seaver 29 Oct '07

29 Oct '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Aroldo Souza-Leite wrote: > Zope Foundation > To the Membership at Large > > Call to the annual meeting. > > On behalf of the Zope Foundation Board of Directors, I call the Zope > Foundation members of all membership classes to the annual meeting on > > Wednesday, October 31, 2007 > at 14:00 UTC (please check local time zone) > > The meeting will take place on IRC. > > The newly elected Board of Directors will be seated at the annual > meeting. > > Zope Foundation members of all membership classes are expected to be > subscribed to the foundation(a)zope.org mailing list. > > Further information and the meeting agenda will be sent to the > foundation(a)zope.org mailing list in the course of the next three weeks. > > With best regards, > > Aroldo. > ----------------------- > Aroldo Souza-Leite > Zope Foundation, Inc > Board of Directors > Chairman Technical Notes =============== Time Zone in GMT - ---------------- Please verify the time of the meeting in your own local time zone by selecting that zone on the following page and submitting the form: http://www.timezoneconverter.com/cgi-bin/tzc.tzc?use_current_datetime=0&mon… IRC Mechanics - ------------- The meeting will be conducted on the following IRC channel: irc://irc.freenode.net/#zope-foundation Prior to the call-to-order, the chair will request that Foundation members present identify themselves by saying their full names on the channel. Between the call-to-order and adjournment, the channel will be moderated, with the chair recognizing speakers. Foundation Members who wish to be recognized by the chair, and therefore receive "voice" on the channel during the moderated segment, will need to authenticate with the Freenode NickServ; please see the following document on how to set up an authenticated nickname: http://freenode.net/faq.shtml#userregistration For the board, Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHJgFO+gerLs4ltQ4RAuwpAKCl0kE0iEcDRUcFlYANv9fMS2y5zwCePYCB 2VQtEBSsvnnJt74cn7ihku0= =tZz4 -----END PGP SIGNATURE-----

1 0

[ANN] Plone4Universities project founded
by Andreas Jung 15 Oct '07

15 Oct '07

I am pleased to announce the Plone4Universities project founded during the Plone Conference last week in Naples, Italy. The goals for the P4U projects are: * promoting Plone to universities or comparable institutions * providing informations related to Plone and universities in a single place * improve the visibility of related projects * strengthen the collaboration between projects and pooling resources * provide a communication-platform for universities and institutes using Plone You can find the P4U project at www.plone4universities.org Andreas -- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: info(a)zopyx.com - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK ------------------------------------------------------------------------ E-Publishing, Python, Zope & Plone development, Consulting

1 0

Grok 0.10.1 released!
by Martijn Faassen 10 Oct '07

10 Oct '07

Hi there, 2007-10-10 - The Grok project is happy to release Grok 0.10.1! Grok 0.10.1 is a bugfix release of Grok, and the first outcome of the Neanderthal Grok sprint that was hosted by GfU Cyrus in Cologne, Germany, last week. The sole aim of this release is to fix Grok's installation story. Releases of Zope 3 components that Grok relied on had the tendency to break Grok. Since Grok now uses a fixed list of versions it relies on, this problem should now be solved. The grokproject tool has also been updated to 0.6, and now automatically uses the version list feature. To update grokproject to 0.6, please type the following: $ easy_install -U grokproject For more information about this release, including instructions on how to update existing buildouts to use the version list feature, see here: http://grok.zope.org/releaseinfo/readme.html What is Grok? --------------------- Grok: now even cavemen can use Zope 3 Grok is a web application framework based on Zope 3 technology. Grok aims to make Zope 3 technology more easy to use for beginners and experienced developers alike. More about Grok: http://grok.zope.org

2 1

Vote for Silva as a CMS Awards finalist
by Kit BLAKE 03 Oct '07

03 Oct '07

Hi all, Please take a minute to vote for Silva in Packt's Open Source CMS Award: http://www.packtpub.com/article/best-other-open-source-cms-award-final-silva 2007/10/1, Alexander Limi <limi(a)plone.org>: > Please take a minute to vote for Plone in Packt's Open Source CMS Award: > > http://www.packtpub.com/article/best-other-open-source-cms-award-final-plone You can vote for Plone too :) but let's get Zope 'up there' (voting takes less than a minute). All the "Overall Winner" candidates are PHP based, and in the "Best Other Open Source CMS" we're competing with Java or .Net systems. Thanks! -- Kit BLAKE · Infrae · http://infrae.com/ + 31 10 243 7051 Hoevestraat 10 · 3033 GC · Rotterdam + The Netherlands OpenPGP 0xE67AD0F2 · Contact = http://xri.net/=kitblake

1 0

Help vote for Plone as a CMS Awards finalist
by Alexander Limi 01 Oct '07

01 Oct '07

Hi all, Please take a minute to vote for Plone in Packt's Open Source CMS Award: http://www.packtpub.com/article/best-other-open-source-cms-award-final-plone You managed to bring Plone to the front page of DIgg.com with your earlier effort for the release of Plone 3.0, let your Python vote count — and make Plone be selected over the Java-based CMSes in their selection! (And if you haven't tried Plone 3.0 yet, you should! :) Thanks! -- Alexander Limi · http://limi.net

1 0

[ANN] SmartPrintNG V 1.0.0 released- Professional and high-quality export of Plone content into office formats
by Andreas Jung 29 Sep '07

29 Sep '07

I am pleased to announce the final release of SmartPrintNG V 1.0.0 SmartPrintNG can convert almost any Plone content into different formats: * PDF * RTF * ODT * WML * DOCX In addition SmartPrintNG provides a configurable pre- and post-processing pipline in order to give you full control over the conversion process. SmartPrintNG comes with filters to remove images, remove links or generate a link list at the end of the document, support for breaking a document into pages (e.g. for presentation handouts) and much more. To control the look & feel of the generated document you can configure custom templates and custom style-sheets. SmartPrintNG is highly customizable and configurable giving you ultimate control over all aspects of the conversion process. Requirements: * Zope 2.10.4 (Plone 3.0), Zope 2.9.8 (Plone 2.5) * Plone 3.0, Plone 2.5 * XFC converter (XMLMind) * XINC converter (Lunasil) * zopyx.convert V 1.0.0 for higher * BeautifulSoup V 3.0.0 or higher * Java 1.5 or higher Project homepage and download: http://smartprintng.zopyx.com Andreas Jung -- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: info(a)zopyx.com - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK ------------------------------------------------------------------------ E-Publishing, Python, Zope & Plone development, Consulting

1 0

Zwiki 0.60 released
by Simon Michael 20 Sep '07

20 Sep '07

I'm glad to announce the recent release of Zwiki 0.60, breaking the unusually long dry spell since 0.59 in 2007/04. Development has continued at a steady pace, as you can see at the darcsweb link below; also the docs continue to improve at zwiki.org and the issue tracker continues to grind through the mass of issues. Zope 2.10 and Plone 3 users will want to upgrade to this one. I am tinkering with the development process to try and make us more efficient. We have fun on this project and don't mind sharing it around, so more contributors always welcome! Best wishes, -Simon Links: - http://zwiki.org - documentation, discussion, download, start here - http://joyful.com/darcsweb/darcsweb.cgi?r=ZWiki;a=shortlog - commit history - http://zwiki.org/FreeHosting - free zwiki hosting - http://joyful.com - related sites Release notes: Zwiki 0.60.0 2007/09/15 ======================= Fix TAL unicode errors with zope 2.10, Plone 3/CMF 2.1 compatibility, quicker page rendering, permanent edit history, labelled bracket links, better support for custom wiki templates, a tool for importing MoinMoin wikis, many other improvements and code cleanups. Upgrade notes * Zope >=2.10 users should upgrade to this release to avoid TAL unicode errors * Plone 3/CMF 2.1 users should upgrade to this release * Plone 2.x users will not be able to install this release in sites, see #1322 below * a wiki catalog is no longer optional, and will be added if missing * skin customizers should note the wiki navigation links are now in the wikipage template Installing * #1322: Plone 3 & CMF 2.1 compatibility. Warning, this version of Zwiki uses GenericSetup and is not compatible with older versions of Plone/CMF. This could be tackled in a future release if there is demand. See the issue page for discussion and possible workarounds. * tools/prepmoin.py, imports MoinMoin wiki data to a zwiki (M. Pedersen) * #1217: fix setupDtmlPages error (Sascha Welter) Configuring * fixPageEncoding renamed to fixEncoding and fixed * move wiki navigation links to wikipage template for easier customizing * #1041, #1145: ensure a catalog and an outline cache are always present. Browsing * make the home link, wiki logo and index_html use the default page url consistently * hide the prefix in mailto: email hyperlinks * change long-standing links order: contents before changes, help after options * #1348 - redirect to original page after useroptions We are always calling FrontPage/useroptions to limit bot traffic. Now we are carrying the redirectURL through the REQUEST, so we know where to redirect in the end. (Sascha Welter) * #1333: make literal/code style more precise to avoid styling difform headings * help page cleanup * #1145: avoid the broken dtml-in sort option in SearchPage, also, to avoid occasional search errors * most access keys are always available, but disable the s subscribeform key if mailout is not enabled, as an extra cue * speed up pages by doing less work * slight discussionUrl speedup, don't look for UserDiscussion page * speed up hasIssues, which was taking half the 2.5s skin render time on zwiki.org Editing * #1157: replace revertEdits[Everywhere]By with history-wiping expunge, expungeEditsBy, expungeEditsEverywhereBy methods * more robust history: - allow partial history, revisions can safely be deleted - use a btree folder for revisions if possible - more zodb cache friendly - richer history api * new history and diff views. History should now be at least as functional as before, and permanent * simple permanent revisions model, use revisions folder instead of recycle_bin * stop discarding content outside of html body tags - they may be part of the content * #1370: allow arbitrary urls in bracket links * optional link labels after | in bracket links * #965: avoid infinite recursion error when a page is reparented to itself (Sascha Welter) * #570 - Ensure valid id with file uploads. But meanwhile try to mess with uploaded file's names as little as possible. We check first if the name is acceptable to Zope, and only if it isn't we change it. (Sascha Welter) * #1085 - Comments are now properly formatted in HTML pagetype. Now it's possible to use comments in HTML pagetype pages and have the comments still properly formatted after page edits. Similar to #1079 and therefore again credits and thanks to Martijn Pieters. We are in the same manner using preRenderMessages to add the comments. (Sascha Welter) * #1079 - Plaintext comments work now. Commenting on plaintext pages would work until you edited the page itself, then the prerendering method lost the comment rendering. Credits go to Martijn Peters for this patch, a bit adapted to code that had moved on. I had to tweak the output test, as the exact placement of blank lines at end of the page content has changed minimally. (Sascha Welter) * refuse any incoming text that's not ascii or utf-8, to avoid problems later * createform and create now look only at folder permissions, not the current page, to be consistent with the page management form. The 'Zwiki: Add pages' permission is meaningful only on folders, and ignored on pages. * #512 - fix footnotes with "create page" links in RST (Sascha Welter) * #1323: revert methods now obey the edits_need_username option * clean up revertEditsBy, don't break with new pages Mail * #1256: handle mailins with encodings other than utf8 * don't log body of mail-ins by default * #141 - Uploading a file causes an "edit" mailout now. (Sascha Welter) * also allow a 'Secure Maildrop Host' for sending mail (Sascha Welter, Encolpe Degoute) Feeds * no updates Issue tracking * yellow color to make open funded issues stand out * IssueTracker cleanups * #1334: make fuzzy urls work better with issue numbers * use html instead of stx page type when installing issue tracker as dtml pages, for a 4x speedup of the unit test on my system General * many code cleanups including imports, safe_hasattr, deprecation warnings, pyflakes warnings, tests * Replace hasattr() with safe_hasattr() everywhere. Problem with hasattr() is that it masks exceptions, which is known to be problematic. "Our" new safe_hasattr() is from http://www.zope.org/Collectors/Zope/742 - with thanks and credits to Dieter Maurer. (Sascha Welter) * #1365 use talsafe() on newname in /editform to avoid UnicodeDecodeError. This problem appeared in localized browsers only for some reason, but the fix likely is necessary for 2.10 too. (Sascha Welter) * #1339 - fixing text encoding for editform.pt textarea. (Sascha Welter) * #1330: a better fix for these unicode errors. Zope 2.10 expects TAL data to be unicode, older zopes do not. This can lead to many obscure unicode errors depending on your system locale, wiki content, cookies, phase of the moon etc. This fix aims to make all the standard templates robust against this. Wikis with old customized templates will still be vulnerable to this problem after upgrading to zope 2.10, until those templates are updated. * partial workaround for #1330 UnicodeDecodeError * Default wiki type is "basic" + added 'jpeg' fs templating. (Sascha Welter) * #1332 - fix for the fix + default wiki_type is "basic". We're now not trying to grab the REQUEST from self any more -- just doesn't make sense to me. Also we have now the default wiki_type as "basic". (Sascha Welter) * #1332 - make manage_addWiki more programmatic + test. We still grabbed the REQUEST and thus got a redirect at the 2nd chance. Now we're doing the same check as on the 1st test and also return the new id if we don't redirect. Added a test too. (Sascha Welter) * Recursively add files/folders on addWikiFromFs. This is used for "nautica" style templates. It's now possible to use templates e.g. from openwebdesign.org without having to "unroll" images into a flat structure. Also we now can set document titles and parents from the filesystem pages. (Sascha Welter) * #1331, #1186 - last_edit_date / creation_date timestamps now in ISO6801. We changed the timestamp format for last_edit_date and creation_date to conform to ISO8601, in order to save time zone information along with it. Special care is taken to upgrading old timestamps in Zope's DateTime's ISO() format. (Sascha Welter) * update stx code, may work better with zope 2.10 * revisionInfoFor -> revisionInfo * inPlone method Translations * no updates

1 0

Announcing zopeproject 0.4
by Philipp von Weitershausen 16 Sep '07

16 Sep '07

zopeproject makes it easy to get started with a web application based on Zope eggs, zc.buildout and WSGI/Paste. If you're not familiar with this world yet, zopeproject is your easy entry to it. If you are, zopeproject will save you lots of typing up the boilerplate. Why eggs? --------- Because they are a great way to distribute Python software and declare its dependencies. Zope 3.4 is completely distributed as individual eggs and will from now on be developed as such. What's zc.buildout? ------------------- It's a tool for repeatable deployments that's configuration-file driven. You tell it "install these eggs for me, create this script and let me develop packages in this directory" and it will go ahead and do all that. Over and over again, if necessary, and for everybody who wants the same setup as you (which is great for teams). What are WSGI and Paste? ------------------------ WSGI is a Python standard for web applications and web servers. It defines how they communicate so that potentially any WSGI application can run on any WSGI gateway (server). Zope has had support for WSGI for a while now, but it has never really been exposed, even though it offers great possibilities such as middlewares. Paste is a collection of related to WSGI. One of its tools, PasteDeploy, is of particular interest. It allows you to plug WSGI applications, middlwares and gateways together using a simple configuration file. zopeproject vs. instances ------------------------- Apart from all the flashy technology that zopeproject brings us, it also implies a big conceptual change in the way we develop web applications with Zope. In the world of regular instances, Zope is the server and the application. Your code is just like a plug-in:: +------------+ +---------+ | Zope | runs |your code| |server & app| ----> | (plugin)| +------------+ +---------+ Even though we've been doing it for years ("Products" ring any bells?), I think this is backwards and accounts for much of the irritation people coming to Zope have. With zopeproject's approach, *your code* is the application. The web application, to be precise. And it *happens* to use Zope. As a library:: +------------+ +-------------+ +---------+ |WSGI gateway| serves | your code | uses | Zope | | (server) | ------> |(application)| ----> |libraries| +------------+ +-------------+ +---------+ Zope isn't the center of attention anymore, your application is. Even better, you can choose how much of Zope you'd really like to use. You may compare this approach to a GUI application that happens to use some sort of GUI framework to get some widgets on the screen, but otherwise it's just like any other, real application. So how does it work? -------------------- It's pretty easy. All you need to do is install zopeproject first. You don't need to install Zope for this, zopeproject will do that for you later. Note that you will have to have setuptools installed for this to work (it provides the easy_install script):: $ easy_install zopeproject Depending on where and how you installed Python, you may have to prefix this command with "sudo" to gain privileges for installing packages globally. Now you can create a new web application:: $ zopeproject WebApp Much like with mkzopeinstance, you'll be asked a couple of questions. The last question concerns the central download location for eggs (which will include the Zope eggs). After the questions, zopeproject will create a 'WebApp' directory with some initial directory structure, as well as download and install the Zope eggs. To start the application, go to the newly created directory and invoke the server:: $ cd WebApp $ bin/paster serve deploy.ini You may also use the webapp-ctl script which works much like zopectl:: $ bin/webapp-ctl fg You will then be able to go to http://localhost:8080 and see the default Zope screen (The standard boilerplate simply uses the Zope 3 default, after all. It is now up to you to change that.) More information and feedback ----------------------------- For more information, please refer to zopeproject's homepage on PyPI: http://pypi.python.org/pypi/zopeproject I'm very much interested in getting your feedback. Please direct questions that are of public interest to the zope3-users(a)zope.org list. Bugs may be reported in Launchpad: https://launchpad.net/zopeproject. -- http://worldcookery.com -- Professional Zope documentation and training

1 0