Then add the nonsense terminology, term abuse and vacuous new non-concepts everyone’s pushing. Add to that the massive ever growing ever changing list of “tools” and everyone and their dog’s favourite language/DSL. You cannot be an expert in anything these days as nothing lasts long enough. although by then C++'ll be screwed up too ( currently planned revisions every 3 years but no doubt someone’ll need more community time to feel good about themselves and that’ll change to at least once every yr - like Android and look how that’s worked out). If I was younger I’d be looking forward to the day when you can write web pages in C++ and there’s no reason to use JS… and that will happen eventually (see webassembly / emscripten). I only got into Javascript 3 yrs ago and was very soon a total convert -now I’m looking forward to getting out of IT. and largely for the same reasons the (broken) promises (pardon the pun) of “write once - run anywhere”. Javascript will be a waste of another 20. Unfortunately it’s not replacing - we’re going round in a big circle again Java was a waste of 20 yrs. So it’s a big thing to chew, but compared to what it’s replacing, I don’t think it’s so bad. Also, I think it’s easier than learning to program natively in iOS, Windows and Android. So the learning curve is steep, but once you get through it, you’ll be able to do some pretty cool things. I’m very good at a few things, and pretty crappy at most others.) At least for me, it’s taken a lot of peeling away one layer of the onion after another, before I finally understand what’s going on. It turns out that, to be an Ionic expert, you have to be halfway decent at several other tools. I certainly held that foolish assumption. I think a lot of people start using Ionic, thinking they just have to learn one framework. But the situation is even worse than you think, in that it really helps to understand some basics of Node, npm, rxjs – and advanced Angular – to do interesting things with Ionic. Ionic’s routing tries to emulate that, instead of Angular’s emphasis on desktop isn’t the only poster here who tries to separate out different parts, though it’s probably fair to say he’s taken the leading role. Routing in phones and tablets is different from routing on a desktop. And it supports Angular 4, hence your project created with CLI 2.2.3 has ionic-angular 3.1.1 and angular 4 dependencies. To further elaborate on this, the Ionic Framework (ionic-angular package) you asked about (ionic 3) is actually on 3.1.1 at this time. So if you’re on the latest version of the CLI and you create a new project, it will probably be on angular 4.0.2 and ionic-angular 3.1.1 at the time of writing. No matter the version of the CLI you’re on, ionic start myApp -v2 (or with the new cli commands) will generate a setup with the latest version of the ionic-angular package and angular dependencies. It’s referred to as the ionic-angular package. where you’re code is based upon can be found inside the contents of your package.json. Ionic App Lib is actually documented over here and is mainly there to make the CLI easier to use. There are a lot of threads here on the forum about this specific distinction between the two, so I can understand your confusion. The CLI is there to make your life as Ionic developer easier it isn’t the ‘framework’ itself. That gives you most definitely ionic-cli version 2.2.3 since that’s the latest stable release. ![]() You would normally install the CLI with the following command: npm install -g ionic.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |