Doh, just realised... .

if i have
com["SynergyFLEX"]["templates"]["mail"]["defaultLayout"]
at the end of the day the compiler evaluates that accordingly and that
becomes my reference point..

as i had something like this

                var pathToTemplate = oTemplate.path.split(".");
                var prfx = com;
                var path = "";
                for(var i=1; i < pathToTemplate.length; i++) {
                        
Dumper.info(com["SynergyFLEX"]["templates"]["mail"]["defaultLayout"]);
// Test... heh.
                        var obj = prfx;
                        var itm = pathToTemplate[i];
                        var prfx = obj[itm];
                        
                }
                oScreenContainer.createChild(prfx);

Now at first glance i was thinking "but i'm doing it a dynamic
iteration wtf!" - then i realised oooooh....the Dumper.info is infact
creating a reference.

I iz dumb ;) thanks for yall patience in this little learning curve.
;) - it did have me thinking that MM did something really cool with
FLASH + Server-side compiler..oh well ;)

my bad 
*embrassed look* :)


On Apr 6, 2005 10:22 PM, Abdul Qabiz <[EMAIL PROTECTED]> wrote:
> 
> Hi Scott,
> 
> As I(and someone else) mentioned earlier, if you refer a class in your
> app.mxml, it would be compiled with rest of code in your app.mxml and
> embedded in your app.swf.
> 
> I think, all the code and assets are embedded in your swf, unless you choose
> to use RSL(for assets) in your application....
> 
> -abdul
> 
> 
> -----Original Message-----
> From: Scott Barnes [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 06, 2005 5:25 PM
> To: [email protected]
> Subject: Re: [flexcoders] Re: createChild dynamically via DB arguments..
> 
> Heres a test for yas:
> 
> Inside a new FLEX app directory (ie start fresh), create a dir, then
> inside that dir, create another and another (go as deep as ya want),
> then finally create a mxml file.
> 
> Then create an simple class file, and instantiate it via initialize()
> on mx.Application, then inside this class, do the same as you did
> (make as many nested ones as you want if need be) then at some point,
> simply do this
> 
> mx.core.Application.application.baseContainer.createChild(blah[arg1][arg2]
> etc..)
> 
> Then explain if you can / want to, how the hell that works. As I must
> be dumber then originally thought as i can't seem to connect the dots
> on how the hell that works? hell i'm struggling to even explain it....
> (also i put another sequence of the above inside the
> unknown-loaded-at-runtime-class and they came up aswell heh).
> 
> imho its as if at compile time, the entire app is packaged together,
> and seperated into whats FLASH code and whats other, if other do i
> embed it inside the swf and all that... i''ll pop the hood a later day
> (if i can figure it out) but *shrug* my level of FLEX expertises ends
> here hehehe.
> 
> _level0["com"] or _global["com"] etc  won't work. As well as findClass();
> 
> On a side note/question. I am also unsure if (hell i have no idea to
> test) whether or not if you have assets embedded inside the mxml files
> in question (even declared as RSL) will they request a new asset per
> instantiation...
> 
> Any input / help is most welcomed heh.
> 
> --
> Regards,
> Scott Barnes
> http://www.mossyblog.com
> http://www.flexcoder.com (Coming Soon)
> 
> Yahoo! Groups Links
> 
> 
> Yahoo! Groups Links
> 
> 
> 
> 
> 


-- 
Regards,
Scott Barnes
http://www.mossyblog.com
http://www.flexcoder.com (Coming Soon)


 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/flexcoders/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 



Reply via email to