On Sat, Mar 1, 2008 at 7:20 PM, Martin Aspeli [EMAIL PROTECTED] wrote:
(1) Why is the line
five:registerPackage package=. initialize=.initialize /
added -- isn't this only to allow a package to be installable as a Zope2
product? Is this needed for plone.app.portlets?
It
Martijn Pieters wrote:
On Sat, Mar 1, 2008 at 7:20 PM, Martin Aspeli [EMAIL PROTECTED] wrote:
(1) Why is the line
five:registerPackage package=. initialize=.initialize /
added -- isn't this only to allow a package to be installable as a Zope2
product? Is this needed for
Thanks to all the hard work from the PLIP authors we have finished
merging all the PLIPs in the Plone 3.1 tree. A total of 16 PLIPs
have been merged:
#184: Include more/improved portlets (Jon Stahl)
#195: Support product dependencies (Wichert Akkerman)
#200: Kupu formlib widget (Martin
On Sun, Mar 2, 2008 at 12:57 PM, Wichert Akkerman [EMAIL PROTECTED] wrote:
Or when you want the quickinstaller to be aware of your package.
Are we talking about the same thing here? The initialize attribute
isn't needed for the quickinstaller, only the five:registerPackage
element, I think.
--
You missed #217 - Workflow lookup by Adaptation, which is merged.
On Sun, Mar 2, 2008 at 6:12 AM, Wichert Akkerman [EMAIL PROTECTED] wrote:
Thanks to all the hard work from the PLIP authors we have finished
merging all the PLIPs in the Plone 3.1 tree. A total of 16 PLIPs
have been merged:
Previously Alec Mitchell wrote:
You missed #217 - Workflow lookup by Adaptation, which is merged.
Thanks, I've added it to the 3.1 release on plone.org and updated the
workflow state for the PLIP there as well.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
