Re: [qooxdoo-devel] Appearance question

> So I make all my incremental changes in the main compiled file until I > have the class like I want it, I presume with all optimizations turned off?! Still, no comments, no indentation ... tough, I thought you were the guy that likes formatting?! > then I copy my changes back into the sourc

Re: [qooxdoo-devel] Appearance question

Yes, I mean everything I said. I change code and re-test in the browser a few hundred times a day (FireBug has allowed me to reduce the number of changes in code I make so that has helped reduce the number of browser reloads). Doing a full build every time I make a change that I need to test would

Re: [qooxdoo-devel] Appearance question

Jim, > No, I do all my development directly into the compiled file, unless I > am in need of a core class that isn't loaded and even then I am apt to > copy that class file in manually). I included the class file you see > in my main file right above where it was first used. If that was not >

Re: [qooxdoo-devel] Appearance question

No, I do all my development directly into the compiled file, unless I am in need of a core class that isn't loaded and even then I am apt to copy that class file in manually). I included the class file you see in my main file right above where it was first used. If that was not enough to get it inc

Re: [qooxdoo-devel] Appearance question

Jim, I guess you found the theme files in the standard skeleton applications (the ones you create with create-application.py), and took your theme inspiration from there. Did you also add the theme class to the "include" key of your config.json?, and re-ran 'generate.py source'?! T. Jim Hunte

Re: [qooxdoo-devel] Appearance question

I guess I am not 'getting' the appearance class. Here is the class I added for my custom appearances, let me know what I am doing wrong: qx.Theme.define("swep.Appearance", { extend : qx.theme.modern.Appearance, title : "swep", appearances : { "sfNavDocArrowBar" : {}, "sfNavDocAr

Re: [qooxdoo-devel] Appearance question

I found an example of what I need to do in the demo apps that come with qooxdoo. I will try and do it that way to see if I get better results. Jim On Thu, Aug 6, 2009 at 4:15 PM, Jim Hunter wrote: > It turns out that things don't work 'normally' if the appearance key is > missing. I am trying to

Re: [qooxdoo-devel] Appearance question

It turns out that things don't work 'normally' if the appearance key is missing. I am trying to create controls that utilize buttons and without the appearance key, you don't get any of the cool rollover animation etc for the button. So it looks like I need to either do things the ugly way and have

Re: [qooxdoo-devel] Appearance question

Hi Jim, I've opened a bug today to address exactly this issue . If a child control is not configured by the appearance theme it should fallback to its default appearance. We are working on this issue. Best Fabian > I don't see a need for this?

Re: [qooxdoo-devel] Appearance question

I don't see a need for this? The controls all render and display fine without creating the appearance keys, so why is there a warning generated? If it renders fine then why is the key 'required'? Thanks, Jim On Tue, Aug 4, 2009 at 12:42 AM, Daniel Wagner wrote: > Hi Jim, > > you need to create a

Re: [qooxdoo-devel] Appearance question

Hi Jim, you need to create appearance keys for all your child controls. For example, if your custom widget with the appearance id "customwidget" has a qx.ui.form.TextField child control, you need an entry for "customwidget/textfield" in your Appearance.js. Since TextField is a standard widget,

[qooxdoo-devel] Appearance question

Why is it that when I am creating my own custom control using the this._createChildControl method, I get warnings about missing appearance, but when I create the same control in the constructor directly, it works fine? How can I easily create my controls using this._createChildControl and not get t

Re: [qooxdoo-devel] Appearance question: how to get the states of the parent widget inside the sub widget appearance definition?

Hi Erich, Erich Konicek wrote: > Hi Alex, > > thank you for the detailed answer. > > Since the my own states are not forwarded to the sub-widgets, > I will try a solution to set the states depending on the class of the > widget > to sub-widget I need. > > Is "widget._getChildControl('xxx')" th

Re: [qooxdoo-devel] Appearance question: how to get the states of the parent widget inside the sub widget appearance definition?

Hi Alex, thank you for the detailed answer. Since the my own states are not forwarded to the sub-widgets, I will try a solution to set the states depending on the class of the widget to sub-widget I need. Is "widget._getChildControl('xxx')" the proper way to get the sub-widget? Erich p.s. My

Re: [qooxdoo-devel] Appearance question: how to get the states of the parent widget inside the sub widget appearance definition?

Hi Erich, Erich Konicek wrote: > Hi Alex! > > I think, that is not correct. > The states-object in the style function of a sub-widgets holds only the > states set in the sub-widget, not in the parent widget. Yes you're right, I should have checked that before wrote the mail :) In fact, there is

Re: [qooxdoo-devel] Appearance question: how to get the states of the parent widget inside the sub widget appearance definition?

Hi Alex! I think, that is not correct. The states-object in the style function of a sub-widgets holds only the states set in the sub-widget, not in the parent widget. I wrote a little test: If a Atom has the state "test", the backgroundColor of the label-object shoud be "red". Here he code of

Re: [qooxdoo-devel] Appearance question: how to get the states of the parent widget inside the sub widget appearance definition?

Hi Erich, Erich Konicek wrote: > Hi! > > Is it possible in qx 0.8 Appearance definition to get the states of the > partent widget > inside the appearance definition of a sub widget? Yes, every sub-widget has access to all states set by the parent widget. > E.g. > I want to change the background

[qooxdoo-devel] Appearance question: how to get the states of the parent widget inside the sub widget appearance definition?

Hi! Is it possible in qx 0.8 Appearance definition to get the states of the partent widget inside the appearance definition of a sub widget? E.g. I want to change the background color or the icon in a checkbox widget depending on the states of the checkbox. Something like this: appearances : .

Re: [qooxdoo-devel] Appearance question:

Hi, I have updated the wiki solving this problem. alex.d wrote: > > Hey! > It works! I deleted the setup routine and just used ColorObject instead > and it works: > > *Instead of:* > /*var oldSetup = apar.setup; > apar.setup = function() { > this.backColorFocused

Re: [qooxdoo-devel] Appearance question:

Hey! It works! I deleted the setup routine and just used ColorObject instead and it works: Instead of: /*        var oldSetup = apar.setup;         apar.setup = function() {             this.backColorFocused = new qx.renderer.color.ColorObject("red");             this.backColor = new qx.render

Re: [qooxdoo-devel] Appearance question:

Here is my exact code to change the appearance of all common controls (sorry, some names are in Spanish): function iniTema() { function actualiza(apar) { if (apar) { var vieState = apar.state; apar.state = function(vWidget, vThem

Re: [qooxdoo-devel] Appearance question:

Normally it's better to extend the existing appearance (create a subclass) and then overwrite (define) the new or to be modified styles. Cheers, Sebastian Alex D. schrieb: > Hi, > > I tried the appearance example from > wiki(http://qooxdoo.org/documentation/developer_manual/appearances) and

Re: [qooxdoo-devel] Appearance question:

How "slight" is your variation? Can send me a working example please? Best Regards, alex.d Strange, I slight variation of this code works ok for me. alex.d wrote: Hi dperez, It enters the function tow times every time i focus one of the textfields(one time for the "unfocused"

Re: [qooxdoo-devel] Appearance question:

Strange, I slight variation of this code works ok for me. alex.d wrote: > > Hi dperez, > > It enters the function tow times every time i focus one of the > textfields(one time for the "unfocused" textfield, and another one for > the "focused" - i have already debugged this - it's working per

Re: [qooxdoo-devel] Appearance question:

Hi dperez, It enters the function tow times every time i focus one of the textfields(one time for the "unfocused" textfield, and another one for the "focused" - i have already debugged this - it's working perfectly). But it seems like qooxdoo just doesn't refresh the appearance of the widget(i

Re: [qooxdoo-devel] Appearance question:

Hi Alex, Place a breakpoint in apar.state or log a message, to see if it enters there. alex.d wrote: > > Hi dperez, > > I added one more textfield but, sorry - no changes at all. It seems to > me that qooxdoo changes the appearance correctly, but anyway uses the > old one. > > Best Regards

Re: [qooxdoo-devel] Appearance question:

Hi dperez, I added one more textfield but, sorry - no changes at all. It seems to me that qooxdoo changes the appearance correctly, but anyway uses the old one. Best Regards, alex.d Hi Alex, This example is from mine. Maybe as you only have one textfield in your form, you can't observe

Re: [qooxdoo-devel] Appearance question:

Hi Alex, This example is from mine. Maybe as you only have one textfield in your form, you can't observe the color change, as it can't lose the focus. alex.d wrote: > > Hi, > > I tried the appearance example from > wiki(http://qooxdoo.org/documentation/developer_manual/appearances) and > i

[qooxdoo-devel] Appearance question:

Hi, I tried the appearance example from wiki(http://qooxdoo.org/documentation/developer_manual/appearances) and it doesn't work. I made following: //---Copy-Paste from Wiki--- var theme = qx.manager.object.Appear