portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gonzalo Aguilar Delgado <gagui...@aguilardelgado.com>
Subject Questions about rendering and desktop mode
Date Sat, 21 Nov 2009 22:06:19 GMT
Hi all, 

I realized that current UI implementation performs well but is not
completely async.

Let me explain if I I'm right.

We have two execution modes, ui and desktop.


        System will render everything as usual but custom YUI code will
        be executed
        to allow move, resize, place, etc.  Windows.
        The portlet creation is created in the jetspeed pipeline in
        sequential mode like
        in the static mode.
        Client will hold until everything is created and rendered.
        This is current and default render mode.


        Only basic html is sent to the client. 
        Ajax Toolkit initialization is sent and everything is handled
        with javascript. 
        Client will start to see contents as soon as they are loaded.
        This is obsolete and posibily will not work with new dojo

I suppose that best world is a mix of both were portlets are rendered
empty of content via
a <div> tag and ajax toolkit will take care of move, resize, place,
etc... And load contents

This way page will get at least portlet configuration if something goes
wrong with ajax.

What do you think?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message