[Framework-Team] Middleware render on Plone 5

Giacomo Spettoli giacomo.spettoli at gmail.com
Tue Oct 1 15:22:16 UTC 2013

+1, I totally agree with this approach. I think it's the natural evolution
of rendering contents since diazo came out. Actually I already thought on
this for a while, and my idea was to switch to an xml output but that would
be hard to achieve and the advantages would be very few. So html (5) it's
fine too.

On Oct 1, 2013 12:05 PM, "Martin Aspeli" <optilude+lists at gmail.com> wrote:

> Hi,
> On 1 October 2013 14:03, Ramon Navarro Bosch <ramon.nb at gmail.com> wrote:
>> Since we are moving to Diazo I have the bad feeling that rendering twice
>> the page is a waste of energy and a possible missunderstanding for
>> integrators / developers ( we will have the frontend, the backend of
>> widgets, the native rendering ... )
>> During these days in Brazil, we've been discussing if it's possible to
>> change the main_template to export the structure of plone instead of a
>> rendered page, different sections with the viewlets, with the portlets, the
>> content, .... and on diazo rules it would be much easier to define the
>> rules. As right now is the moment to discuss about this subject(diazo theme
>> is really in early step and plone5 is a possible target to change this), my
>> idea is to talk about it today at FWT meeting if it's ok with you.
> So to check my understanding: you are saying main_template exposes
> something very simple, e.g. a pile of divs with sensible ids, and then
> Diazo makes it visually appealing?
> If so, that makes sense to me, at least once we have good "out of the box"
> Diazo themes.
> Martin
> _______________________________________________
> Framework-Team mailing list
> Framework-Team at lists.plone.org
> https://lists.plone.org/mailman/listinfo/plone-framework-team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.plone.org/pipermail/plone-framework-team/attachments/20131001/21e1daab/attachment.html>

More information about the Framework-Team mailing list