Jenec schrieb:
> Hi, I have a little question for you:
> I need to get an object, which has fired an event.
>
> I place a Listener:
>
> this.addListener("someName", function(e) {
>someObject.someMethod(); //someObject is undefined here
> }, this);
>
> Then I fire a DataEvent using:
>
> qx.
Can someone post an example of how to use the "packages" feature in the 0.8
build framework. I have read the online docs but cannot seem to get it to
work.
My config.json contains a "packages" top level key
"packages" :
{
"parts":
{
"qooxdoo" : [ "qx.*
Bug 1925 ...
Cheers,
Fritz
On Tue, 10 Feb 2009, Alexander Back wrote:
> Hi Fritz,
>
> many thanks for your very detailed input. Could you please file a bug
> report for this issue? I think it would be sufficient if you just grab
> the text of your mail and add it to the bug report. With such a d
Hi Fritz,
many thanks for your very detailed input. Could you please file a bug
report for this issue? I think it would be sufficient if you just grab
the text of your mail and add it to the bug report. With such a detailed
report it should be easy to nail down this one.
cheers,
Alex
Fritz
Hi Jenec,
> --snip--
> var sourceWidget =
> qx.core.ObjectRegistration.fromHashCode(e.getData().hashCode);
> --snip--
Sorry for the typo, but it has to be "qx.core.ObjectRegistry" *not*
"qx.core.ObjectRegistration".
cheers,
Alex
--
Hi Jenec,
Jenec wrote:
> Hi, I have a little question for you:
> I need to get an object, which has fired an event.
>
> I place a Listener:
>
> this.addListener("someName", function(e) {
>someObject.someMethod(); //someObject is undefined here
> }, this);
>
> Then I fire a DataEvent us
Hi, I have a little question for you:
I need to get an object, which has fired an event.
I place a Listener:
this.addListener("someName", function(e) {
someObject.someMethod(); //someObject is undefined here
}, this);
Then I fire a DataEvent using:
qx.Class.define("gm.Komponents.String
Matthew Gregory schrieb:
> Hi,
> I can't quite understand something, why does
> qx.ui.core.Widget.__createDecoratorElement call
> "element.useMarkup(decorator.getMarkup())" rather than
> "decorator.init(element)"?
>
> I was looking at overriding the beveled decorator and it is working but
> I n
Hi,
I think there is a bug in ComboBox.js of version 0.7.3 (didn't check with
0.8.x) which is triggered when a ComboBox does not have an item selected -
either after setting it up or after calling resetSelected() - and a
changeLocale event occurs. The following code is enough to reproduce the
erro
Hi,
I can't quite understand something, why does
qx.ui.core.Widget.__createDecoratorElement call
"element.useMarkup(decorator.getMarkup())" rather than
"decorator.init(element)"?
I was looking at overriding the beveled decorator and it is working but
I need to insert another div. Currently I h
Fabian Jakobs schrieb:
> Matthew Gregory schrieb:
>> Thanks,
>> I've attached an image of how it is currently looking compared to the
>> orriginal qx button. I think it looks nicer when the "third color
>> band" is only 1px rather than two. Its working in Fx3 and IE7 (with
>> and without the box
I agree with sebastian. lighter colors look nicer (I know this is a matter
of taste).
btw: thanks Matthew for your work.
On Tue, Feb 10, 2009 at 1:18 PM, Sebastian Werner wrote:
> I prefer the two pixel variant, but I would use softer/lighter colors
> like seen in the original Google buttons. Wh
Matthew Gregory schrieb:
> Thanks,
> I've attached an image of how it is currently looking compared to the
> orriginal qx button. I think it looks nicer when the "third color
> band" is only 1px rather than two. Its working in Fx3 and IE7 (with
> and without the box model).
>
> I will change the
I prefer the two pixel variant, but I would use softer/lighter colors
like seen in the original Google buttons. What do the others say?
Sebastian
Matthew Gregory schrieb:
> Thanks,
> I've attached an image of how it is currently looking compared to the
> orriginal qx button. I think it looks n
Hello,
I believe I have run into a bug on Opera. Logged as
http://bugzilla.qooxdoo.org/show_bug.cgi?id=1922
Are there any workarounds? This is not critical for me at the moment
(Opera is not a required browser for my application), but the problem
seems important as it breaks qooxdoo tables on Ope
Thanks,
I've attached an image of how it is currently looking compared to the
orriginal qx button. I think it looks nicer when the "third color band"
is only 1px rather than two. Its working in Fx3 and IE7 (with and
without the box model).
I will change the implementation I have to use the be
I especially like the effect for being that basic. The thing is that
this kind of markup is quite compact for the little markup needed. You
can still use the Beveled decorator etc. if you need a more
sophisticated effect.
BTW, I think the 3.1 example with the pseudo-gradient is more
interestin
Matthew Gregory schrieb:
> Sounds like a challenge! I don't mind doing this, although I do have
> several other work responsibilities currently so it won't be a quick
> turnaround.
>
> Is there anything anybody else wanted to say about this before I start?
> I will make this fully customizable
18 matches
Mail list logo
