Hi Martin, Am Donnerstag 01 April 2010 schrieb MartinWittemann: > congratulations to the product launch. The site is really looking good and > I'm not only thinking of the content. :) > Heiko Stübner wrote: > > - qooxdoo compiled into different parts using the generator and explizit > > includes/excludes for each part to keep the size minimal [core, dombom, > > io] > > Do you already use the new, parallel partloading or is it the old one? > (based on a 1.0.1 or on trunk) Maybe using the new one could bring the > footprint of your app down a bit because the new one does not necessarily > need the event system because its based on callbacks. the "part-loading" isn't based on the qooxdoo part-loader. Instead the page knows through the generated content which parts are needed and adds code to load it. This is due to the fact that qooxdoo is just a small piece of our application-puzzle and has to integrate into the whole system.
And I wouldn't want to miss the event system :-). For example the popup menu
at the top of the page uses pregenerated html and a qooxdoo-class which
controls the state of the popup and uses the qooxdoo event system to attach
the needed events to the html elements.
> Heiko Stübner wrote:
> > - Product-listings and -details use a widget system based on qooxdoo's
> > widgets, stripped down alot but still using qx.html.* internally which is
> > _really_ nice to work with :-) .
>
> Did you use the qx.ui.core.Widget class or did you write your own,
> lightweight widget? Maybe you could share some more details about that,
> sounds really interesting.
it's based on a combination of qx.ui.core.LayoutItem and qx.ui.core.Widget but
heavily dumbed down, i.e. qx.ui.queue.*, decoration and other stuff removed.
Most layout properties come from a css file i.e. the widgets contentElement get
assigned a class-Attribute, so qooxdoo size and position handling is not
necessary. But the widgets provide a neat way of grouping functionality and
accessing
As a small example I have attached a select-widget. It simply encapsulates a
qx.html.Input("select") ContentElement. It can be filled with setOptions(arr)
where arr is something like
[
{ value : 'val', text : 'Optiontext' },
...
]
The appropriate entry can be selected using setValue which also changes the
underlying Input-Element. It fires a changeValue-Event when the user selects
another Element. Using getValue() the currently selected value can also be
retrieved.
Another heavily widget-based feature [released just now] is the function to
filter for specific products by selecting different properties.
It is included for example in Passionata/Passionata BH.
I don't think it is bug free currently but it does look nice :-)
Heiko
--
Nexst4 GmbH
Arndtstrasse 12
01099 Dresden
Tel.: +49 (351) 655 76 70
Fax: +49 (351) 655 76 66
Mail: [email protected]
Geschäftsführer: Alf Thiele, Matthias Schmidt
Sitz der Gesellschaft: Dresden
Handelsregister: Amtsgericht Dresden HRB 27274
Select.js
Description: application/javascript
------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev
_______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
