Hi Jim,

so far as I know is this in the manual not explicit documented. I have searched in the API doc for a include method, so I have found it.

Cheers,
Chris


Am 06.08.2010 00:03, schrieb Jim Hunter:
Yes! You were right. I was missing the include statement. I added that one line to my code and it's working perfect. Did you find this in the docs somewhere? If so, I must have missed it.

Thanks,

Jim


On Thu, Aug 5, 2010 at 1:08 AM, Christian Hagendorn <[email protected] <mailto:[email protected]>> wrote:

     Hi Jim,

    it seems to me that your "runtime" generated is not included to the
    current appearance. Just try to include the "runtime" generated
    with the
    application appearance:
    http://tinyurl.com/399e43x

    This should also works with qx 0.8.3.

    Cheers,
    Chris

    Am 05.08.2010 04:32, schrieb Jim Hunter:
    > I am finally getting around to fixing this code that broke when
    I went
    > from .7 to .8 (I think I am at .8.3 right now). My application is
    > slightly different then most in that I don't know at design time
    what
    > anything is going to look like at run time. This includes the
    > appearance of fonts. The users are able to design their own look and
    > feel and that information is stored in a database. Our server loads
    > the information from the db and then the browser renders it. So, in
    > .7, I was able to create, on the startup of the application, a
    custom
    > appearance for the fonts used by this user. Here is what that file
    > looks like, it gets loaded at the start of the application:
    >
    > qx.Theme.define("swep.Appearance", {title: "swepAppear",
    appearances: {
    > "SFREGULARTEXT" : { style : function(states){ var myfont = new
    > qx.bom.Font(12, ["Arial"]);   return  { font: myfont, textColor:
    > "black"}  }},
    > "SFHIGHLIGHTEDTEXT" : { style : function(states){ var myfont = new
    > qx.bom.Font(12, ["Arial"]);   return  { font: myfont, textColor:
    > "black"}  }},
    > "SFHOTTEXT" : { style : function(states){ var myfont = new
    > qx.bom.Font(12, ["Arial"]);   return  { font: myfont, textColor:
    > "red"}  }},
    > "SFSFOR_CHANGELEVELTEXT" : { style : function(states){ var myfont =
    > new qx.bom.Font(13, ["Arial"]);  myfont.setBold(true);   return  {
    > font: myfont, textColor: "red"}  }}
    > }});
    >
    > (this is an abbreviated version, there is actually about 50
    variations
    > all created by the user)
    >
    > And when I displayed a label I knew the 'style' that I needed to use
    > and I would simply do a myLabel.setAppearance("SFHOTTEXT") and I
    would
    > get my font styled in 12pt Arial red. Now in .8, instead of it
    working
    > I get a warning stating:
    >
    > qx.theme.manager.Appearance[z]: Missing appearance: SFHOTTEXT
    >
    > I am betting that I am missing something simple, but I can't seem to
    > find it. Any suggestions?
    >
    > Thanks,
    > Jim


    
------------------------------------------------------------------------------
    The Palm PDK Hot Apps Program offers developers who use the
    Plug-In Development Kit to bring their C/C++ apps to Palm for a share
    of $1 Million in cash or HP Products. Visit us here for more details:
    http://p.sf.net/sfu/dev2dev-palm
    _______________________________________________
    qooxdoo-devel mailing list
    [email protected]
    <mailto:[email protected]>
    https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel



------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to