View Single Post
Posts: 607 | Thanked: 450 times | Joined on Sep 2009 @ Washington, DC
#129
Originally Posted by Laughing Man View Post
Well considering Nokia and Intel's goal is to run Meego on nearly everything, if a developer wants to create a multi-touch only app, then their app is only marketable to devices with multi-touch capability. Meego isn't N900 + next Nokia device. Meego is netbooks, mobile devices, TVs, etc..thus a developer that wants the largest audience will make an app that isn't limited to certain hardware forms.
I fear you are right but you shouldn't be. A developer should program for the most capable device and both the app and the OS should gracefully degrade the app when the capability doesn't exist. If Meego ends up with a bunch of apps designed to run on non-touch netbooks it will die. If it winds up with a bunch of apps that are not usable without multi-touch, it will die.

If I run a well written Windows program on my OQO, it detects that I'm running in 800x480 and it adjusts while my desktop runs 1280x1024 and, again it adjusts. My OQO has an active digitizer so programs like Acrobat let me do ink annotations while my desktop does not have a digitizer so I don't see that function. This auto-configuration started from the initial install of Win7 which turned off Aero on my OQO because it didn't detect sufficient graphics hardware acceleration.

The point is, I don't have to do anything - no options, no preferences, no configuration, no hacking - to make this happen. That is how a developer should write for Meego. Figure out what device you are running on and adjust all the program's options accordingly.
 

The Following 2 Users Say Thank You to DaveP1 For This Useful Post: