Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Received-SPF: pass (nike.apache.org: domain of aharui@adobe.com designates
 64.18.1.238 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "dev@flex.apache.org" <dev@flex.apache.org>
Date: Mon, 25 Mar 2013 12:26:05 -0700
Subject: Re: [FalconJx] progress update
Thread-Topic: [FalconJx] progress update
Thread-Index: Ac4pjTmGTyVoDq7nSO+/dFC2A9aCYAAAV5Rf
Message-ID: <CD75F2DD.5002B%aharui@adobe.com>
In-Reply-To: 
 <CACK5iZeqLcPAnFW-9j9N4Vc5DyYDZBeqh8MrCsmsLWYZbKCbbw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-Entourage/13.16.0.130206
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Om, can you give an example?

IMO, there is a difference between MXML Graphics and FXG.  To me, FXG is
stuff in an FXG file exported from several Adobe design tools.  The interna=
l
pieces are not manipulated at run time.  Today, FXG assets are compiled int=
o
Sprites and other SWF primitives.

MXML Graphics in a skin are generally there for manipulation.  The top-leve=
l
tag is some component class.  I think in FlexJS, I would suggest just
writing components for Rect, Path, etc, so they can also be manipulated at
runtime.


On 3/25/13 12:15 PM, "Om" <bigosmallm@gmail.com> wrote:

> On Mon, Mar 25, 2013 at 11:55 AM, Erik de Bruin <erik@ixsoftware.nl> wrot=
e:
>=20
>> Om,
>>=20
>> 1) the wiki is mostly current, but as a work in progress: if it
>> doesn't work, ask and we will fix ;-)
>>=20
>> 2) CSS resulting from...? I'm not familiar with FXG etc., so my
>> questions are bound to be naive as well, as you'll notice. Basically
>> we have access to whatever the compiler (Falcon-main, if you will) has
>> access to, but some thing might be easier than others. Mike S. is our
>> wizard, he'll know what to do if we can't figure it out.
>>=20
>=20
> Just to be clear, for all practical purposes, when I say FXG, I really me=
an
> MXML.  This is because, the Flex implementation of FXG ensures that FXG
> elements can be pluggable inline into any MXML component.  So, if we are =
to
> support MXML, then we must support FXG.
>=20
> In what I am doing currently, I am actually processing an MXML file, igno=
re
> things that I dont care about (like fx:Script, fx:Metadata, and any
> non-visual component)
>=20
> It just happens that for Spark components, the FXG elements appear only i=
n
> their Spark skins.  This makes my job easier because if I target only the
> spark skins, I wont have to deal with a lot of other MXML functional (i.e=
.
> non view) elements.
>=20
>=20
>>=20
>> 3) Ah, there is the CSS, I guess (fxg -> svg + css). The AS code will
>> be cross-compiled to AS (weird, I know) or any form of JS we chose,
>> most likely 'goog' JS, as it will have to be compatible with FlexJS
>> and the VanillaSDK. Due to the way FalconJx is set up, it will be easy
>> to add FXG specific JS parsing, if needed.
>>=20
>=20
> What if I want to handcode some javascript?  For example, if I want to
> support the current 'states' paradigm used in spark skins, I need to writ=
e
> some javascript to make it a reusable component.  I am not sure if this i=
s
> the right approach, though.  What do you guys think?
>=20
>=20
>>=20
>> 4) Sounds like and excellent starting point... however, you'll
>> probably have to tweak your local SDK 'a bit' to get both the Flex and
>> JS side working.  Or should be start one of those much rumored
>> 'shared' feature branches of the SDK?
>>=20
>=20
> What kind of tweaking do you mean?  Actually, I dont understand anything
> you just said.  Please explain like I am 5 years old :-)
>=20
>=20
>>=20
>> I love how everything seems to be converging and it really feels like
>> Flex -> HTML5/JS is doable!
>>=20
>=20
> Cautious optimism abounds!
>=20
>=20
>>=20
>> EdB
>>=20
>>=20
>>=20
>> On Mon, Mar 25, 2013 at 7:21 PM, Om <bigosmallm@gmail.com> wrote:
>>> Erik,
>>>=20
>>> I am planning to get FalconJX working on my machine soon.  Before I sta=
rt
>>> digging into it,
>>>=20
>>> 1. Are these wiki pages current?
>>>=20
>>>=20
>>=20
https://cwiki.apache.org/confluence/display/FLEX/AS+to+JS+-+the+%27goog%27+=
Wa>>
y
>>>=20
>>> https://cwiki.apache.org/confluence/display/FLEX/FalconJx+Prototype
>>>=20
>>> 2.  Do you have any thoughts on how we want to handle the resulting CSS=
?
>>>  Inlining everything or have it as separate files?
>>>=20
>>> 3.  My approach would take in a spark skin file and convert the fxg
>>> elements into svg+css.  There is going to some AS code that needs to be
>>> converted JS.  I believe your approach already handles this right?
>>>=20
>>> 4.  I see that the VanillaSDK supports the Button component in HTML5.
>>>  Maybe that is where I should start and get my code working there?
>>>=20
>>> Sorry if I am asking naive questions, but I am looking for some guidanc=
e
>> on
>>> how to get my work integrated into FalconJx (or FalconJS)
>>>=20
>>> Thanks,
>>> Om
>>>=20
>>> On Mon, Mar 25, 2013 at 8:45 AM, Erik de Bruin <erik@ixsoftware.nl>
>> wrote:
>>>=20
>>>> Hi,
>>>>=20
>>>> Just 'checking in': FalconJx can now compile the FlexJSTest_again
>>>> example from the command line, using these arguments:
>>>>=20
>>>>=20
>>>>=20
>> +env.PLAYERGLOBAL_HOME=3D/Users/erik/Documents/ApacheFlex/dependencies/P=
layerGl
>> obal/player
>>>> +playerglobal.version=3D11.1
>>>> -load-config=3D"/Applications/Adobe Flash Builder
>>>> 4.7/sdks/4.9.1/frameworks/flex-config.xml"
>>>>=20
>>>>=20
>> -library-path+=3D/Users/erik/Documents/ApacheFlex/git/flex-asjs/framewor=
ks/as/l
>> ibs/FlexJSUI.swc
>>>> -js-output-type=3DFLEXJS
>>>> -output=3D/Users/erik/Desktop/FlexJS/fromEclipse/FlexJSTest.js
>>>>=20
>>>>=20
>> /Users/erik/Documents/ApacheFlex/git/flex-asjs/examples/FlexJSTest_again=
/src/
>> FlexJSTest.mxml
>>>>=20
>>>> Well, not exactly those, please change the paths to fit your local
>>>> environment ;-)
>>>>=20
>>>> Next up:
>>>> - support for publishing with the GCC and associated tricks (SourceMap
>>>> etc.)
>>>> - full FlexJS type AS -> JS support (the current implementation is
>>>> custom tailored to the FlexJSTest_Again example code)
>>>>=20
>>>> Have fun!
>>>>=20
>>>> EdB
>>>>=20
>>>>=20
>>>>=20
>>>> --
>>>> Ix Multimedia Software
>>>>=20
>>>> Jan Luykenstraat 27
>>>> 3521 VB Utrecht
>>>>=20
>>>> T. 06-51952295
>>>> I. www.ixsoftware.nl
>>>>=20
>>=20
>>=20
>>=20
>> --
>> Ix Multimedia Software
>>=20
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>=20
>> T. 06-51952295
>> I. www.ixsoftware.nl
>>=20

--=20
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui