Hi Derrell,
You can include it manually with qx.Theme.include [1]. I don't think I've
used that method though - personally I prefer to write appearances etc as
mixins for each custom widget and then include the mixin in the
application's theme, although neither method is the automatic solution
you're looking for.
[1]
http://qooxdoo.org/contrib/usage/contrib_application_integration_guide#integ
rate_contributions_which_provide_own_themes
John
From: Derrell Lipman <[email protected]>
Reply-To: qooxdoo Development <[email protected]>
Date: Tuesday, 15 May 2012 15:13
To: qooxdoo Development <[email protected]>
Subject: Re: [qooxdoo-devel] Incorporating many external JavaScript files
On Tue, May 15, 2012 at 6:24 AM, thron7 <[email protected]>
wrote:
>
> On 05/15/2012 03:29 AM, Derrell Lipman wrote:
>> > On a related note... I've run into this problem before, and never
>> > figured out how to solve it. I can't figure out why an application
>> > that uses a library, by referencing its manifest in its config.json
>> > file, doesn't see and use that library's appearances. I've solved the
>> > problem in the past by by manually copying all of the appearances from
>> > from libraries I've used, but that's certainly not the way it should
>> > work. What is the incantation to get libraries' appearances to be used
>> > by apps using those libraries?
>
> By specifying the library's theme as QXTHEME in your config.json, e.g.
>
> ...
> "let" : {
> "QXTHEME" : "somelib.theme.Theme",
> ....
> }
>
>
> (What that does behind the scene is just adding somelib.theme.Theme to
> the "include" key when generating the app, i.e.
>
> "include" : ["myapp.Application", "somelib.theme.Theme"]
>
> and setting the environment key "qx.theme" to the same class name:
>
> "environment" : { "qx.theme" : "somelib.theme.Theme", ... }
> ).
Thomas, I don't think this does what I asked about. I believe what you're
describing is replacing the theme. The library (typically) does not provide
a replacement theme for the application; it only provides its little portion
of an existing theme, e.g. modern. Example: The collapsablepanel contrib
provides a "collapsable-panel" map in its Appearance.js file as part of the
modern theme. My question is about merging the "collapsable-panel"
appearance into the default modern theme. I would think this should happen
automatically, just by including the library's manifest in my app. Even if
not added by default, will putting it in the "include" array include it in
the selected appearance theme? I'll give it a try.
Thanks,
Derrell
----------------------------------------------------------------------------
-- Live Security Virtual Conference Exclusive live event will cover all the
ways today's security and threat landscape has changed and how IT managers
can respond. Discussions will include endpoint security, mobile security and
the latest in malware threats.
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___________________
____________________________ qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
