FWIW, here’s some Angular-compatible components: http://angular-ui.github.io/ http://angular-ui.github.io/bootstrap/ http://angular-ui.github.io/ng-grid/
and a whole site dedicated to cataloging Angular modules (some of it UI, and some of it business logic): http://ngmodules.org/ As you can see, except for the basic HTML elements, any UI that is used with Angular is going to be external modules from either existing UI frameworks (i.e. Bootstrap), or ones built specifically for Angular. None of these are part of the core Angular framework. I do think that for FlexJS to be successful, we would need some kind of public catalog of external modules (components) similar to the ngmodules site. On Jul 9, 2014, at 8:11 PM, Harbs <harbs.li...@gmail.com> wrote: > Angular is not really components. It’s more the glue that holds the > components together. > > Basically, the selling point of Angular is how it binds javascript to HTML. > Building custom Angular components is the hardest part of using the framework > (and for the most part is not part of the framework itself). They call them > “directives” and they have very unintuitive json markup that goes with the js > code. > > Angular pretty strongly prescribes how the app is put together and it’s > comprised of HTML template and directive files which comprise the view, and > controller/factory/service files which comprise the model and controller. > > > On Jul 9, 2014, at 7:44 PM, Alex Harui <aha...@adobe.com> wrote: > >> >> >> On 7/9/14 9:16 AM, "Harbs" <harbs.li...@gmail.com> wrote: >> >>> I wouldn¹t call myself an expert on the subject, but I have had the >>> opportunity to familiarize myself with both Angular and Create.js the >>> past half year. >>> >>> Create.js makes sense to integrate into FlexJS. I¹m not sure I understand >>> how Angular would/could be integrated. It seems to me that Angular is a >>> competing framework and I don¹t understand how the two could work >>> together. >> IMO, most JS frameworks offer a set of components that you glue together >> with JS. I'm not an expert on these frameworks, but I think Angular is >> one of them. Assuming the JS framework is not buggy, I think there is a >> lot of pain in writing and debugging the JS code that glues the components >> together (the rest of the pain is probably in browser-specific issues). >> TypeScript seems to have reached the same conclusion and offers a new >> language to do the gluing. I'd say Dart and GWT also have the same >> thoughts. >> >> FlexJS has the potential to be on-par or better as a way to do the gluing. >> We have IDEs, we have runtime verification, and we have declarative >> markup in MXML. >> >> Think of it this way. If IKEA or other assemble-it-yourself furniture >> makers shipped you a box of pieces cut to size and then just nails and >> screws and pre-drilled holes, you'd make a lot of mistakes building the >> furniture. Instead, these manufacturers use special connectors making it >> much more clear what goes where and making it impossible to make certain >> kinds of errors. >> >> IMO, classes are those special connectors. JS is just nails and screws. >> In JS, you can attach anything to anything and won't find out until much >> later. In FlexJS, we can offer both better connectors and a schematic >> diagram (MXML). >> >> -Alex >> >>> >>> On Jul 9, 2014, at 5:28 PM, Alex Harui <aha...@adobe.com> wrote: >>> >>>> I hope to attract Jquery, Angular, >>>> CreateJS experts and fans to build out these frameworks and making them >>>> wade through the current SDK would probably be an inhibitor to them. >>> >> >
