Yes, just look at Dark Diamond theme INI files and you'll see that dealing with different resolutions in both portrait and landscape inside the same package was tricky but not so painful...
But, in the way it is right now, even if it's a bit tricky, the numbers of different settings we have to deal with for each resolution are minimal compared to a single INI file for each one. And that's because there are not so much differences between resolutions and most of all you've done a great job in the way PocketCM handles them: I just had to add about 10 specific lines to handle wide resolutions!
Portrait/landscape was a pain though!
Also I think I've covered almost any usual resolution.
I have just not taken square resolution that are using the usual width as height in account.
Applying those requests would make things easier for ME as I wouldn't have to rewrite any part of the theme (as it is already ready for this and, for me, almost finished). I'd just need to use 320x320 and 640x640 landscape backgrounds together with
mapimage to make things works.
PocketCM seems to work well this tricky way.
Portrait/landscape PLUS many resolution to deal with is certainly more complicated/unfriendly than using the right settings for each.
I'm following you on this idea, but you have to take into account that this is a very different approach.
This can be a priority in a programmer's approach but I personally think that if PocketCM needs enhancements, they lay (for the time being) in the user-related and "plus-features" stuff.
Perhaps resolution-specific INI files could just be an addition before breaking compatibility?
Edit: Just another thought: Why not just use resolution prefixes in settings.ini (like "portrait." and "landscape." instead of multiple INI files?
Happy thinking (this is worth it),
Alex.
Edited 4 time(s). Last edit at 04/22/2009 12:34AM by donpipo.