[Product-Developers] plone.app.widgets nightmare

[Philip Bauer]

I still refrain from using plone.app.widgets in Plone 4.3. in production. I had to accept that it is still under heavy development and might need some more time before it's production-ready. There will be a release of plone.app.widgets for the pending 5.0a1-release that should arrive pretty soon. 
Until that is done and we have documentation at https://github.com/plone/plone.app.contenttypes#widgets I would stick with the old widgets. 

Philip

Am 03.03.2014 um 11:44 schrieb Asko Soukka <asko.soukka at iki.fi>:

> Dylan Jay wrote:
>> 
>> You do know plone.app.widgets is still in development and targeting
>> plone 5 right?
>> I wouldn't be seriously trying to use it on plone 4.3
>> 
> -1
> 
> I think, we really should keep p.a.widgets working (and be re-usable in
> add-ons) also an Plone 4.3.
> 
> The widgets work OOTB with built-in types, but it's really hard to
> integrate them into your own add-ons without digging into code for the
> hidden details. And the widgets do require jQuery >= 1.8, which bring
> additional incompatibilities (e.g. p.a.theming's editor does not work
> yet with 1.8).
> 
> Personally I'm waiting p.a.widgets to get more stable before re-learning
> their integration, but I do want to upgrade Plone 4.x sites to use those
> well before Plone 5. (We already have one site running with early alpha
> of p.a.widgets. It works great, but the integration has changed after
> that and I will re-learn it only after widgets get stable enough :)
> 
> -Asko
>> On 3 Mar 2014 18:25, "ajung" <lists at zopyx.com
>> <mailto:lists at zopyx.com>> wrote:
>> 
>>    Hi there,
>> 
>>    we are trying to use plone.app.widgets in a Plone 4.3 project with
>>    Dexterity
>>    since week - but the overall developer experience is more than
>>    frustration -
>>    especially for non-hardcore Plone developers of the team (I am the
>>    coach).
>>    We got various Javascript problems with some other 3rd party
>>    Javascript
>>    modules (that are supposed being compatible with the jQuery
>>    version of Plone
>>    4.3). We basically took a step back and removed stuff that could
>>    possibly
>>    lead to conflict. Now we had a buildout running with some trivial
>>    Dexterity
>>    types and plone.app.widgets worked fine out of the box with the
>>    type. Now a
>>    co-worker added a RichText to his type and
>>    *bbbbbbbbbbbbbbbbbuuuuuuuuuuuuuuuuuuuuuummmm* : yet another JS issue.
>> 
>>    Full error see here:
>> 
>>    https://dev.plone.org/ticket/13893
>> 
>>    <rant>
>>    This is truly frustrating...especially for the other devs - we are
>>    currently
>>    in the we-hate-Plone mode and asking ourselves: why should we use
>>    Plone
>>    again?
>>    </rant>
>> 
>>    -aj
>> 
>> 
>> 
>> 
>> 
>>    --
>>    View this message in context:
>>    http://plone.293351.n2.nabble.com/plone-app-widgets-nightmare-tp7570364.html
>>    Sent from the Product Developers mailing list archive at Nabble.com.
>>    _______________________________________________
>>    Product-Developers mailing list
>>    Product-Developers at lists.plone.org
>>    <mailto:Product-Developers at lists.plone.org>
>>    https://lists.plone.org/mailman/listinfo/plone-product-developers
>> 
>> _______________________________________________
>> Product-Developers mailing list
>> Product-Developers at lists.plone.org
>> https://lists.plone.org/mailman/listinfo/plone-product-developers
> _______________________________________________
> Product-Developers mailing list
> Product-Developers at lists.plone.org
> https://lists.plone.org/mailman/listinfo/plone-product-developers

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.plone.org/pipermail/plone-product-developers/attachments/20140303/7745210f/attachment.asc>