On Tue, May 19, 2015 at 12:34 PM, Alex Harui <aha...@adobe.com> wrote:
> > > On 5/19/15, 9:11 AM, "Michael Schmalle" <teotigraphix...@gmail.com> wrote: > >3. FlexJS IS a javascript/html framework. > > > >I have a really bad problem of over thinking things. Alex, what I am > >trying > >to do right now is digest 2 years of development within a couple weeks > >time. :) My goal is mobile targets with FlexJS and Cordova. SO I really > >need to know the edges of the framework because not only to I have to know > >the limitations of FlexJS is, I need to know HTML/JS limitations. > > OK, I’m not sure what “edges” are in your mind so keep asking questions. > It is a good way of getting more information out to everyone else who > might be following along at at some point it may make sense to organize > some of it on the wiki. > Edges in the context of what I am thinking in are my boundary of understanding. I always have low self confidence until I get to the point of understanding what I "can't" do with something. Weird I know but it has served me well the last 10 years with software dev. I am a dreamer, so I dream up things I want to do; right now, I don't feel the boundaries of what FlexJS is capable of abstracting. Obviously I can google all the things I want to do with HTML/JS, search if it works on mobile etc. In other words, I don't feel what I can't do with FlexJS right now, hence my trying to understand the javascript part of the framework, the non cross compiled part. I am trying to figure out what is real using AS, what has to be written in JS, what shims are necessary, what are my limitations of the cross compiling. So basically, I am searching for the end of the road sign in the ActionScript development paradigm. Where it stops and only things can be done in JS. It's like when I feel this line, I can then start putting together all these ideas in my head, using mobile, web audio or whatever. I'm being really abstract here on purpose, my greatest "programming feats" have come from a gut feeling, I just don't have that feeling with FlexJS yet, so I am trying to find it. > > A key thing about FlexJS though is that we are trying to make the tools > “framework-agnostic” so I’m not sure there are as many edges as there are > for a monolithic framework like the current Flex SDK. If Josh were > starting Feathers today off of FlexJS, in theory he wouldn’t have had to > muck with the compiler at all. > > Hmm, here are couple of “rules” that popped into my head (and keep in mind > there are exceptions to every rule). > > -Compilers shouldn’t generate code, they should generate data and byte > code (JS is the "bytecode" for the browser). > -The lowest-level of a framework should re-use as much of the > platform/runtime/existing code as possible. That’s why we use the Flash > SimpleButton instead of building a button on Sprite, and why we use > HTMLElement button and why we thinly wrap Jquery and CreateJS components. > > Agreed. Mike > > Glad to have you in the discussion, > -Alex > >
