Just a heads up for anyone who has it … 1.03 of mySlate for iPad was just approved by Apple and should be propagating its way through the app store now. Here’s the changelog:

#WebView:

Added Bookmark Folders

Save Images with 2 finger tap on image

2 finger swipe left/right to go back/forward

#Photos:

Option to randomize the slideshow

#Videos

New display layout

#General

Change password

Contact Support from the app

Problem: You want to limit if a tableview cell is ABLE to move to a new section, or is limited to ONLY moving to a new section. For example in mySlate I’m supporting moving bookmarks to a new section/folder. However the bookmarks are laid out in alphabetical order inside a section/folder, so re-ordering them would do no good. Each time you open the bookmarks view they are returned alphabetically from the data store.

Solution:

- (NSIndexPath *)tableView:(UITableView *)tableView targetIndexPathForMoveFromRowAtIndexPath:(NSIndexPath *)sourceIndexPath toProposedIndexPath:(NSIndexPath *)proposedDestinationIndexPath
{
    if( sourceIndexPath.section != proposedDestinationIndexPath.section )
    {
        return proposedDestinationIndexPath;
    }
    else
    {
        return sourceIndexPath;
    }
//Reverse those to support only moving inside a section
}

Of course supporting movement in the tableview is yours to implement.

Source: stackoverflow

I spent the last few days trying to wrap my head around how to save a user selected image in a UIWebView. The concept itself would seem really simple, and if you’re using Safari on the iPad or iPhone it is really simple. You just tap and hold on an image. Simple. Problem is, when you’re developing you’re own application, this functionality doesn’t exist in UIWebView. Don’t believe me? Try it out for yourself. Go ahead… I’ll wait.

Ok, so if you’re still here you must have found out I’m right. The worst part of all this is I found out the hard way… from a user. I rarely save images from the web, so it never occurred to me to try it in my own app (and honestly I thought this was built in freebie functionality). Well, I got an email the other day from a user who was shocked that this didn’t work. He was not nearly as shocked as I was. I was even more shocked to find out that there’s pretty much nobody on the web who has discussed how to do this. Much time was spent searching for a solution, a couple tweets sent with only crickets responding, time was spent filling out a bug report with Apple (radar) only to have it closed without a work around as a duplicate. So, I basically hit a brick wall.

Alright, let’s get down to it. My complaining is done. Well not really. Did you also know its a huge PITA to handle touches in a UIWebView? Like to the point where you’re either having to sub-class UIWindow to trap touches or you’re having to add a view above the UIWebView. I’m going to leave it up to you as to how you want to implement what we’re talking about. I personally decided to not bother with any of it. Why? Well, I’ve already started building in a bunch of gestures, so it just made sense use a gesture recognizer instead of adding in a bunch of code which may or may not end up breaking sooner than later. My hope is that Apple fixes the problem, but I’m not holding my breath. Anyway, choose for yourself. For this example we’ll just follow the KISS method.

Ok, here come the code. First things first, you need to have some kind of way to collect touches. For simplicity we’ll use a UITapGestureRecognizer:

UITapGestureRecognizer *doubleTap = [[UITapGestureRecognizer alloc] initWithTarget:self action:@selector(doubleTap:)];
doubleTap.numberOfTouchesRequired = 2;
[self.webView addGestureRecognizer:doubleTap];
[doubleTap release];

What we’ve done is simply define a gesture (two fingers on tap the screen at the same time) and add that to the webview. When the webview detects two fingers on the screen (tap) it’ll fire the doubleTap method which is where we’ll figure out what image has been selected (if any at all).

- (void) doubleTap:(UITapGestureRecognizer *)sender {
	int scrollPosition = [[self.webView stringByEvaluatingJavaScriptFromString:@"window.pageYOffset"] intValue];
	CGPoint startPoint = [sender locationInView:self.webView];
	NSString *js = [NSString stringWithFormat:@"document.elementFromPoint(%f, %f).tagName", startPoint.x, startPoint.y+scrollPosition];
	NSString *value = [self.webView stringByEvaluatingJavaScriptFromString:js];
	if ([value isEqualToString:@"IMG"]) {
		NSString *imgURL = [NSString stringWithFormat:@"document.elementFromPoint(%f, %f).src", startPoint.x, startPoint.y+scrollPosition];
		NSString *urlToSave = [self.webView stringByEvaluatingJavaScriptFromString:imgURL];
		}

//Do whatever you want - like a UIAlertView or UIPopover to let the user chose what to do with the image
}

So, let’s walk through the code. The first thing we need to get is where we are on the page. Without this vital chunk of information we end up sending the same coordinates to the document so even if we’re at the bottom of the web page, when we tap the top of the screen it sends the coordinates for the header image. Not good. Next we get the location of the tap in the webView itself. After that we determine which element is at the location where the user tapped. Notice we added the scroll position to the y coordinate so again we don’t end up with the same x,y all the time. ‘tagName’ returns back the element type – ‘A’, ‘IMG’, ‘IFRAME’ etc. We only want images right now (you could always grab the a ref if you wanted to do other fun stuff) so we throw an if statement in to check if the element is an image. If it is, we grab the URL of the element and do stuff with it.

When that code is all said and done you’ll end up with an NSString like so:
http://justanotheripadblog.com/wp-content/uploads/2010/04/3GiPad_thumb.jpg
Nice right?

So, that’s how I ended up saving images from a UIWebView without resorting to private API calls or other wacky business.

Sound Off: Did this work for you? Am I crazy and there was a much easier way? Please let me know in the comments. Thanks!

Credits: iCab Blog for the elementFromPoint idea – see Alexander’s comment on 9/1 11:55am, and the support folks at perfectbrowser.com who got me started looking at doing this through javascript.

There was not a lot of changes to the full version – just some bug fixes however due to my update to Snow Leopard I lost all backwards compatibility with the older iPhone SDKs so the new versions do not support any iPhone platform older than 3.0. The lite version is now ad supported and almost completely the same as the full version. This is a test to see if I can actually support development on ads… if it fails then I’ll end up going back to a truly lite version.

Finally, I think I’ve got a bug where if you take a picture with the camera it is not putting that picture into the app properly. I’ll try to track that down asap and get it resolved. Not sure why it started showing up now, but I have a feeling that its only a problem on 3.1…

Here’s something I know. I know I can’t draw. I know that when I get a great little idea for an iPhone app, that there’s a couple things which are going to give me a hard time before I even get down to considering code and that’s mapping out the application itself and drawing what its going to look like when it gets on the device. Well thankfully there’s at least one new tool to ad to my arsenal and that’s the iPhone Sketchbook.

Sometimes an idea is so darned obvious that nobody really thinks about it. There’s a ton of very good iPhone books and many of them discuss planning out your application before you start writing it. There’s also many people who (like me) have done this that hard way with an iPhone like shape on a piece of paper and then maybe some horrible little icon things to represent common elements like the status bar, the signal strength and the battery. My iPhone drawings are horrible and finally there’s a book for that.

The iPhone Sketchbook is the brainchild of Kapsoft and I love it. I’ve only had the chance to use it a couple times, but I can tell already that its the (near) perfect tool for capturing an iPhone app idea quickly and easily so that when you sit down to really think through an application your initial idea can be right there ready for you to implement it.

I’ve tried a couple different methods for designing applications and prior the the sketchbook nothing had really stuck. There was always free hand drawing on lined or graph paper and teamed with the iPhone Stencil I bought that worked out pretty well. Other tools (like OmniSketch) didn’t work out so well simply due to the complexity required just to capture an idea. Now, with the iPhone Sketchbook I’ve got a simple notepad which already has the iPhone laid out on paper for me, ready for my to start filling in the elements and making notes so there is no chance I can forget the details later.

Great concept and as I said “near” perfect. My only complaint is I would really like to see the iPhone itself be bigger and by possibly adding a second image on the page the sketchbook would be even better. On paper its life size, which is handy, but when doing an initial sketch I’m less worried about scale sizing and more worried about capturing the essence of the idea quickly. With more space to draw I think capturing the idea would be simpler and less concern would be placed on making sure everything fits.

That’s a fairly minor gripe however. And so far I’m really happy with the iPhone Sketchbook. If you’re an application developer looking for a great tool to capture ideas with, the iPhone Sketchbook definitely warrants a look. You can find out more about the sketchbook at Kapsoft’s Sketchbook Website, pick it for $14.99 at Amazon, or you can check out the video (not mine) below:

photo credit: BrianScott

I’ve gotten a couple of emails giving me some feedback about crashing in both applications. It would appear that some are having the app crash as soon as it opens, others are crashing when they hit the settings page and change the text options. To be honest I was able to recreate the crashes – but only on 2.x software. I had a report of the app dying on 3.0.1 but so far I haven’t seen that yet.

So, that brings me to the next points:

1. I have tried as best I can – but I can’t get any of my 3 devices to downgrade to 2.2.1 – without that I can’t test on device.

2. See the picture up there? Snow Leopard. Yea, it came out. Yea, I bought it. And while is rocks – there’s one thing that sucks… The iPhone 3.0 SDK on Snow Leopard DOES NOT support older versions of the SDK, and you can’t install older SDKs. So what does that mean? That means gCalWall and gCalWall 1.4 will be 3.0 only. With no way to test older iPhone builds there’s little I can do – SORRY!!!

3. gCalWall Lite is moving to an ad supported model. With a couple thousand users over the past few months (and over 50% of my full version users being cracked versions) – it was time to find a better way. So ad supported it is. But with ad support, I’ve decided to turn on basically everything from the full version in the lite version.

There you have it. That’s the update. Let me know what you think – and again I’m sorry for having to drop 2.x support. Unfortunately Apple has dropped 2.x support from the SDKs.

I’ve also decided to just leave pricing where it is. I think for what it does and the fact that I can’t set the wallpaper for you, it’s a fair price.

Again thanks to all who have purchased gCalWall. It’s definitely done well enough to cover a nice vacation with my lovely wife!

I just wanted to throw up a quick post on the current state of gCalWall. I know there’s some things that are a little “wonky”. Some (minor number) of folks have seen issues with all day events, and some other stuff like blurry images. I have every intention of doing everything I can to fix these issues. I also have every intention of working in some requested improvements. But at the same time, I haven’t made much of anything off of gCalWall wall – so while its a product I intend to continue working on, it’s not a “top” priority.

So, long story short – I’m working on it, but I wouldn’t expect to release anything (aside from a major affects everybody emergency bugfix) until the iPhone 3.0 software is released. Why? Well, there’s some things I have to change for gCalWall in 3.0 to work properly and I’ve already got a development build started. So, rather than try and maintain separate builds, I’m jumping ship from 2.x and moving on to 3.x…

and unfortunately they don’t look so hot. Now to be fair, the ratings/reviews are pretty decent from the folks who have taken the time to write them. They aren’t all positive, and some are downright rude, but unfortunate reality of the App Store is that (as Iliumsoft wrote) Apple really has designed the rating system to make it super simple for those who “hate it to rate it” and those who love it … to not rate it at all.

Now, I’m happy with what gCalWall has done. It has sold a “decent” amount of copies, and the free version has done very well. I’m never going to make it rich off the application (hell I’m never going to buy a broken down Honda off of it), but for being my very first attempt at building anything its done very well. Ultimately I took a lofty goal (capturing data from Google and getting onto the lockscreen) and for the most part I succeeded. I didn’t truly succeed, but the goal was impossible because Apple doesn’t allow access to the lockscreen. Ultimately, the failure of gCalWall is a failure of my own.

What do I mean by that? Well, I mean that the ratings for gCalWall are very low, because I mis-judged that people wouldn’t mind taking a few extra seconds and setting the created image as a wallpaper. The ratings are low not because the application itself doesn’t work – but because of STUPID restrictions placed on the developers, and my own mis-judgement that people wouldn’t mind the extra steps for the much added benefit of having a useful lockscreen.

Keep this in mind. I want to dynamically update the lockscreen when you run gCalWall. There’s nothing I want more. Its been written in the app description and mentioned in every fricking write-up on the web. I WANT TO DO IT. APPLE WON’T LET ME. So please – if you like the app, review it on the App Store. If your only complaint is that it doesn’t set the wallpaper – TELL APPLE, but don’t give it 1 star reviews because of that.

Long story short – the rating system is broken. Go read about the feelings a successful developer has about the process, and imagine how I feel. Not only am I getting my ass kicked by Apple once for limiting functionality, but I’m getting it kicked again by Apple for having a broken rating process.