Henry, reading this, should you add a compile time constant for the AIR runtime? Since there are AIR specific APIs/settings, and the Flex compiler needs a different configuration to deploy AIR apps?
Just a thought. On Sun, Sep 12, 2010 at 4:11 AM, Henry Minsky <[email protected]> wrote: > The list of possible compile time constants are these, I believe > > $runtime : string > $swf7 : boolean > $swf8 : boolean > $as2 : boolean > $swf9 : boolean > $swf10 : boolean > $as3 : boolean > $dhtml : boolean > $j2me : boolean > $svg : boolean > $js1 : boolean > $debug : boolean > $profile : boolean > $backtrace : boolean > > > > On Sat, Sep 11, 2010 at 10:08 PM, Henry Minsky <[email protected]> > wrote: >> >> The supported attributes for <when> are >> >> 'property', which looks at a boolean compile time property >> <when property="$as3"> // checks for Boolean true >> >> 'property' with 'value', checks that the given compile time property >> equals the given literal value >> <when property="$runtime" value="swf9"> // checks for string >> equality >> >> and for back compatibility, the 'runtime' attribute, equivalent to the >> above: >> <when runtime="swf9"> >> >> <unless> takes the same arguments as <when>, it just has the sense >> inverted, so it includes it's body if >> the condition is false. >> >> >> >> >> On Sat, Sep 11, 2010 at 6:06 PM, Lou Iorio <[email protected]> wrote: >>> >>> Are <property> and <value> the only two attributes for <when>? >>> What are the possible values? >>> Are the attributes for <unless> the same as those for <when>? >>> My plan is to do simple reference pages for <when>, <unless>, >>> and <otherwise>, and link from those pages to the <switch> page. >> >> >> -- >> Henry Minsky >> Software Architect >> [email protected] >> >> > > > > -- > Henry Minsky > Software Architect > [email protected] > > >
