On Thu, Oct 2, 2008 at 9:20 PM, Jim Hunter <[EMAIL PROTECTED]> wrote:
> I am having a dickens of a time getting my mixin classes to be included in
> both script builds and actual builds
>
Jim, I know there's a way to do that using the config file. Another option
is to use #require entries in one of your class files. In any of your class
files that are getting properly included (and preferably in one to which the
mixin is relevant), you can do something like this:
/*
#require(swep.mixinsWidget)
*/
Note that this must be in a commented section.
Also note that by convention, mixins are named with a capital 'M' followed
by a camel-case brief (1-3 words) description of the purpose of the mixin.
Yours contains three completely unrelated changes so you could consider
making them into three separate mixins. If you keep it like it is, you
might consider renaming it to swep.MWidget. Otherwise, you could have
swep.MToolId, swep.MHtmlProperty, and swep.MChildren or something like that.
Derrell
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
