[Framework-Team] Re: PLIPs for 3.1

[Andreas Zeidler]

On Dec 2, 2007, at 6:19 PM, Martin Aspeli wrote:
> Hi team,

hi martin,

> I'm submitting the following PLIPs for Plone 3.1.

here's my (late) review of the plips.  i've intentionally tried to  
read and comment on them first before reading the corresponding  
threads, so sorry for potential redundancies... :)

> 1. http://plone.org/products/plone/roadmap/184 - Ship additional  
> portlets

+1 as this is purely add-on functionality and contains no risks other  
than maybe confusing users if done in a non-intuitive way.  having  
that said i think the "use document as portlet" approach makes sense,  
since it would save us from a lot of extra code or duplication.  an  
easy way to turn a "page" or even an arbitrary content item into a  
portlet and thereby (optionally) hide it from the navigation and  
folder listing would be great to have, although the latter, i.e. the  
generic assignment, might require too many changes for 3.1.

> 2. http://plone.org/products/plone/roadmap/200 - Kupu formlib widget

+1 on that as well as it's badly needed to get the formlib story  
going.  being an add-on as well i don't see any risks, either.

> http://plone.org/products/plone/roadmap/201 - Improved  
> UberSelectionWidget

the same goes here, so +1.  or should i abstain from voting since i'm  
involved?  hmm, anyway, i've got no objections.

> 3. http://plone.org/products/plone/roadmap/202 - KSS inline editing  
> and validation for formlib forms

+1 as well, as it's also purely add-on functionality and needed to  
make formlib a real alternative.  two minor notes, though:  the  
example uses both "kssattr:renderStructure" and "kssattr:structure",  
which is probably just a typo, right?  if not, i think one should be  
renamed to avoid confusion.  and how about including the "@@" when  
referring to the edit form in order to make it a bit clearer it's a  
view?

also, one of the deliverables here should be some documentation and  
examples on how to use this.  this also goes for the above plips, but  
imho it's more important here, since it uses those conventions, some  
of which might be hard to grasp without more detailed info.  so +1 on  
making this an explicit deliverable.

> 4. http://plone.org/products/plone/roadmap/203 - Manage portlet  
> assignments with GenericSetup

another add-on, this time enhancing the GS story, so again +1.   
however, i think this should definitely also include an export  
handler, because it's also targeted towards site integrators and  
admins, who would probably like to make assign their portlets using  
the ui and then dumping the current state into a theme product.

personally i think this is one of the great possibilities with GS  
anyway — no need to write code or even xml, just make your changes and  
diff/export them.  it'd be awesome to extend the comparison feature to  
be able to download a minimal version containing only the changed  
values, btw, but that's a different plip... :)

> 5. http://plone.org/products/plone/roadmap/204 - Manage content  
> rules using GenericSetup

+1 for the same reasons as above.  but again, imho and export handler  
should be included right from the start to make it easier for people  
to get going.  this would also make documentation a not so important  
deliverable, even though a short howto would be very helpful, of  
course.  the same goes for #203.

so much for these, more to follow... :)


andi

--
zeidler it consulting - http://zitc.de/ - info at zitc.de
friedelstraße 31 - 12047 berlin - telefon +49 30 25563779
pgp key at http://zitc.de/pgp - http://wwwkeys.de.pgp.net/
plone 3.0.4 released! -- http://plone.org/products/plone

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
URL: <http://lists.plone.org/pipermail/plone-framework-team/attachments/20071213/ed90d6c5/attachment.sig>