Hi Stu, Today's discussions are hitting the crux of whatever AngularJS 2.0 should be:
* -- built in RequireJS functionality* * -- CouchPotato lazy-loading on the fly for controllers and even directives* * -- "states" that are dynamic and multiple (on same page), built on the fly* * -- ability to "forget" code when memory gets scarce in a browser* * -- unlimited way to add new features to a web site, but never making these "obese" with a single-load approach at the start* * -- an architecture for many developers working in teams around the world to add new features to a web site* *add to this:* * -- secure log-in controls and authentication in order to cater to multi-layers of users -- outsiders just browsing, partners* * touching their data, customers tracking their orders and shipments, internal users running separate factory processes, * * sales, marketing, finance, personnel, etc. Security when accessing a part of a system has to be server-side controlled, * * based on profiles and just-in-time (lazy-load) access to HTML pages as well as DATA sources (read-only, modify, no access).* * -- lazy-load also means having "secret" pages and scripts that cannot load without previous authentication inside the main app.* We run a company that is expanding all the time, and we're trying to convert legacy client/server systems into web apps. We're hoping to develop a single strategy around AngularJS "thinking", so that everyone working inside the project is able to use tools developed with just one standard (anarchy sucks !). We're also trying to expand our features into customers and partners who will be "touching" parts of our corporate databases. After seeing how firebase can eliminate layers of database structures, all of this makes even more sense to build additional features. We're looking at just-in-time manufacturing data that can become new "bits" of pages where we can monitor stock in warehouses (in pictures), shipments (on maps), machines (giving a pulse of their states), and even farm equipment with GPS tracking. I can picture the solution, but I can't figure out how to code all of this, unless we have an enterprise platform that can be dynamically developed with many people involved within a single architecture. Hopefully AngularJS is that solution. Marcus On Friday, December 20, 2013 7:26:08 PM UTC+1, Stu Salsbury wrote: > > > > 1) patch RequireJS to support dumping its definition of a module in such a > way that it truly forgets that it already got a definition for it > 2) work around it somehow by playing with RequireJS paths so that it at > least *thinks* it's downloading a new module > > Anyone up for it? > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/groups/opt_out.
