Watch on
Localize "Previous/Next/Done" buttons on an iPhone project

For my latest project, I’m developping a cross-platform mobile application using PhoneGap/Cordova (which I heavily recommend!).

Anyway, I came across a problem: I couldn’t find how to get the “Previous/Next/Done” buttons on the iPhone keyboard to show up in my phone’s language.

The solution is quite easy: under Xcode4, go to your Project, Info tab, then add your country in the localizations part. That’s it!


PhoneGap 1.0 lets devs write apps for seven platforms

Watch on

My slides from Mr Mobble’s Magical Emporium, October 2011


Tutorial: Make an iOS App Using the Hype App, PhoneGap and Xcode (by MacsFuture)

Check out my video on how to make a native iOS app for the iPhone, IPad, or iPod Touch using no coding skills.  You can use the Hype App for the Mac to make HTML5 animations. You then use the PhoneGap plugin for Xcode as a way to import your Hype HTML5 project into Xcode.  Using these three tools you can quickly create native IOS apps with no code writing.  Pretty cool.

TerrariaHB Status Update

I have been looking into the issues with the app running on 1.5 and 1.5 however I haven’t really had any luck. I have found a few other people that are getting the same error that I am but so far there doesn’t seem to be a way around this. I am going to see if changing the version of phonegap it’s compiled on makes a difference.

The good news is that the app seems to be running really well on 3.2 and 4.0 emulators that I have setup. Due to how slow the emulators are I really can’t get a good feel for performance on these systems.

I took some time off of working on the app to get some stuff in my game done but I plan to get back to work on the new parser and finishing it soon.

Example HTML App Interface

I finally found time to build my PhoneGap demo app for Android. As you can see from the side by side photo below (and that really is an HTC EVO next to an iPhone 4), the app looks very much the same on Android and iOS.

For this demo app I used jQueryMobile and PhoneGap, so there are native Objective C and Java versions of the app sharing a common HTML interface. PhoneGap provided the necessary abstraction layer which allowed to me only write my app in HTML, JavaScript and CSS. 

I’ll admit this demo application is not as visually stunning as many games are. However, for many simple UI apps (think Facebook, Twitter, Foursquare, TripIt, etc.) having a single, consistent HTML interface like this is much easier to maintain than a native UI for every device you plan to support.

I’m planning on finding time to do something more elaborate in the near future but for now just consider the possibilities…

HTC EVO and Apple iPhone 4 running the same app

PhoneGap 0.9.5 and Android hardware buttons

Turns out that with PhoneGap 0.9.5 the way that hardware buttons (menu, search, back) are handled was changed. It really isn’t a bad thing, it’s becoming more unified, however, it caused me to spend a significant amount of time tracking changes so that I can upgrade my app.

In order to use back button:

document.addEventListener(‘backbutton’, function(e) {
// Your code
}, false);

In order to use menu button:

document.addEventListener(“menubutton”, function(e) {
// Your code
}, false);

In order to use search button:

document.addEventListener(“searchbutton”, function(e) {
// Your code
}, false);

All these functions should be called after PhoneGap is initialized (I call them onDeviceReady() ).


Mobile Web-apps

Agency: Lumia

Client: Unilever - Sedal

Developed by: Luis Nesi

Designed by: Luis Nesi


Tech Used:

  • HTML 5
  • JavaScript
  • JQTouch
  • Phonegap
Watch on

PhoneGap 101

Day 11: iPhone App, Part 4, 3/11/11

For today’s project, I wrote code to make the app tell me which time zone a desired time would occur in next and how it would be until that event, e.g. 32 minutes until 5:00pm in UTC-3.  Once I put in some code to match those time zones with locations, pretty up the app a little bit, and add a few customizable settings, I think it will time to try to put it in the app store.

Structuring a Combined Android & BlackBerry PhoneGap Project

Android and BlackBerry expect two different folder locations for resources. Android has its assets/www folder while BlackBerry expects just a www folder under the project root directory. Since the BlackBerry .cod file is opaque after compilation, it makes it difficult to understand how resources are structured in the file.

I found that putting the BlackBerry config.xml file under assets/www and referencing my HTML file within the assets/www folder worked fine as long as there is a www folder in the root of the project which contains plugins.xml, the ext folder with the phonegap.1.2.0.jar file, and a resources directory with my icons and splash screen image.

Make sure to modify the BlackBerry build.xml file to reference the config.xml file in the assets/www folder and to include both the assets/www folder as well as the www under the project’s root directory.

With this folder set up, I was able to successfully deploy to both Android and BlackBerry without duplicating any files within the project structure.

Once I integrate iOS into the project structure I’ll post the code on Github.

Does Adobe make me look fat?

Yesterday Adobe acquired Nitobi. It’s not a partnership — they won’t be renamed Adobi or Nitobe — it’s merely an acquisition. Adobe swallowing up a darling child of the mobile world in an effort to bolster a portfolio of more than 120 products that resemble the software equivalent of big fat couch potatoes.

As soon as Adobe becomes acquainted with something it usually gets a little chubby, loses its luster, and is then dumped and never heard from again. Adobe never wants to be seen with the fat chick. But what the hell… they are usually the ones responsible for the weight gain. That’s not to say Adobe doesn’t have some really good products, but they always seem to get heavier than they need to be. Kind of like the Adele of the software world — beautiful and talented, but would get even more fanfare if they just lost 20 pounds and always remained true to their roots.

We need only look at the long laundry list of purchases over the past decade to see that Adobe doesn’t always take care of its acquisitions. Tell me who you remember from this list and what significance the corporate identities play in the role at Adobe today:

  • Accelio (2002) took the technology for Acrobat.
  • Syntrillium (2003) Cool Edit Pro is merged into Adobe’s exiting editing products.
  • Yellow Dragon Technology (2003) an ebXML pioneer that was never heard from again.
  • Q-Link (2004) took the technology for Adobe IDP.
  • OKYZ (2004) 3D technology company.
  • Macromedia (2005) Flash, ColdFusion, DreamWeaver they *were* all the rage.
  • Navisware (2006)
  • TTF (2006) CAD system software.
  • Pixmatec Technology (2006) digital imaging software.
  • InterAKT (2006) content management, Intranet and e-commerce.
  • Actimagine (2006) vector graphics technology.
  • Serious Magic (2006) video and communication software.
  • Antepo (2007) technology used for future development of Acrobat.
  • Scene7 (2007) rich media solutions.
  • YaWeh (2008)
  • Business Catalyst (2009) hosting and e-commerce.
  • Omniture (2009) web analytics company purchased for $1.8 billion.
  • Day Software (2010) Web CMS
  • Demdex (2011) take a look at the Demdex website -
  • EchoSign (2011) electronic signature services.

Adobe has said all the right things. “We’ll adopt you, and love you just like your real parents. Only we can give you a better life. We can offer you the best developers, marketing, and provide you opportunities you could have never had if you stay with your birth parents.” Really, mommy? Okay, if that’s what’s best for me.

I would suspect the guys over at Nitobi got a nice payday — deservedly so. I’m not a non-profit, and I can surely respect that. Hell, I can respect that more than anything. I also know that *partnerships* like these never seem to last. I hope that the creative and intelligent group that was Nitobi can move on quickly and get back to developing one of the truly cool and unique products for mobile. Good luck fellas, please encourage Adobe to keep PhoneGap skinny, pretty and filled with personality. Like it was meant to be.

As a founder of the Breaking Development Conference, perhaps I should be excited to see this type of mobile web news hitting the mainstream? Though I’m not. I was hoping that the Sencha, Appcelerator, jQuery Mobile and PhoneGap’s of the world would become the next Adobe, not be eaten by the present one. Perhaps Adobe will elevate us all into a brave new mobile world? That, if it happens, I am excited about.

iOS Safariのalertとかconfirmのタイトルは変更できない


navigator.notification.alert(‘alert message’, function() {}, 'title’);