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.21 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "dev@flex.apache.org" <dev@flex.apache.org>
Date: Wed, 27 Mar 2013 10:50:33 -0700
Subject: Re: [FalconJx] progress update
Thread-Topic: [FalconJx] progress update
Thread-Index: Ac4rEVkM+4ghK9LuTYqhpWKUPryzRgAAjsWc
Message-ID: <CD787F79.50270%aharui@adobe.com>
In-Reply-To: 
 <CAJs+wW0ojWU79wBECDp2ew=R42FLPCCg--fxiT1eP1g+dqQbCA@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

Excellent.  I will try it out later today.  I have to quickly fix some
FalconJS stuff for my potential "customer", but once I get past that I will
see if FalconJX can generate the same code.

I am hopeful that if I run into more of the kinds of errors I am fixing in
FalconJS, that they will be easier to find and fix in FalconJX.


On 3/27/13 10:34 AM, "Erik de Bruin" <erik@ixsoftware.nl> wrote:

> Another update (have taken/will take some time to get this right this wee=
k):
>=20
> FalconJx can now parse both FlexJS MXML and AS reasonably correctly.
> If run from the command line, it will now create the correct output
> directories (bin/js-debug and bin/js-release) and emit all JS and HTML
> files, both plain text (debug) and optimised using the GCC (release).
> Please use these command line arguments:
>=20
> +env.PLAYERGLOBAL_HOME=3D/Users/erik/Documents/ApacheFlex/dependencies/Pl=
ayerGlo
> bal/player
> +playerglobal.version=3D11.1
> -load-config=3D"/Applications/Adobe Flash Builder
> 4.7/sdks/4.9.1/frameworks/flex-config.xml"
> -library-path+=3D/Users/erik/Documents/ApacheFlex/git/flex-asjs/framework=
s/as/li
> bs/FlexJSUI.swc
> -js-output-type=3DFLEXJS
> -output=3D/Users/erik/Desktop/FlexJS/fromEclipse/FlexJSTest.js
> -closure-lib=3D/Users/erik/Documents/ApacheFlex/dependencies/GoogleClosur=
e/libra
> ry
> -sdk-js-lib=3D/Users/erik/Documents/ApacheFlex/git/flex-asjs/frameworks/j=
s/FlexJ
> S/src
> /Users/erik/Documents/ApacheFlex/git/flex-asjs/examples/FlexJSTest_again/=
src/F
> lexJSTest.mxml
>=20
> NOTE: please use the -sdk-js-lib argument to point to the library you
> want to use, instead of the previous 'vanilla' themed one.
>=20
> Also worth mentioning: as of now, the application doesn't do anything
> in the browser, due to some unfinished business in the emitted JS
> (mainly places where 'goog' is still used, instead of FlexJS). This is
> my todo for tomorrow...
>=20
> Have fun,
>=20
> EdB
>=20
>=20
>=20
> On Tue, Mar 26, 2013 at 11:33 PM, Om <bigosmallm@gmail.com> wrote:
>>>> So, I need to research more about how skinning works in HTML5, but I h=
ave
>>=20
>>>>> this vague recollection that skins in HTML5 are entirely graphics.
>>>>=20
>>>>=20
>>>> I dont think so.  SVG is part of the HTML5 spec now, so what we are do=
ing
>>>> is completely legitimate.
>>> That's sort of what I meant.  I think a skin in HTML5 doesn't have
>>> sub-components, and is a bitmap or SVG.
>>>=20
>>=20
>> Ah, got it.  I dint read your sentence that way earlier.
>>=20
>>=20
>>>>> I also need to understand how an HTML5 button skin changes its visual=
s
>>> with
>>>>> hover/down/selected/focused/emphasized.  That would also educate how =
we
>>> set
>>>>> up a skinning model for FlexJS.
>>>>>=20
>>>>=20
>>>> Here is an example: http://demos.madeinthenorth.com/slicker-buttons/#
>>>> Notice how they use SVG in IE9 and CSS3 for Firefox and Webkit.  This
>>> also
>>>> shows how to use CSS to control the various states.
>>> I took a look at this post. It uses the "hover" pseudo selector as
>>> expected.
>>> But the button did not have support for things like focused and emphasi=
zed.
>>>>=20
>>>=20
>>=20
>> If you can share some examples you like, that would be useful for me.
>>=20
>>=20
>>>>=20
>>>=20
>>>>=20
>>>> A restriction on skins to not have sub-components would be great IMHO.=
  A
>>>> new suffix would be great as well.  One more modification from our
>>> current
>>>> spark skins would be to perhaps have a HostInterface instead of a
>>>> HostComponent in skins.
>>>>=20
>>> Actually, I don't envision any sort of HostInterface or HostComponent
>>> contract for skins.  The actual skins shouldn't really know anything ab=
out
>>> the host.  The view bead, which sets up the sub-componentry for the vis=
uals
>>> may bind to the component's model.
>>=20
>>=20
>> In that case, it should bind to an interface of the component's model an=
d
>> not any specific implementation.
>>=20
>> Thanks,
>> Om
>=20
>=20

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