Hello All,
I've managed to migrate my app from qooxdoo 0.7
(branches/legacy_0_7_x/qooxdoo) to 1.2 pre (trunk) and after a hard
battle and some refactoring it works.
This is a health care patient data management app which is focused on
regional anesthesia. The goal is to collect data with respect to
complications during patient treatment.
This means we have a LOT of input fields. In the patient chart we have
approx.:
110 checkboxes
260 radiobuttons
100 textfields/textareas
44 comboboxes
The patient chart form is generated from a XML-schema via xsl
supplemented by an additional fields dependency description XML-File
(nowaday I suppose we call this a domain specific language?!?!).
The form is placed within a window.
Here some manually measured times for the first opening of the window
(dom creation and data loading):
qooxdoo 0.7 qooxdoo 1.2pre
FireFox 3.6 ~1sec ~3 sec
IE 8 ~2 sec ~9 sec
For FF 3.6 the additional 2 seconds are not dramatic but for IE 8
waiting additional 7 seconds for the first start of the form is not
acceptable.
There is no benefit for my customers in using the qooxdoo 1.2 version of
the app. This gives no additional functionality, quite the opposite: it
is, from their impression, MUCH slower. Additionally checkboxes and
radiobuttons are to small compared to the native checkboxes and
radiobuttons in 0.7.
I took a look at how form fields are rendered in qooxdoo 0.7 and
compared that to 1.2pre. I noticed the following differences regarding
the number of created DOM elements:
qooxdoo 0.7 qooxdoo 1.2pre difference
checkbox 2 DIV, 1 INPUT 6 DIV, 1 LABEL 4 elements
radiobutton 2 DIV, 1 INPUT 6 DIV, 1 LABEL 4 elements
textfield 1 DIV, 1 INPUT 4 DIV, 1 INPUT, 1 LABEL 4 elements
For my form this means that (without comboboxes) additional ~ 1600 dom
elements are created in 1.2pre compared to 0.7. I'm using the classic
theme with this app so I suppose execution times would be even longer
using the modern theme because of the heavily used gradient background
images and more complicated decorators.
Now my questions are:
Are my thoughts regarding the increase in execution time reasonable?
How can I reduce the amount of created dom elements?
Why does a textfield use additional 4 dom elements in 1.2pre compared to
0.7?
Is it possible to re-implement native checkbox and radiobutton widgets
from qx 0.7 as a replacement of the 1.2pre versions?
Any ideas, comments are very welcome.
Best regards...
--
Mit freundlichen Grüßen
Dietrich Streifert
--
Visionet GmbH
Firmensitz: Am Weichselgarten 7, 91058 Erlangen
Registergericht: Handelsregister Fürth, HRB 6573
Geschäftsführer: Stefan Lindner
------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
