How about creating your application without skins and then to load branded
skin-packs at runtime?
I think this way you should be able to build one application swf and a bunch
full of skin swfs. You could now either pass the skin swf name as a
parameter to the main application or you set this to a fixed name and place
the appropriate skin swf with that name on your server:
Here's how I load an external Skin module:
protected function initSkin(skinName:String):void {
styleManager.loadStyleDeclarations(skinName, true, false,
ApplicationDomain.currentDomain);
}
It's just an Idea ... mabe it helps.
Chris
2011/2/3 yar <[email protected]>
> Thank you!
>
> I'm afraid in that case I will end up with 15 or so maven projects to
> build my app for 15 different graphic sets were the only difference
> would be in which branding dependency (swc file with graphics only) to
> add. Do you think maven build process is a bad choice for my case?
>
> On Jan 15, 6:09 pm, Marvin Froeder <[email protected]> wrote:
> > If you wanna produce 2 artifacts is really advised to have 2 projects.
> Now,
> > if you wanna 2 artifacts with two different dependencies set, then it is
> a
> > must. Maven doesn't allow to build same stuff twice, using different
> > dependencies on the same reactor.
> >
> > VELO
>
> --
> You received this message because you are subscribed to the Google
> Groups "Flex Mojos" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]<flex-mojos%[email protected]>
> For more options, visit this group at
> http://groups.google.com/group/flex-mojos
>
> http://flexmojos.sonatype.org/
>
--
You received this message because you are subscribed to the Google
Groups "Flex Mojos" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/flex-mojos
http://flexmojos.sonatype.org/
