Hi geo!
The problem is that every time you call initPopUpMenuAd() you create new
objects: one PopUp and one Button. Why don't you just create them once
and just update the label and command?
I saw, that you save your widgets in the "widgets" map. Just save the
menu button too to gain easier a
Thanks for help
Sebastian Werner wrote:
>
> Try out getDocumentLeft/getDocumentTop:
>
> http://demo.qooxdoo.org/current/apiviewer/
> #qx.event.type.Mouse~getDocumentLeft
>
> Sebastian
>
>
> Am 11.09.2008 um 18:33 schrieb Grykar:
>
>>
>> Thanks a lot.
>>
>> I have one more question regardi
yep, pure OO beauty :)
Sebastian
Am 11.09.2008 um 21:27 schrieb Jean-Baptiste BRIAUD - Novlog:
OK, so its pure OO approach and there is no "hack" like splitting
the code of one class into several file except by usiing Mixin but
the doc state that the code in Mixin should be generic.
Any
OK, so its pure OO approach and there is no "hack" like splitting the
code of one class into several file except by usiing Mixin but the doc
state that the code in Mixin should be generic.
Anyway, pure OO approach is perfect :-)
On 11 Sep 2008, at 21:18, Sebastian Werner wrote:
You can use
You can use Mixins in your application class as well and this way move
parts of your code out of the application code. But even better would
be to break your class into multiple classes where each one does a
specific part (and this well ;))
Sebastian
Am 11.09.2008 um 21:15 schrieb Jean-B
I didn't know Mixin but I still have a question : can I split the
application class file in several files without creating other classes?
On 11 Sep 2008, at 20:56, Sebastian Werner wrote:
Jean-Baptiste,
you can have a look into our documentation. Mixins would be a good
concept as well.
F
Jean-Baptiste,
you can have a look into our documentation. Mixins would be a good
concept as well.
For a good introductioral read start with:
http://qooxdoo.org/documentation/0.8/oo_introduction
followed by:
http://qooxdoo.org/documentation/0.8/mixins
Hope this helps.
Sebastian
Am 11.0
OK, but how do you do that ?
That was my question :-)
Is there an include concept in qooXdoo or js ?
Is creating classes the only way to break element into files ?
On 11 Sep 2008, at 20:36, Jim Hunter wrote:
Breaking up a large file or a large method up into smaller ones is
rarely a bad ide
Breaking up a large file or a large method up into smaller ones is rarely a
bad idea. It will make editing easier and provide more clarity in your code.
My application resides in about 35 of my own classes, each one with their
own file.
Jim
On Thu, Sep 11, 2008 at 11:32 AM, Jean-Baptiste BRIAUD
Hi,
I'm now having a big (I feel too big) javascript file.
I'm wondering how to improve the structuration and modularity.
For example, just the menu there is a fair amount of line.
SHould I do a class just for that and use it on the application class ?
This would allow me to split in 2 files in t
Try out getDocumentLeft/getDocumentTop:
http://demo.qooxdoo.org/current/apiviewer/
#qx.event.type.Mouse~getDocumentLeft
Sebastian
Am 11.09.2008 um 18:33 schrieb Grykar:
>
> Thanks a lot.
>
> I have one more question regarding positioning - how to check
> position of
> mouse cursor inside th
Thanks a lot.
I have one more question regarding positioning - how to check position of
mouse cursor inside the mouse hadler. I use e.getPageX() and e.getPageY() in
0.7
Karol
Sebastian Werner wrote:
>
> Easy: As I mentioned the button must be layouted and visible first. At
> the moment you
Easy: As I mentioned the button must be layouted and visible first. At
the moment you call ''getBounds'' it is only a in-memory widget. Nothing
applied to the DOM yet.
You can listen for the resize event as the resize event is the first
time the widget is layouted:
button1.addListener("resize"
I don't know why part of code below doesn't work properly.
var button1 = new qx.ui.form.Button("First Button");
this.getRoot().add(button1, {left: 100, top: 100});
alert(button1.getBounds());
button1.getBounds() returns null
Karol
Sebastian Werner wrote:
>
> The position detection require
Hello Jonathan,
I cannot reproduce this problem by using legacy 0.7.3. It seems that this
problem was fixed some time ago.
Thank you!
Best regards,
Denis
--
View this message in context:
http://www.nabble.com/How-to-avoid-appearance-of-caret-in-TextField-in-Internet-Explorer-tp19145371p194363
The position detection requires that the widget is visible and rendered.
You can use:
widget.getBounds() which returns a map of sizes and positions. The
position is relative to the next parent.
widget.getContainerLocation() returns a map with absolute coordinates
from the left/top corner of th
I would like to know in relation to the next parent.
I suppouse if I know relation to the next parent I can find absolute
position in a few steps but if there is one step method to find it please
let me know.
Karol
Sebastian Werner wrote:
>
> Do you mean absolute position to the document o
Do you mean absolute position to the document or in relation to the next
parent?
Sebastian
Grykar schrieb:
> Hi
>
> There is easy way to getLeft, getRight, getTop, getBottom in 0.7. How to do
> the same in 0.8 ?
>
> Thanks,
> Karol
-
Oleksiy Golovko schrieb:
> Sebastian
>
> Thank you for the explanation, but I'm not yet accustomed to new qx
> layouting system, so I often think - are 'width' and 'height' widget
> properties or layout ones. Yeah, I've read the ui_layouting aricle but
> seems that I want to re-read it once agai
Hi
There is easy way to getLeft, getRight, getTop, getBottom in 0.7. How to do
the same in 0.8 ?
Thanks,
Karol
--
View this message in context:
http://www.nabble.com/How-to-get-position-of-widget-in-0.8--tp19435030p19435030.html
Sent from the qooxdoo-devel mailing list archive at Nabble.com.
Sebastian
Thank you for the explanation, but I'm not yet accustomed to new qx
layouting system, so I often think - are 'width' and 'height' widget
properties or layout ones. Yeah, I've read the ui_layouting aricle but
seems that I want to re-read it once again :)
Regarding the moving/resizing w
Please also keep in mind that percent dimensions keep percent. So using
them might break the support for resizing and moving of such a window.
You can disable these if this is OK, otherwise mhh, you are maybe out of
luck for the moment.
Sebastian
Sebastian Werner schrieb:
> Just saw you add
Just saw you add it to the root of your application. If you use a
traditional Standalone application you can define a percent width at the
insertion time of the window as a so-named layout property e.g.
app.getRoot().add(dlg, { width : "30%" });
You may also double check that you have read this
You could add some methods to the Window class to support environment
variables (such as the container etc) to compute the width and height
according to given percent parameters, no ?
-
This SF.Net email is sponsored by the Mob
Dimensions can only be given using pixels. Other dimension values depend
on the layout you use inside the parent widget of the window.
The HBox, VBox, Dock, Canvas layouts supports percent dimensions. But
all other do not. Where do you insert the window to?
Sebastian
Oleksiy Golovko schrieb:
Hi Chi Mo,
Thomas is on vacation for the next two weeks. Hope you can wait for your
answer a bit. I send him a reminder to your post so he do not overlook
it. Maybe some other people on the list could help. My own experience
with the Simulator is quite nonexistent :)
Sebastian
Chi Mo schrieb:
>
I think this is already answered off list, but for the archive. Yes,
it's possible using:
qx.bom.Label.getHtmlSize or getTextSize
It also supports styles to be applied onto the label e.g. specific fonts
(second parameter)
Sebastian
Derrell Lipman schrieb:
> I need to determine the width of
Hi
I'm trying to set window dimensions using 'NN%'-like form without any
success. The only effect I see is that "X"-close button got moved closer
to the window title text. Here steps to reproduce:
var dlg = new qx.ui.window.Window('Error', null)
.set({
//wid
Hi Thomas,
Recently I upgraded to Window Vista. In my old PC(Window XP), the test
script works fine in both IE7 and Firefox2. In the new PC(Window Vista), the
script is still work in Firefox 2. But here comes an error in IE7. It's a quite
simple script, something like:
sel.qxClic
> But I use the EventListener "contextmenu" to display my context
> menu in the tree, I also use a function to create the customized
> menu with this case code I don't know where place the
> "this.remove".
I remove the old context menu when a new one is constructed. That way you
know that it's
30 matches
Mail list logo
