On the Mac I use ImageAlpha to reduce the colours to 256 (it has a preview window so you can see if it's OK), then when saving the file I choose the option to send it to ImageOptim.
On Linux you can get the same by using pngquant, then using trimage. AFAIK there's no GUI frontend for pngquant so I guess how many colours would be ok and check before running trimage.
The reason why I use 2 tools is that ImageAlpha/pngquant is lossy and ImageOptim/trimage is lossless.
He provides one example - Vienna. Where I live the transport companies are privatised but realise that by providing the data to Google they get more people using their services.
When Apple releases ios 6 they will have to create a new app just because Apple doesn't want to be compatible with the existing feeds that these companies are already providing.
Maybe they didn't want to take the risk of it being rejected as 'duplicating existing functionality'. I know that some apps have got through nowadays, but has the policy changed to allow this, or is Apple allowing these on a case-by-case basis?
No, they didn't do it because Apple was already paying them to use their maps.
If they came out with their own Google Maps application that had feature parity with the Android app, I would imagine that most iOS users would switch immediately to that app instead of Apple's built-in one.
That could have potentially cost Google a lot of money, assuming that Apple was paying on a per-use basis.
I'm sure the transit providers would be happy to provide the same feed to Apple and Google, but it looks like Apple want to make something new and incompatible.
> It makes some sense as it's not likely you'll accidentally delete one of your photos that way.
Well the file would go in the Trash, so if you pressed delete accidentally it's not a disaster. I use Presbutan so pressing delete on its own works, and pressing enter opens the file, instead of having to use Command-O.
My experience:
Phonegap: Responsiveness is bearable on iOS but on Android it is very slow - scrolling is choppy and there is a noticeable delay between pressing a button and seeing it activate. We abandoned it at this point.
Titanium: The layout code seems to be different between iOS and Android so if you get your app to look right in one platform it can be completely wrong in the other. On Android it bundles the V8 Javascript library so it's definitely not native code but at least with V8 the speed is not a problem. Titanium adds about 10MB for its stuff which is annoying to me as an old programmer!
region (optional) defines the appropriate borders to display, based on geo-political sensitivities. Accepts a region code specified as a two-character ccTLD ('top-level domain') value.
There's not enough contrast between the street names and the rest of the map, making readability a problem. It's the kind of design mistake that young people with nice monitors make!
This was designed primarily on a MacBook Pro running Linux, so the colors were oddly calibrated. We tested it on several other calibrated monitors, and a few other devices (iPhone/Pad/Android).
Short story is that it could be much bolder and more colorful, at the cost of aesthetics. A growing number of users have good screens - sometimes excellent screens like most mobile devices.
It'll probably look odd, just like everything on an old computer. Designing for the craziest CRT is just as bad or worse than designing for a cinema display.
I know this guy's being downvoted here, but he's got a point. I find people on nice, big cinema displays tend to make choices on colors and labeling that people with shittier monitors wouldn't make. Eg, colors that are very close, tinier labels, etc.
On Linux you can get the same by using pngquant, then using trimage. AFAIK there's no GUI frontend for pngquant so I guess how many colours would be ok and check before running trimage.
The reason why I use 2 tools is that ImageAlpha/pngquant is lossy and ImageOptim/trimage is lossless.