I had included some sample code of what I am doing. I added the disposeChildren method to qx.core.Object, this is not a current method. I have a few other methods that I added to Object as well, but they are all similar to disposeChildren.
JimOn 9/25/06, Sebastian Werner <[EMAIL PROTECTED]> wrote:
as I understood Christians code he does not add new properties and
methods to object instances. He just add them to a already defined class.
Please correct me if I'm wrong.
I'm doing the same thing with the current rev.
Adding and modifying properties and methods (including modifiers) to a
alre
Hi John,Have a look at qx.client.Builder - it looks like it can construct a Qx app from XML.SimonJohn Comerford <[EMAIL PROTECTED]> wrote: Hi Folks,I am looking new to qooxdoo, ajax and I am still a bit green when it comes to JS so excuse me if this is a stupid question. I am putting together an a
Hi Simon,
it must be a parent of the window, this is the case, why the window gets
the click event to. Just to be beneath the window shouldn't be enough.
Have you also discovered such a problem?
However I have took a look at your example. The window should definitely
stop more events. Just bec
Hi Folks,
I am looking new to qooxdoo, ajax and I am still a bit green when it
comes to JS so excuse me if this is a stupid question. I am putting
together an application. I want to send it XML and have the client side
parse the XML. I am using RemoteRequest to send the request to the
serve
Jim, we talk about properties here, but right, this will affects fields
and methods, too.
Do you only fix properties to fulfill your custom needs or do you add
stuff, too?
Cheers,
Sebastian
Jim Hunter schrieb:
> I add both fields and methods to base classes. Here is an example of one
> of t
Folks,
This is driving me crazy. Maybe I'm too tired, but I can't seem to
get this right.
Using latest svn of qooxdoo.
I'm building a dynamic shared calendar as part of a larger enterprise project.
I'm loading a set of 6 tab panes from javascript created by PHP. In
the example code below, I've
Hi Sebastian,I have updated to 0.6.2-pre (r4314) and I can still observe the unexpected behaviour in both Firefox 1.5.0.7 and IE 6.0.2800.1106CO on a Windows 2000 5.00.2195 service pack 4 machine.I have attached a small test page that is based on test/window_2.html. If you drop this file straight
Sebastian Werner schrieb:
Hi Christian,
please explain what are your exact use cases. Do you just add properties
e.g. IDs etc. or do you even modify them? To you attach modifiers? Do
you do this on instance level or on prototype level?
Cheers,
Sebastian
Hi Sebastian, have a look at the
I add both fields and methods to base classes. Here is an example of one of the methods that I use all over my application (I use the disposeChildren() function everywhere to remove objects from the system as removeAll() does not work as detailed in many posts):
qx.Proto = qx.OO.classes["qx.core.Ob
Hi Christian,
please explain what are your exact use cases. Do you just add properties
e.g. IDs etc. or do you even modify them? To you attach modifiers? Do
you do this on instance level or on prototype level?
Cheers,
Sebastian
Christian Boulanger schrieb:
> Hi Sebastian,
>
> thanks for you
Hi Sebastian,
thanks for your input. I can only speak for myself, but my interest as
developer is to work with the existing classes instead of subclassing
them as new ones. This is much more flexible and allows me to extend the
behaviour of my application without having to rewrite a single line
OK, lets me explain the benefits of this new version, when it comes, and
let us find solutions for your needs. Sometimes it's not the best
solution to try to keep an existing system, especially when they have
some design issues. It might be better to reinvent the wheel in some
cases. And we def
Hej Christian!
Are you still struggling? Forget to migratewe have tried to do it in
house. The result: too costy Additionally, there are too many issues
we do not accept with the new version. Good luck in your struggling, but
the question is if you ever will be ready with version 1.
We ha
Sebastian Werner schrieb:
>
> I just mention this, because this will not work in the future. The plans
> for a new property system doesn't allow the dynamic addition of
> properties to previously defined classes.
>
> Maybe it's better to enhance the other properties to make it possible to
> use
I have run into this before but thought I would let someone know. In IE, if there are no focused objects, like when a page is first rendered, and you hit a CTRL or ALT or SHIFT key you will get a _javascript_ error "this.getFocusRoot
() is null or not an object". This does not happen with FireFox o
I would like to chime in and say that if you remove the ability to add properties to already defined classes it will completely blow my program up. I have added many properties to many objects and I do it at run time so that I don't have to manage my custom code as opposed to the SVN code. Right no
Christian Boulanger schrieb:
> Sebastian Werner schrieb:
>> Christian Boulanger schrieb:
>>
>>> Sebastian Werner schrieb:
>>>
>>>
However I would like to mention again, that this is not a good idea.
Please use the userData support instead of custom runtime added properties.
Sebastian Werner schrieb:
> Christian Boulanger schrieb:
>
>> Sebastian Werner schrieb:
>>
>>
>>> However I would like to mention again, that this is not a good idea.
>>> Please use the userData support instead of custom runtime added properties.
>>>
>>> obj.setUserData("myproperty", "the
Howdy,
absolutely right, the API at various places could be easier and more
intuitive for the application developer. Please see the corrensponding
entry in Bugzilla:
http://bugzilla.qooxdoo.org/show_bug.cgi?id=116
Some of the your widget examples could need a specific mapping to hide
internal
Christian Boulanger schrieb:
> Sebastian Werner schrieb:
>> Christian Boulanger schrieb:
>>
>>> Wouldn't a qx.OO.setProto("qx.core.Object") method be useful, which does
>>> the first two lines, in order to save some typing? This method could
>>> return qx.OO, so one could write
>>>
>>> qx.OO.
Sebastian Werner schrieb:
> Christian Boulanger schrieb:
>
>> Wouldn't a qx.OO.setProto("qx.core.Object") method be useful, which does
>> the first two lines, in order to save some typing? This method could
>> return qx.OO, so one could write
>>
>> qx.OO.setProto("qx.core.Object").addProperty
[EMAIL PROTECTED] schrieb:
> Hi Sebastian,
>> Hi Alessandro!
>>
>> Thank you for your patch. I've slightly modified your idea. I've added
>> "block" to the separator statements, but I have not extended not_after
>> because this will otherwise change the idea behind this list (and I'm
>> not sure
Hi Sebastian,
> Hi Alessandro!
>
> Thank you for your patch. I've slightly modified your idea. I've added
> "block" to the separator statements, but I have not extended not_after
> because this will otherwise change the idea behind this list (and I'm
> not sure if this is the correct place). I t
Thank you Alex.
I think I've found the problem: I'm setting the backgroundcolor of the
textfields initially to white. This stops the behaviour of the
textfield in FF getting a gray background if it is disabled.
So a clear solution would be to have two properties for the
backgroundcolor: backG
Hello all,
I try to use the widget qx.ui.ListView :
*** ListView creation and fill with data
var ld=[];
for (i=0;i<10;i++){
ld.push({
COL1 : { text : "TEST1" },
COL2 : { text : "TEST2"},
COL3 : { text : "TEST3" },
});
}
var lc = {
COL1 : { label : "myCol1", width : 120, sortable: true, type : "
The idea behind: i need the textfields to change their background-color
on focus/blur. So i did following:
var theme =
qx.manager.object.AppearanceManager.getInstance().getAppearanceTheme();
var apar = theme._appearances['text-field'];
if(apar)
{
var focusinBgColor = new
Working with revision 4269 - no problems(neither FF nor IE).
Cheers,
alex.d
> Hello List!
>
> In my application I need to enable or disable textfields. Having a given
> textfield tf I have to do a simple:
>
> tf.setEnabled(false);
>
> in order to disable the textfield. If the textfield does n
I think I've figured it out. If you ever set an inner division with dimensions greater than the parent division, the parent dimensions are ignored. Further, "100%" doesn't seem to work either.Thanks!
MikeOn 9/25/06, Sebastian Werner <[EMAIL PROTECTED]> wrote:
Hi Mike,please create a new qooxdoo d
Title: AW: [qooxdoo-devel] Visual representation of disabled
qx.ui.from.TextField
The bug I’ve reported seems to be
fixed in svn.
Best Fabian
Von:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Im Auftrag von Fabian Jakobs
Gesendet: Montag, 25. September
2006 15:15
An: qooxdoo
Title: AW: [qooxdoo-devel] Visual representation of disabled
qx.ui.from.TextField
Yes it has been fixed. I reported the bug to bugzilla:
http://bugzilla.qooxdoo.org/show_bug.cgi?id=174
Fabian Jakobs schrieb:
The bug I’ve
reported seems to be
fixed in svn.
Best F
Title: AW: [qooxdoo-devel] Visual representation of disabled qx.ui.from.TextField
Hello Dietrich,
it looks like this is a problem with the Internet Explorer. Firefox grays the textbox out.
This demo seems to expose another bug. The radio button and the check box cannot be disabled. In FF I
Hello List!
In my application I need to enable or disable textfields. Having a given
textfield tf I have to do a simple:
tf.setEnabled(false);
in order to disable the textfield. If the textfield does not contain any
text the user is not able to visually determine if the textfield is
enabl
Hi Alessandro!
Thank you for your patch. I've slightly modified your idea. I've added
"block" to the separator statements, but I have not extended not_after
because this will otherwise change the idea behind this list (and I'm
not sure if this is the correct place). I think the idea from you be
Looks good. Applied to SVN. Revision 4334.
Thank you for your on-going support.
Cheers,
Sebastian
Alessandro Sala schrieb:
> Hi sebastian,
>
> I think I've found another bug, this time in treegenerator.py: when
> an expression starts with a pre-increment or pre-decrement operator
> and begins
Looks good. Applied to SVN. Revision 4334.
Alessandro Sala schrieb:
> Hi Alex, Sebastian,
>> That works, but it doesn't look really nice, because i have large
>> arrays with objects that describe various widgets and regular
>> expressions belong to it. Is there any way to patch this issue in
>
Hi Simon,
I don't think that such a new behavior is a good idea to integrate into
a class like Window. Maybe you can, instead of directly modify Window,
implement such a feature inside a child class.
Cheers,
Sebastian
Simon Bull schrieb:
> Hi All,
>
> Attached is a demo of a window feature
Christian Boulanger schrieb:
> Dietrich Streifert schrieb:
>> Try this instead:
>>
>>
>> var constructor = qx.OO.classes["qx.core.Object"];
>> qx.Proto = constructor.prototype;
>> qx.OO.addProperty({ name: "myproperty", type:
>> qx.constant.Type.STRING, defaultValue: null});
>>
> Wouldn't a
Hi Mike,
please create a new qooxdoo demo and try to integrate the problematic
code into it. But please try to keep it small and clean (without any
Ajax and Effect calls). Maybe this will help us to understood your problem.
Cheers,
Sebastian
Mike Crowe schrieb:
> OK, this is complex, so I'l
Hi Simon,
I don't exactly understand your problem. I have just played some minutes
with the window demo and it seems to work well. However I have added
some more event propagation stop calls to some critical events. Maybe
this fix your problems. Otherwise please tell us more details e.g.
brows
Hi Sebastian,I noticed in 0.6.1 (r4314) that the behaviour of qx.ui.window.Window resizeSouth and resizeEast seems to have a small bug. I tried it with all the resizeMethods. Resizing the window edge north or west works perfectly. When you mousedown and drag a window edge south or east, the final
Yes it works. Thank you Alessandro.
Sebastian, will you apply this patch, or should i wait with
"re-back-constructing" my code?
Cheers,
alex.d
Hi Alex,
Sebastian,
That works, but it doesn't look really nice,
because i have large arrays with objects that describe various widgets
and regula
42 matches
Mail list logo
