incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: FalconJS "Demo" checked in
Date Fri, 30 Nov 2012 16:15:29 GMT
I think you can just work in the develop branch.  I'm going to be in the
falcon folders for a while anyway (I think).


On 11/30/12 8:05 AM, "Erik de Bruin" <erik@ixsoftware.nl> wrote:

> I've branched the root into my whiteboard.
> 
> I'm currently doing a major reorganisation of the JS framework (files,
> not code) and the general setup of the project. I've also started work
> on the 'publisher', that will take the AS, compile it to JS, add the
> JS framework to it and create the 'index.html'. There are empty dirs
> waiting for the unit tests and there is an examples directory in both
> the 'source' and 'published' directories. Please take a look and
> decide if this is something that would make sense to implement in de
> 'develop' branch.
> 
> Thanks,
> 
> EdB
> 
> 
> On Fri, Nov 30, 2012 at 8:02 AM, Alex Harui <aharui@adobe.com> wrote:
>> I branched my whiteboard into the root.  I decided to call it "asjs" because
>> we are developing parallel as and js frameworks.  There is a develop branch
>> in there where we should be making our commits.
>> 
>> -Alex
>> 
>> 
>> On 11/28/12 11:21 AM, "Erik de Bruin" <erik@ixsoftware.nl> wrote:
>> 
>>>>> Are we ready to put the framework.js in the FalconJS develop branch so
>>>>> we can all work on it?
>>>> IMO, framework.js shouldn't be in the FalconJS branch.  It is as
>>>> independent
>>>> of FalconJS as any of the AS code is independent of Falcon.
>>>> 
>>>> I would refactor framework.js into separate js files so we don't step on
>>>> each others toes and put it somewhere else in SVN and start adding to it
>>>> and
>>>> the .AS files.  We could start by having folks just work in my whiteboard
>>>> or
>>>> we can create a new whiteboard folder not under my name if that makes folks
>>>> more comfortable.  I was going to branch what I have checked in for further
>>>> modifications so what I checked in stays running.
>>> 
>>> Might I suggest a 'as2js' in the root of the repo, with branches, tags
>>> and trunk. In trunk (and/or branches/develop?) I would have an 'as'
>>> and a 'js' folder, and within each of those a 'src' and 'srcTest'...
>>> But that's just of the top of my head, so I'm open to suggestions ;-)
>>> 
>>>> Are you planning to use FlexUnit to test the AS side?  What will you use
>>>> for
>>>> the JS side?
>>> 
>>> FlexUnit seems to make sense for the AS. I use Jasmine [1] for
>>> JavaScript, so that would have my preference...
>>> 
>>>>> Question: I expect that we'll need to figure out a way to put the
>>>>> framework components through the Closure Compiler upon "publish",
>>>>> correct?
>>>> Yes, there is a missing step where we generate an index.html and collect
>>>> all
>>>> of the required JS files and minify them.  I'm hand-assembling stuff right
>>>> now.
>>> 
>>> Don't let Om hear it, or he'll start another AIR project :-) I'll give
>>> this some thought once we've set the rest up.
>>> 
>>>>> Another question: for your prototype you modified/bypassed parts of
>>>>> the SDK, it looks like. Does this mean that you envision 2 versions of
>>>>> the SDK, one for Flash Player deployment and one for web native
>>>>> deployment?
>>>> I'm not sure what you mean here.  For this new effort, I am not using
>>>> Apache
>>>> Flex 4.8 at all and have no plans to.  This is a next-generation and a full
>>>> rewrite with different goals.  What it has in common with Flex is MXML and
>>>> AS3 and many but not all APIs.  The idea is that for every component you
>>>> write in AS, you have to create its equivalent in JS.  You might be able
to
>>>> get FalconJS to help you create parts of the JS equivalent, but the parts
>>>> that touch the visuals pretty much have to be written differently.
>>> 
>>> This was the missing link in my understanding. We're writing a new
>>> SDK, fresh components on both sides of the FalconJS compiler.
>>> 
>>>>> I'll stop here and catch my breath ;-) I like what I'm seeing so far
>>>>> and certainly see the possibilities going forward. I do not share your
>>>>> caution about creating components that are more than basic
>>>>> implementations of available HTML controls. But we'll cross that
>>>>> bridge once we have a "working" version of the JS framework hooked up
>>>>> to the FalconJS compiler :-) First things first, right?
>>>> Definitely.  My only "caution" about creating more than basic controls is
>>>> how long it will take to create them. My goal is to get the basic
>>>> unskinnable 7 (Button, CheckBox, RadioButton, TextInput, TextArea, List,
>>>> Label) running ASAP so folks can actually play with it.  If you have the
>>>> time/energy to do fancier stuff you are more than welcome to get going on
>>>> it.
>>> 
>>> Sure, first things first though, set up this sub-project, ok?
>>> 
>>> EdB
>>> 
>>> 1:
>>> http://www.adobe.com/devnet/html5/articles/unit-test-javascript-applications
>>> -w
>>> ith-jasmine.html
>>> 
>>> 
>>> 
>>> --
>>> Ix Multimedia Software
>>> 
>>> Jan Luykenstraat 27
>>> 3521 VB Utrecht
>>> 
>>> T. 06-51952295
>>> I. www.ixsoftware.nl
>> 
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>> 
> 
> 

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


Mime
View raw message