![]() The good news is that you can, of course, write JavaScript in your NativeScript apps. It made total sense once I figured it out, but it really threw me at first. Getting Your Route On with NativeScript-Vue: Episode Two.Getting Your Route On with NativeScript-Vue: Episode One.□ For more information, I've got two articles to help you out: Don't just tell me "I must do X" but tell me why as well.) (Which as a developer I greatly appreciate. The NativeScript folks have written up these rules as well as the thinking behind them. In fact, there's over ten different requirements a plugin has to pass. Verified plugins are checked for multiple different criteria, including things like have demos. (You can see in the screen shot above that the Image Picker plugin verified.) The last icon represents that this is popular plugin.Īnd remember how I said Cordova had a set of plugins they always ensure worked? Turns our NativeScript has something similar, "Verified" plugins.Second from the right is an icon representing Travis CI support and finally.The next two icons represent Angular and Vue (yay!) support.The TypeScript icon means typings are available.And then the "N6" icon represents the current NativeScript version supported.The "N4" icon represents the minimum NativeScript version supported.If you mouseover them you get a nice tooltip telling you exactly what they mean. That row of icons there provide you a quick look at what's supported for the plugin and with what JavaScript libraries it can be used in.ĭon't worry if all of those icons don't quite make sense. There's a great search experience here and make note of how plugins are listed: The NativeScript Marketplace has over one thousand plugin options. And going forward, I understand that NativeScript itself is a bit more "hands off" than Cordova and makes no assumptions about some plugins over others.Īll of that sounds somewhat scary perhaps, but it isn't a bad situation at all. When I ran into documentation problems I filed them as issues. While that's a fairly common problem to run into when working with open source projects (we're human, we've got limited free time, and docs tend to suffer the most), my expectation coming from a Cordova background was that it would be better supported. As an example, I ran into multiple documentation issues (all of which are fixed now I believe). It ended up being somewhat frustrating, so I turned my frustration into a blog post: Working with the Camera in a NativeScript Vue App. ![]() To be clear, this is possibly just my personal opinion, but I had a very rough time working with the camera and I had just assumed it would "just work". When I first began working on my NativeScript-Vue project, I was a bit surprised to find that camera support was not quite as stable. These plugins included fairly common needs like camera, location, and so forth. One of the things the Apache Cordova project did pretty well was define a set of "core" plugins that were guaranteed to work with the latest release of the project. That experience also colored my expectations and led to some surprises along the way. I'll also add that I had many, many years of experience with hybrid mobile apps using Apache Cordova and Ionic. However, I ran into a few things that surprised me along the way and I thought I'd share some tips for others looking to use their Vue experience to work with NativeScript. ![]() In general, it was an amazing experience. I got to use Vue while getting practical experience with NativeScript. I had been using Vue already for a while and had fallen in love with how easy it was. I was also lucky enough to be able to use NativeScript-Vue. It was only late last year when I had a client who wanted a demo built that I was able to truly get some experience with NativeScript. I was interested in it when it originally came out but never really had the time to get deep into the platform. After trying this out some more I came up with the following fix to the `app.hideToolbar` & `app.showToolbar`:Īpp.I've been a somewhat "casual" fan of NativeScript for some time now.
0 Comments
Leave a Reply. |