On Mon, Feb 2, 2009 at 4:51 PM, Jean-Baptiste BRIAUD -- Novlog <
j-b.bri...@novlog.com> wrote:
> I didn't had time to read as I would like that virtual widget for
> qooxdoo,
> so I might asked stupid question :-)
>
> I understood the benefit of that virtual widget as not rendering the a
> part of widget that can't be seen (eg : a table with a lot of rows).
> So, what is the point of pre-rendering a widget part that can't be
> seen ?
>
The point of pre-rendering a few rows above and below, or a few columns to
the left and the right of the portion that can be seen is that you can then
scroll smoothly by simply moving the X and Y coordinates of the viewport.
Scrolling can be made as smooth, this way, as if the entire page were
rendered and browser scrollbars were used... yet the benefits of virtual
widgets remain, because NOT all rows and/or columns are rendered; only a few
to any side of the visible area.
My suggestion was to allow rendering all of the rows and columns so that the
same code could be used both for on-screen rendering and for generating
reports that contain the widget. In the on-screen case, only a few extra
rows/columns would be rendered for smooth scrolling. In the printable case,
the entire widget would be rendered and the widget's inner HTML plugged in
to the report.
Derrell
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
