Re: [Plone-developers] Deco vs. deco lite vs huh?

[Martin A. <opt...@gm...>]

On 28 May 2012 21:10, Alex Clark <ac...@ac...> wrote:

> And… I've now read all the latest threads on the "it's time to talk
> Plone 5" thread but, I still don't get it. Can someone please take a
> minute to explain to the TL;DR crowd why anyone should care at all about
> Deco (Tiles, Blocks, whatever)?

Didn't my reply to Lennart summarise just that?

> Is it accurate enough to say: Deco == New editing UI (with the old
> monolithic page concept being replaced by a page comprised of
> tiles/blocks.) Or is their more to the story folks should care about?

That's accurate.

The difference between 'full' and 'lite' comes down to what happens to
the rendering of the rest of the page (e.g. do portlets get replaced
by tiles, does main_template get replaced by a bit of HTML with tiles
in it) and how much we refocus Plone's default content type story on a
smaller number of types (e.g. just page + file) with the differences
we see today between news item, event etc being seen more as a
difference of layout and metadata.

> After I wrote the above post, I took a quick look for released packages.
> AFAICT there is nothing called "Deco" in existence (there is however a
> tiles release.) Perhaps the fact that there is no actual release is
> contributing to folks' confusion.

Deco-the-editor lives in plone.app.deco.

The shared toolbar infrastructure required by Deco and plone.app.cmsui
lives in plone.app.toolbar.

The page type behind full Deco lives in plone.app.page.

The page type behind Deco lite lives in plone.app.layoutpage.

Tiles live in plone.tiles and plone.app.tiles (and have been
successfully used without Deco at all).

The rendering engine that can merge tiles into a layout (whether
edited by Deco or not) lives in plone.app.blocks.

Martin