4 ms·
I watched video, it is just overview. We currently solving same problems and a bit more (we do heavy localization.) And unfortunately level of details provided
by hippich 12y ago
I watched video, it is just overview. We currently solving same problems and a bit more (we do heavy localization.) And unfortunately level of details provided in this video are not enough to see how specifically they e.g. load module, how they load module dynamically with angular, how they update routes and trigger these again, how they update dependencies in run time for already loaded and registered modules.
This proved to be more complicated than it should have been and I am looking to see real app in action to view code and learn from it. Paying (or becoming trial user) is not part of what I want to do to learn from that :)) That's why I was asking where actual app I can touch resides, if it is possible to try it without submitting my credit card details :)
- lobo_tuerto 12y agoThen the problem has nothing to do with AngularJS per se, but how you package and deliver a web app in general. You need to learn about asset management. Take a look at webpack for example: http://webpack.github.io/ http://webpack.github.io/ In the video they explain the strat behind how they managed to make a big app load only the necessary parts. With that, and some researching on your part should be enough to get you on the right track. In any case, your argument doesn't hold. It isn't only for small apps. ;)
- hippich 12y agoBelieve me, this is problem with AngularJS (mostly because they invented modules/dependencies and decided to stick with it despite obvious deficiencies instead of teaming up with other open source projects and using something like require.js Strategy is easy part, as this stuff done many times already. The devil is in details about how to actually get into guts of angular's dependency and routing systems.