[Plone-conference] Openspace: growing plone | as a brand

[Asko Soukka]

Johannes Raggam wrote:
> i remember you mentioning that mosaic isn't compatible with the current
> development on mockup/new resource registry... if so, we should fix it.
> let's talk about this at the ploneconf. when are you coming?

Hi Johannes,

the layout storages and composition is already fully compatible with 
Plone 5, but

a) plone.app.widget dependency should be refactored to be Plone 4.x only
    (and it should import widgets' base class from CMFPlone in Plone 5)

b) yes, css and jsregistry may need fixes, because the current Mosaic
    expects the latest p.a.widgets release

c) layout editor pattern is already inside p.a.mosaic, but it should
    registered properly for the new registries

but these would only fix the integration part (which already worked for 
Plone 5 before the new registries), but the layout editor would still be 
somewhat broken because of CSS differences between Plone 4 and Plone 5.

Cheers
Asko

>
> johannes
>
> On Mon, 2014-10-27 at 18:21 +0200, Asko Soukka wrote:
>> Hi all,
>>
>> Martin Aspeli wrote:
>>> Of course we tried this in 2007 when Alex and others invented Deco (the
>>> original, bold, clean and beautiful concept) and that may well have done
>>> it. I still think that it's better than anything else out there even
>>> now, although the gap is narrowing.
>> I hope that somone could bring the original "Deco+UI proposal.pdf"
>> online again.
>>
>> As you may know, Mosaic Sprint Barcelona worked hard to fix the "boring
>> legacy stuff" to give the Deco vision a yet another change as Plone
>> Mosaic. So, with plone.app.mosaic (and its versions of plone.app.blocks
>> and friends), it's possible to use these new style layouts side by side
>> legacy templates, already with Plone 4.3+.
>>
>> And how is Mosaic relevant to this discussion? The Deco/Mosaic vision
>> describes the UI layer using such terms and technologies that it's no
>> longer tied to the current Plone technologies. Deco/Mosaic page
>> composition (be it plone.app.blocks, Varnish ESI, or something else)
>> does not really need to care where do those layouts and tiles come from.
>>
>> So, as long as used tiles are not interdependent, their backend could be
>> replaced one by one with any fancy new technology (of course, it would
>> help, if we could make Plone ZODB accessible from Python 3 code).
>>
>> Cheers,
>> Asko
>> _______________________________________________
>> Plone-conference mailing list
>> Plone-conference at lists.plone.org
>> http://lists.plone.org/mailman/listinfo/plone-conference
>