Then, when the Angular community starts catching up to jQuery in terms of plugins and extensions you can start refactoring your views to not use jQuery-dependent directives and then you'll just be able to drop the dependency altogether.Īlso the world has survived with Bootstrap 2 and Angular plugins for it for a while - is there anything you need in 3 that you couldn't live without? I'm sure you know this by now - newer isn't always better you shouldn't fix what's not broken etc. About Press Copyright Contact us Creators Advertise Developers Terms Privacy Policy & Safety How YouTube works Test new features Press Copyright Contact us Creators. Step 2: Added some CSS classes into the head section of index.html file. I have included app.js file as well at the end of all libraries. (I don't think people agree completely on this point but here's my two cents:) As far as the drop jQuery thing goes, as long as you keep all of your DOM manipulation inside directives there's nothing wrong with wrapping jQuery widgets (when you get good enough to write your own directives) because then the jQuery will be isolated to only how you express your models. Step 1: Created index.html file into sample-angular-bootstrap-typeahead and added all dependency files into head section of index.html file. You will get a better idea of how much learning/porting you'll have to do and how well it will meet your needs. If you haven't made a toy application in Angular, yet, I strongly suggest doing so.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |