On 5 Jun 2010, at 18:06, Petr Kobalíček wrote:
> qxscripts = [
> qxsettings["qx.path"] + "/script/qx-" + qxsettings["qx.mode"] + ".js"
> ];
>
> qxloader.run({
> scripts: qxscripts,
>
> finish: function() {
> // your code here...
> }
> });
That's neater. Thanks! :)
Another question... I have the following code:
qx.Class.define("qxPascal.Application", {
extend: qx.application.Standalone,
members: {
showLabel: function(aParent, aText, aLeft, aTop) {
aParent.add(new qx.ui.basic.Label(aText), {left: aLeft,
top: aTop});
},
main: function() {
this.base(arguments);
var container = new qx.ui.container.Composite();
container.setLayout(new qx.ui.layout.Canvas());
container.setDecorator("main");
var win = new qx.ui.window.Window("Window", null);
win.setLayout(new qx.ui.layout.Canvas());
win.setAllowMaximize(false);
win.setWidth(300);
win.setHeight(200);
container.add(win, {left: 10, top: 10});
this.showLabel(win, "Hello world from qxPascal!", 5,
5);
this.getRoot().add(container, {edge: 5});
win.open();
// --
}
}
})
I put the code within the "your code here..." section. ;)
I saw a bit increasing performance if I moved the "showLabel" to below the
"main". Is member position really affecting performance in qooxdoo (or
qxbuild)? I thought it isn't, but somehow I saw it's slightly different. Or
maybe I did something wrong?
TIA.
-Bee-
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
