Another post about PhoneGap 3.0! So - I don't work with plugins a lot. I play with them every now and then, but I would certainly not consider myself an expert. Therefore, most of what I'm about to share here may be common knowledge, and if so, great, but I lost an hour or so yesterday trying to understand how to install a plugin via the command line and I figured a quick overview may help others.
A tip of the rage wolf to fellow Adobian Brian Leroux for his help with this blog post. And by help, I mean he basically explained it all to me and I'm just making it pretty.
One of the big changes to PhoneGap 3.0 is in how you install it. Previously you would download a zip file, expand it, and have all the bits you need. Now the installation process has you use npm (Node Package Manager) to grab the bits.
I'm currently working on an update to my jQuery Mobile book (jQuery Mobile Web Development Essentials), but for those curious about one of the cooler new features of jQuery Mobile, check out my new article on DZone (and yes, I am doing a lot more articles this year - all part of the master plan):
I've seen a lot of people (including myself!) have some issues with PhoneGap 3. It is definitely a big change from previous versions. I thought it might be good to have an open meeting over Connect (this is our online meeting solution, all you need is a browser) later this week to talk about it. This won't be a formal presentation per se (although I've got a few slides in mind just to help outline the discussion), but rather a chance for me to explain how things have changed from earlier versions and talk about some things you can to make the process easier. It is also a chance for you to ask questions and share your thoughts about PhoneGap 3.0.
I won't pretend that I'll have all the answers, but I'll do my best to gather questions and - at worst - bring them to the smarter folks and try to get answers posted here as soon as possible.
The meeting will be this Friday, September 6th, at 1:30 PM CST. You can attend by simply going to this URL: http://experts.adobeconnect.com/pg3ftw/. If you think you will attend, please RSVP by posting a comment below. (You don't have to, I'm just judging the expected size.)
Please note the date of this posting (Aug 21, 2013) - what you are seeing here should be fixed rather soon and is probably not an issue at the time you're reading this. I ran into this last week and wanted to blog it in case others hit the same hurdles.
I've recently spoken to more and more people who are working with PhoneGap on Windows, so I'm trying to get my own environment (well, my own virtual environment) up to shape. I even have an application I'd like to put out on the Windows app store. I ran into some significant issues with it (the app, not PhoneGap in general) with 2.9 but decided to try it again with 3. I ran into an interesting issue and I want to share it in case others run into it as well.
Before we get started, I should point out that today's blog entry isn't really PhoneGap specific. Any browser that supports WebSQL can make use of this entry. As WebSQL is a dead standard, I pretty much only use it in PhoneGap.
Just a quick note that I was honored to speak on the Authored Content pod cast. It just wrapped up live and you can watch the recording here. I talk about Creative Cloud, PhoneGap, and a few other topics. It was also pretty cool to meet the other guys (I had only met one of them before) and talk tech.
Just a quick post to point out this PhoneGap 3.0 FAQ posted by the team: PhoneGap 3.0 FAQ I want to add one quick note to this FAQ. One of the questions deals with Node.js and how it is a "mandatory requirement." I think it should be noted that while Node is used behind the scenes, there is absolutely nothing that you - as a developer - need to know about Node. Yes, you're going to install it, but you don't have to actually learn how to use it. You can install it and forget it (for the most part). The only exception I'd make to that is that you're going to want to know how to update the CLI at some point. That is typically done via: npm update -g phonegap.
Anyway - maybe I'm being too sensitive here, but I wanted folks who are considering PhoneGap to not be scared away thinking that there were multiple different things they would need to know beforehand. (Although if it isn't clear yet, I'm somewhat of a Node fanboy and recommend you learn it anyway!)
A few months back I wrote a quick blog entry on how you can modify the default www template used when creating new PhoneGap projects. While not a problem for most people, I tend to create a crap load of PhoneGap projects so I can test various mission critical important features. So it bugs me when I have to go in and remove the pretty, but useless to me, boilerplate code. Currently there is an open bug to allow for something along these lines at the command line, but in the meantime, you may be wondering where the default template exists now.