Hugh.

It was working for me well all the weeks :)

But I am sitting on a 20Mbit connection at home ;) (and mhh, about 
100Mbit here at work ;))

Please open a bug and suggest the timeout increasement there. Gzipping 
will also be an option. But a further split of the files is IMHO not a 
good idea. It is already quite fine grained. Even more files will result 
in slower performance because of the latency which is also relevant.

Sebastian



Hugh Gibson schrieb:
> I was trying to use http://demo.qooxdoo.org/current/apiviewer to look at
> the 0.7 documentation. 
> 
> The new design of the API viewer loads each section as required. I'm
> running on a 512KB ADSL connection, and the default 5 second timeout
> doesn't give enough time for some sections.
> 
> For example, navigate to
> http://demo.qooxdoo.org/current/apiviewer/#qx.ui.form.TextField
> 
> Under the hood, the JS is requesting
> http://demo.qooxdoo.org/current/apiviewer/script/qx.ui.core.Widget.js?noca
> che=1181820020280
> 
> which is 303K, taking 6 seconds or so on my connection. Therefore the
> request is timed out, and no details are shown for that section.
> 
> The default timeout is too short and must be increased for those on "slow"
> connections.
> 
> Having said that, it seems that a huge amount of data is required for
> these sections (maybe anything derived from widget, with a large number
> of inherited entries). 
> 
> Possible ways of reducing the hit:
> 
> 1. zip the data files them - the zipped version of that 303K file is
> around 19K, which is a huge improvement. Only works in IE7 and FF2
> (probably a significant number of users these days).
> 
> 2. Restructure the split of the data files so that each data file doesn't
> contain all the base class information, but has a list of the base class
> files required which can then be requested in sequence, if they're not
> already held in the API viewer. Therefore there would be a 30OK file only
> once (for widget) and all the files for the derived classes would be a
> lot smaller. 
> 
> 3. Combine 1 & 2 - and it would really fly, even for users on very slow
> connections!
> 
> This would significantly improve the usability of the API viewer, an
> important first point of call for anyone evaluating qooxdoo. At the
> moment it is broken, probably for a significant number of users, which
> gives a very bad impression.
> 
> Hugh
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to