Hi again.
Wichert Akkerman wrote:
If there are no objections I think we should merge these four PLIPs into
trunk in the next couple of days:
PLIP 8 - Versioning
PLIP 118 - Portlets engine based on PlonePortlets and Viewlets
Hi.
Wichert Akkerman wrote:
If there are no objections I think we should merge these four PLIPs into
trunk in the next couple of days:
Aren't we supposed to have an official vote on what PLIP's we think are
ready for inclusion?
In case anybody agrees with me, here are my votes:
PLIP 8 -
Hi all!
Raphael Ritz wrote:
So the biggest open issue at the moment is probably the move to
using events instead of the 'manage_*' hooks.
At least for CatalogMultiplex and all catalog indexing behavior I was
able to fix this in the meantime. The solution was far easier than I
would have
Hi.
Vincenzo Di Somma wrote:
Conclusion
I think the plips succeeds in its goals, the implementation on the i18n
layer is much clearer now, easy to read and manage and of course it is
reusable.
Thx, I always love to get positive feedback.
Hanno also provides a list of todo
Martin Aspeli wrote:
Hi Hanno,
1. Global configuration:
Currently menus (Actions menu, Workflow menu, ...) are configured in
ZCML and thus immediately available without any installation step.
For an add-on product this means there is no way to unregister a
particular menu and menus added
Hi all,
while it's getting late, I was finally able to review the first PLIP on
my list.
I have added a detailed list of open problems to the bundle itself at
http://svn.plone.org/svn/plone/review/plip142-componentised-content-menu/COMMENTS.TXT.
For those of you not familiar with the PLIP
Hi.
Raphael Ritz wrote:
- I tried to fix 'installTypes' from Archetypes but I didin't
fully succeed. For some plain AT folderish items the default
actions are missing (I tested with MyAddressBook from my tutorial:
the 'Contact' type is OK but the 'AddressBook' type is missing
Hello from the St. Augustin sprint :)
Raphael Ritz wrote:
Hello again,
this is just a service to those of you who do not follow the svn/plone
commits ;-)
2006-09-12 Raphael Ritz ([EMAIL PROTECTED])
My test set-up: Python 2.4.3, Zope 2.10.0b2 release on Linux (FC5)
First
Martin Aspeli wrote:
Raphael Ritz wrote:
What would be really nice to have for our add-on developers:
- a hands-on, fool-proof guide on how to update 3rd-party products
for Plone 3.0. In particular this should contain (pointers to)
instructions on supporting and using
Alec Mitchell wrote:
On 9/12/06, Raphael Ritz
[EMAIL PROTECTED] wrote:
Hanno Schlichting schrieb:
What would be really nice to have for our add-on developers:
- a hands-on, fool-proof guide on how to update 3rd-party products
for Plone 3.0. In particular this should contain
Hi all.
Martin Aspeli wrote:
Hi guys,
I took a look at the PLIPs still remaining. I put some preliminary
names to some of PLIPs, purely along the lines that I thought people
may be interested in. All the ones with ? in front of them are just
suggestions - the other ones are the ones Wiggy,
Hi.
As I'm lazy, I wrote a new template for plone.app projects now as well.
So in step 3 you can also do:
paster create -t plone_app
which will ask you the same question as the plone_core template but adds
a question for the second namespace, which defaults to app :)
Step 4 (svn import)
Raphael Ritz wrote:
First, I think we should really encourage the SoC projects by
defining a time line and process that offers the **possibility**
of getting results from SoC projects into the 3.0 release.
My intention here was to give all the SoC projects a clear statement
that their code
Hi all.
Thx Martin for starting this thread ;)
Before going into details I would like to note some time constraints, as
we agreed on having time and not feature based releases, so we get some
feeling what might be feasible in the time we have:
Plone 2.5
-
January 2006, feature /
101 - 114 of 114 matches
Mail list logo
