[Wing, P4350 ROM development] quicksite:
prscott1, I *totally* agree. Ivan should go for the lean release and not try to accommodate others so much, including me. A couple of points to be clear: (1) I've never expected or wanted Ivan to cater to the requests of people who've "pre-donated". My feedback in this thread has been very verbose because (a) I'm not concise when I am being precise :Dand, (b) I have this feeling that this ROM from Ivan is going to largely be the end of the road for Wing/Herald users as pertains to optimzing the performance of these phones, partially due to the hardware itself, as I learned in this thread, not being as robust as other models, and also due to chefs moving on to newer phones. So I have been trying to pull into this thread everything I can think of that has been associated with my use of the Wing, and where the areas of improvement could be. I know it's bogged down the thread in places (shortcut commands, active sync stuff, icons), so I'm sorry for that. It has just seemed like NOW OR NEVER.
​

(2) As for accomodating others, this has been my logic: I don't think it's even such a good idea to have a custom ROM made for me, nor am I asking for one. For me, all I ask is that for things that really are annoying (to me) from a useability point of view, just allow people to disable and enable things. Like PCM keyboard for instance. Even if it COULD be cooked in (and it cant for licensing reasons), I have no problem installing cabs. I just want my installations to not be obstructed by stuff coooked in, like the Touch Diamond Keyboard.

I don't know how many people here are expecting Ivan to release his kitchen for this ROM. I asked earlier in this thread how much diff there is in performance when an app is cooked in vs added by cab, and the answer was not very much at all. So, my philosophy is, why should Ivan spend an equal amount of time prepping a base for people to cook in their fav apps & configurations when, with a minimal ROM, they can just add cabs and maybe lose a microsecond of betterment in performance than if cooked in.

To that end, the thing that would make MY life a lot easier would be:

(1) a lean, fast ROM

with

(2) a ZIP or RAR file that has all the extra apps and utilities and cab scripts that I would want to install, so that I can do all of that in one primary action after flashing to the ROM. To me that's even better than a custom cooked ROM. My needs chnage, especially when the new iFonz is released next week. I'm going to use it, so many of my temporary needs right now for interface improvements go away in a poof in another week. Thus i have always liked the original concept of JUST STABLE. As lean & clean as can be, with some common basic apps that almost everyone agrees are best of breed. Then a ZIP or RAR of cab files -- the likes of which I have posted in this thread, or linked to, would be my add-on package. I unpack them on my Mac or PC, extract the cabs, and copy them to my storage drive (bypassing active sync whenever possible), and then knock them out one by one, install, install, install.

I think that's better because for the next ROM or update, there's less to overwrite and then rebuild the app configurations & settings again.

Lastly, I want ot remind some enterprising person here at XDA who happens to see this thread: It would be very smart for someone to build a for-fee app utility that saves off all config files related to any and all apps you have installed, and then restores those config files to their correct folders once those folders are rebuilt in a new installation of a ROM and/or apps. Whoever does this will make a lot of money on repeat sales. Priced at $4.99, I would bet you could see half a million of them once the WindowsMobile apps market comes online. It's taking what PIMbackup does and taking it further ---if it takes me X time to always reset up my S2U2 prefs and wallpapers, same ith keyboard and skin & layout, same with quick menu configuration, etc etc, it is way worth it in my time to pay for a neat little app that grabs all that stuff, then restores it later. hint hint hint :rolleyes: