look, i don't want to get into a fight with people, but i can really say that the google closure toolset makes every other html/javascript approach look absolutely stoneage. a compiler, i mean a real compiler, it eliminates dead code, does your optimisations for you, you don't have to write javascript like you are the compiler. if you play nice and religiously annotate your code, you get static type checking (huge benefit!) proper OO, interfaces (granted no way to really do is-A)
lots of components http://closure-library.googlecode.com/svn/trunk/closure/goog/demos/ components actually have a livecycle (believe me, for most people playing around with javascript this is a radical concept). there is a framework (called relief), but i don't use it, it is not trying to solve the problems I am solving. I implemented my own binding system in a matter of hours, you can even add your own passes to the compiler (at any point, so pre abstract syntax tree (AST) or use the AST to do your own transforms) I tend to code in netbeans since the code completion is decent and I can also say the chrome debugger and profiler is extremely sweet. other people use different tools. if you like flex I think you will like closure, it is like the step up from flash to flex which I took in 2004 and I went like whooooaaa this is awesome. check this video http://www.youtube.com/watch?v=M3uWx-fhjUc now the bad, people don't seem to know about it, so it does not get all the loving it deserves, the lists however are extremely responsive (there are lists for all the different parts of the toolsets, but using all of them together makes for insane results) the compiler is not very fast, but using stuff like plovr (build tool) people make life pretty easy. i am just going to flame here as a finish, but jquery is for building mom and pop crap, if you plan to do any kind of real development in javascript and you like your wrists, closure is really the only way to go IMO. On Thu, Oct 13, 2011 at 9:52 PM, jamesfin <james.alan.finni...@gmail.com>wrote: > ** > > > As a devoted flex developer of over five years now, I'm getting the nudge > by management to get as comfortable with HTML5/Javascript as I currently am > with MXML/Actionscript. Not my decision. > > That said, I figured this forum would be better suited to answer a few > questions about html5/javascript rather than a endure throught a few > flash-hater filled javascript forums. ;) > > Knowing the following about common flex development practices, what are the > analogs with flex when using javascript, if any at all? > > FlashBuilder = ? (i.e. dreamweaver?) > MXML = HTML > Actionscript = Javascript > RobotLegs = ? > AS3Signals = ? > Others, feel free to contribute... > > Also, > Using Robotlegs affords many comforts towards MVC development practices. In > that context, can other analogs be made in HTML5/Javascript where separate > files are used for each of these areas? Links and/or examples would be > great. > > View = ? > Mediator = ? > Service = ? > Model = ? > Controller = ? > Dependency Injection = ? > Signals = ? > > It would appear as if SproutCore shares some of the attributes we enjoy in > Flex but would like to hear what Javascripts frameworks are most friendly to > Flex Developers. > > Thanks in advance! > > > -- j:pn \\no comment
