Re: [flexcoders] Re: Declaring protected fields in MXML?
Yeah I get what you mean, I was thinking about doing something similar, just wrapping them in an or something. Cheers! -J On Thu, May 8, 2008 at 12:39 PM, Bjorn Schultheiss < [EMAIL PROTECTED]> wrote: > sorry, at the end i meant to say > > So you can*t* access the button ID's via the panel. > Only the canvas. > > --- In flexcoders@yahoogroups.com , "Bjorn > Schultheiss" > > <[EMAIL PROTECTED]> wrote: > > > > well i'm not sure what you're actually trying to do but you can hide > > the id within a certain scope. > > > > > > look at code: > > MyApp.mxml > > http://www.adobe.com/2006/mxml"; xmlns="*" > > layout="absolute"> > > > > > > > > > > myCanvas.mxml > > http://www.adobe.com/2006/mxml"; xmlns="*" > > width="400" height="300"> > > > > > > > > > > > > > > > > > > testcmp.mxml > > http://www.adobe.com/2006/mxml"; width="400" > > height="300"> > > > > > > > > > > > > > > > > > > So you can access the button ID's via the panel. > > Only the canvas. > > > > > > --- In flexcoders@yahoogroups.com , "Josh > McDonald" wrote: > > > > > > Bummer... I've got some classes in which I'm doing a lot of the stuff > > > declaritvely in MXML, and I just didn't want the ids leaking into > > the public > > > API. > > > > > > I guess I'll just have to rethink things a little bit, make the > > declarative > > > stuff the public API, and have it reference the functions that are > > declared > > > in that used to be ;-) > > > > > > -J > > > > > > On Thu, May 8, 2008 at 11:30 AM, Bjorn Schultheiss < > > > bjorn.mailinglists@> wrote: > > > > > > > Everything you described is possible except the protected > instead of > > > > public part. > > > > At some point one of the accessor must be public. > > > > > > > > > > > > --- In flexcoders@yahoogroups.com > > > > 40yahoogroups.com>, > > "Josh > > > > McDonald" wrote: > > > > > > > > > > Hey guys, > > > > > > > > > > Is it possible to define (non visual) components in MXML that are > > > > protected > > > > > instead of public, but can still be referenced by the ID (or a > > name, or > > > > > something)? > > > > > > > > > > Cheers, > > > > > > > > > > -J > > > > > > > > > > -- > > > > > "Therefore, send not to know For whom the bell tolls. It tolls for > > > > thee." > > > > > > > > > > :: Josh 'G-Funk' McDonald > > > > > :: 0437 221 380 :: josh@ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > "Therefore, send not to know For whom the bell tolls. It tolls for > > thee." > > > > > > :: Josh 'G-Funk' McDonald > > > :: 0437 221 380 :: josh@ > > > > > > > > -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED]
[flexcoders] Re: Declaring protected fields in MXML?
sorry, at the end i meant to say So you can*t* access the button ID's via the panel. Only the canvas. --- In flexcoders@yahoogroups.com, "Bjorn Schultheiss" <[EMAIL PROTECTED]> wrote: > > well i'm not sure what you're actually trying to do but you can hide > the id within a certain scope. > > > look at code: > MyApp.mxml > http://www.adobe.com/2006/mxml"; xmlns="*" > layout="absolute"> > > > > > myCanvas.mxml > http://www.adobe.com/2006/mxml"; xmlns="*" > width="400" height="300"> > > > > > > > > > testcmp.mxml > http://www.adobe.com/2006/mxml"; width="400" > height="300"> > > > > > > > > > So you can access the button ID's via the panel. > Only the canvas. > > > --- In flexcoders@yahoogroups.com, "Josh McDonald" wrote: > > > > Bummer... I've got some classes in which I'm doing a lot of the stuff > > declaritvely in MXML, and I just didn't want the ids leaking into > the public > > API. > > > > I guess I'll just have to rethink things a little bit, make the > declarative > > stuff the public API, and have it reference the functions that are > declared > > in that used to be ;-) > > > > -J > > > > On Thu, May 8, 2008 at 11:30 AM, Bjorn Schultheiss < > > bjorn.mailinglists@> wrote: > > > > > Everything you described is possible except the protected instead of > > > public part. > > > At some point one of the accessor must be public. > > > > > > > > > --- In flexcoders@yahoogroups.com , > "Josh > > > McDonald" wrote: > > > > > > > > Hey guys, > > > > > > > > Is it possible to define (non visual) components in MXML that are > > > protected > > > > instead of public, but can still be referenced by the ID (or a > name, or > > > > something)? > > > > > > > > Cheers, > > > > > > > > -J > > > > > > > > -- > > > > "Therefore, send not to know For whom the bell tolls. It tolls for > > > thee." > > > > > > > > :: Josh 'G-Funk' McDonald > > > > :: 0437 221 380 :: josh@ > > > > > > > > > > > > > > > > > > > > > -- > > "Therefore, send not to know For whom the bell tolls. It tolls for > thee." > > > > :: Josh 'G-Funk' McDonald > > :: 0437 221 380 :: josh@ > > >
[flexcoders] Re: Declaring protected fields in MXML?
well i'm not sure what you're actually trying to do but you can hide the id within a certain scope. look at code: MyApp.mxml http://www.adobe.com/2006/mxml"; xmlns="*" layout="absolute"> myCanvas.mxml http://www.adobe.com/2006/mxml"; xmlns="*" width="400" height="300"> testcmp.mxml http://www.adobe.com/2006/mxml"; width="400" height="300"> So you can access the button ID's via the panel. Only the canvas. --- In flexcoders@yahoogroups.com, "Josh McDonald" <[EMAIL PROTECTED]> wrote: > > Bummer... I've got some classes in which I'm doing a lot of the stuff > declaritvely in MXML, and I just didn't want the ids leaking into the public > API. > > I guess I'll just have to rethink things a little bit, make the declarative > stuff the public API, and have it reference the functions that are declared > in that used to be ;-) > > -J > > On Thu, May 8, 2008 at 11:30 AM, Bjorn Schultheiss < > [EMAIL PROTECTED]> wrote: > > > Everything you described is possible except the protected instead of > > public part. > > At some point one of the accessor must be public. > > > > > > --- In flexcoders@yahoogroups.com , "Josh > > McDonald" wrote: > > > > > > Hey guys, > > > > > > Is it possible to define (non visual) components in MXML that are > > protected > > > instead of public, but can still be referenced by the ID (or a name, or > > > something)? > > > > > > Cheers, > > > > > > -J > > > > > > -- > > > "Therefore, send not to know For whom the bell tolls. It tolls for > > thee." > > > > > > :: Josh 'G-Funk' McDonald > > > :: 0437 221 380 :: josh@ > > > > > > > > > > > > > -- > "Therefore, send not to know For whom the bell tolls. It tolls for thee." > > :: Josh 'G-Funk' McDonald > :: 0437 221 380 :: [EMAIL PROTECTED] >
Re: [flexcoders] Re: Declaring protected fields in MXML?
Bummer... I've got some classes in which I'm doing a lot of the stuff declaritvely in MXML, and I just didn't want the ids leaking into the public API. I guess I'll just have to rethink things a little bit, make the declarative stuff the public API, and have it reference the functions that are declared in that used to be ;-) -J On Thu, May 8, 2008 at 11:30 AM, Bjorn Schultheiss < [EMAIL PROTECTED]> wrote: > Everything you described is possible except the protected instead of > public part. > At some point one of the accessor must be public. > > > --- In flexcoders@yahoogroups.com , "Josh > McDonald" <[EMAIL PROTECTED]> wrote: > > > > Hey guys, > > > > Is it possible to define (non visual) components in MXML that are > protected > > instead of public, but can still be referenced by the ID (or a name, or > > something)? > > > > Cheers, > > > > -J > > > > -- > > "Therefore, send not to know For whom the bell tolls. It tolls for > thee." > > > > :: Josh 'G-Funk' McDonald > > :: 0437 221 380 :: [EMAIL PROTECTED] > > > > > -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED]
[flexcoders] Re: Declaring protected fields in MXML?
Everything you described is possible except the protected instead of public part. At some point one of the accessor must be public. --- In flexcoders@yahoogroups.com, "Josh McDonald" <[EMAIL PROTECTED]> wrote: > > Hey guys, > > Is it possible to define (non visual) components in MXML that are protected > instead of public, but can still be referenced by the ID (or a name, or > something)? > > Cheers, > > -J > > -- > "Therefore, send not to know For whom the bell tolls. It tolls for thee." > > :: Josh 'G-Funk' McDonald > :: 0437 221 380 :: [EMAIL PROTECTED] >
