Re: [flexcomponents] Re: Styles :: Revisted once again

Wed, 09 Aug 2006 15:22:35 -0700

Glenn,

VERBATUM

Is it this that is doing what you just said?

    <target name="build-framework" depends="setup" description="use this to build framework.swc">

        <property file="framework-classes.properties"/>
       
        <exec executable="${compc.dir}/${compc.exe}" failonerror="true">
            <arg line="-include-namespaces= http://www.adobe.com/2006/mxml
                       -namespace http://www.adobe.com/2006/mxml core-framework-manifest.xml
                       -external-library-path=libs/playerglobal.swc
                       -source-path=source
                       -accessible=true
                       -include-classes ${flex.classes}
                       -include-file defaults.css defaults.css
                       -include-file Assets.swf Assets.swf
                       -resource-bundle-list=rb.properties
                       -o libs/framework.swc"/>
        </exec>
    </target>

--------------------------------------------------------------------------------

If so where(or how) does this get called(from)? I am a component dev, just starting to getinto all these compiler config xml stuff.

Peace, Mike


On 8/9/06, Glenn Ruehle <[EMAIL PROTECTED]> wrote:

The default Halo theme is always included when building a Flex
application. It is the first theme included, so all contents of it can
be overridden.



Glenn

> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Renaun Erickson
> Sent: Wednesday, August 09, 2006 3:11 PM
> To: [email protected]
> Subject: [flexcomponents] Re: Styles :: Revisted once again
>
> Ok, makes sense.
>
> In the case of the Tree control in the Flex framework, are they
> embedded? Or is there some sneaky way that you always have the
> -theme=Assets.swf always being called when it compiles?
>
> Renaun
>
>
> --- In [email protected], "Glenn Ruehle" <[EMAIL PROTECTED]>
wrote:
> >
> > It depends on the size of the assets and whether or not they will be
> > replaced by the component user.
> >
> > Embedding them all together definitely simplifies the process. The
> > question is whether the component users will be upset if they have
> > additional unused assets in their final output SWF.
> >
> > Glenn
> >
> > > -----Original Message-----
> > > From: [email protected]
> > > [mailto:[email protected]] On Behalf Of Renaun
Erickson
> > > Sent: Wednesday, August 09, 2006 10:00 AM
> > > To: [email protected]
> > > Subject: [flexcomponents] Re: Styles :: Revisted once again
> > >
> > > That last step of including the SWC in the -theme mxmlc argument
> > > requires the user of our components to have knowledge of changing
the
> > > compile arguments. That doesn't help with making components easy
to
> > use.
> > >
> > > If so, would it be better just to embed all the assets into the
> > > component itself?
> > >
> > > Renaun
> > >
> > > --- In [email protected], "Glenn Ruehle" <gruehle@>
> > wrote:
> > > >
> > > > The actionscript approach for initializing defaults has a
drawback -
> > any
> > > > referenced classes or assets will always be linked into the
final
> > output
> > > > SWF, even if they are overridden by CSS. For simple classes and
> > small
> > > > assets, this may not be a problem; but when building up an
entire
> > theme
> > > > (like the default Halo theme), it adds up.
> > > >
> > > >
> > > >
> > > > Here are the basic steps for creating a CSS theme and including
it
> > in
> > > > your component SWC.
> > > >
> > > >
> > > >
> > > > 1. Put all defaults into a CSS file, and give the CSS file
a
> unique
> > > > name (not just 'defaults.css').
> > > > 2. When building the SWC, use -include-file to add the CSS
file
> and
> > > > any other required assets
> > > > 3. When building the SWC, use -include-classes to add any
skin
> > > > classes
> > > > 4. When using the component, make sure the SWC is added to
the
> > > > compiler "theme" setting. This can be done on the command line
or in
> > the
> > > > config file.
> > > >
> > > >
> > > >
> > > > Glenn
> > > >
> > > >
> > > >
> > > > ________________________________
> > > >
> > > > From: Gordon Smith
> > > > Sent: Tuesday, August 08, 2006 6:44 PM
> > > > To: [email protected]
> > > > Cc: Glenn Ruehle
> > > > Subject: RE: [flexcomponents] Styles :: Revisted once again
> > > >
> > > >
> > > >
> > > > I think Glenn knows more about this than I do, so I've cc'd him.
> > > >
> > > >
> > > >
> > > > - Gordon
> > > >
> > > >
> > > >
> > > > ________________________________
> > > >
> > > > From: [email protected]
> > > > [mailto:[email protected]] On Behalf Of Michael
> > Schmalle
> > > > Sent: Tuesday, August 08, 2006 6:37 PM
> > > > To: [email protected]
> > > > Subject: Re: [flexcomponents] Styles :: Revisted once again
> > > >
> > > >
> > > >
> > > > Hi Gordon,
> > > >
> > > > Thanks for the clarification!
> > > >
> > > > Yes, the double hit on file size makes sense, that is why I am
> > trying to
> > > > get the css file approach correct. I am having some issues with
it
> > and
> > > > assets.
> > > >
> > > > One other thing.
> > > >
> > > > You have the defaults, how do I create something similar and
> > 'compile it
> > > > in' when I make the SWC file.
> > > >
> > > > I have had no luck with the library project doing this. Embeded
> > assets
> > > > inside the css file were not getting included. In a linked
directory
> > the
> > > > css file in the library project wasn't even getting recognized
and
> > > > compiled into the SWC.
> > > >
> > > > Any thoughts?
> > > >
> > > > Is there any one that could give a 'quick and dirty' procedural
step
> > > > process for the benefit of this list?
> > > >
> > > > Peace, Mike
> > > >
> > > > On 8/8/06, Gordon Smith <gosmith@ <mailto:gosmith@> >
> > > > wrote:
> > > >
> > > > This approach is fine, and it's what the mx.charts classes do.
> > > >
> > > >
> > > >
> > > > But for the standard Flex components, we decided to use the
> > defaults.css
> > > > approach instead. That makes it possible to restyle them easily
by
> > > > editing a single CSS file. Also, if they get styled in this way
via
> > > > autogenerated code, there is no need to have the superceded
> > > > class-initialization-code-that-sets-up-styles, which adds to SWF
> > size.
> > > >
> > > >
> > > >
> > > > - Gordon
> > > >
> > > >
> > > >
> > > > ________________________________
> > > >
> > > > From: [email protected]
> > > > <mailto:[email protected]>
> > > > [mailto:[email protected]
<mailto:[EMAIL PROTECTED]>
> > ] On
> > > > Behalf Of Michael Schmalle
> > > > Sent: Tuesday, August 08, 2006 1:22 PM
> > > > To: [email protected]
> > > > <mailto:[email protected]>
> > > > Subject: [flexcomponents] Styles :: Revisted once again
> > > >
> > > >
> > > >
> > > > Hi, knock knock, echo, echo
> > > >
> > > > Can any Adobe peoplz tell me why
> > > >
> > > > putting a variation of the following in a component class to
> > initializes
> > > > styles is bad?
> > > >
> > > > // SizerOverlay
> > > > style = StyleManager.getStyleDeclaration
("SizerOverlay");
> > > > if (!style)
> > > > {
> > > > style = new CSSStyleDeclaration();
> > > > StyleManager.setStyleDeclaration("SizerOverlay",
style,
> > > > false);
> > > > }
> > > > if ( style.factory == null)
> > > > {
> > > > style.factory = function():void
> > > > {
> > > > this.cornerRadius = 5;
> > > > this.fillAlpha = 1;
> > > > this.fillColor = 0xffcc00;
> > > > this.horizontalCursorXOffset = -9;
> > > > this.horizontalCursorYOffset = -5;
> > > > this.leftDiagonalCursorXOffset = -9;
> > > > this.leftDiagonalCursorYOffset = -8;
> > > > this.realtimeResize = true;
> > > > this.realtimeResizeAlpha = 0;
> > > > this.rightDiagonalCursorXOffset = -9;
> > > > this.rightDiagonalCursorYOffset = -5;
> > > > this.sizerAlpha = 1;
> > > > this.sizerClientButtonRenderer =
> > > >
com.teotiGraphix.managers.sizerManagerClasses.SizerOverlayButton;
> > > > this.sizerOverlayAlpha = 0;
> > > > this.sizerOverlayOffset = true;
> > > > this.sizerOverlaySkin =
mx.skins.halo.ButtonSkin;
> > > > this.sizerOverlayThickness = 10;
> > > > this.verticalCursorXOffset = -9;
> > > > this.verticalCursorYOffset = -9;
> > > > };
> > > > }
> > > >
> > > > Since this is what the compiler actually does anyway.
> > > >
> > > > Specifically,
> > > >
> > > > // SizerOverlay
> > > > style =
StyleManager.getStyleDeclaration("SizerOverlay");
> > > > if (!style)
> > > > {
> > > > style = new CSSStyleDeclaration();
> > > > StyleManager.setStyleDeclaration("SizerOverlay",
style,
> > > > false);
> > > > }
> > > >
> > > > I am not really agreeing with littering my classes with if()
checks
> > > > everywhere for default styles.
> > > >
> > > > Maybe something is not thought through all the way. If I am
wrong,
> > can
> > > > someone from Adobe please clarify the exact procedure for
> > initializing
> > > > default styles and skins for a commercially distributed
component?
> > > >
> > > > Peace, Mike
> > > >
> > > >
> > > > --
> > > > What goes up, does come down.
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > What goes up, does come down.
> > > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Yahoo! Groups Links
> > >
> > >
> > >
> > >
> > >
> >
>
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>




--
What goes up, does come down. __._,_.___


SPONSORED LINKS
Custom software development Database development software Embedded software development
Offshore software development Software development

YAHOO! GROUPS LINKS



__,_._,___

Reply via email to