6700Yuma wrote:
Exactly... read my mind.
something similar to the concept of a message box that asks "Do you want to browse hard drive for OEMs or do you want to go to www.website.com to download latest OEMs?"

...The initial download could already contain a number of OEMs most commonly used, and/or a document that very briefly explains the various OEMs available.


I hope all these points are being heard and noted.

Now if only we can get BigJ to implement what he drafted then we'll be in business!

I too am a developer, I'd be willing to help with a C# client.

Also...

- disable error reporting

JBabey's idea is AWESOME! This is becoming a REALLY user friendly project!

One thing to point out which would strongly support an app based system. The web site would serve as a single point of failure (or lawyer :( ) in which to fubar everyone. An app can live on in P2P land forever almost.

For the OEM directory, consider what sort of wrapper might be needed to create OEMs. There may be more info desired (or option sets for a given OEM) that would be worked out by the more expirienced builders. Sort of akin to minimal install, Frank's Sounds, Everything, etc. Also, there should be a way to "share" ROM config files. That way someone can download a smallish config, say from Saridnour, and then mod it more themselves (and possibly reshare it). Prevents a lot of reinvention when someone finds a ROM that is almost perfect.

I like JBabey's outline the best.

A few things to think about. Apologies if a lot of this has already been mentioned.

-Radio/PRL stuff. Will the app handle this? Or is it assumed that the user will make sure they have latest versions for their carrier?

-Extended ROM. Will the app give any options on this? Full/minimal version by carrier. Extended ROM as an OEM (which I think is the way to go). Extended ROM unlock. Ability to load your own cabs into Extended ROM...etc

-Regarding the above 2 points. Is the app only going to create an nk.nbf or also the radio and extended rom?

-Base ROM options. Need to be careful here. Some things like changing the look and feel or the ability to remove MSN, HTC apps might be no brainers but do we want to give users more options to get even leaner and cut closer to the bone. e.g. removing T9 keypad...etc. and have the potential for more errors.

-Registry edits. Do we just do as Jbabey suggested and let user enter registry changes. Or do we want to provide some built in options for the best the most often used registry changes. Perhaps we sort of build in a version of PPCHacks into the kitchen app. I know a lot of chefs will make their own custom Registry hack OEM that has an .rgu with all their hacks. Perhaps we find a handful of the best or create a handful and let a user just choose one of these as an OEM. Again, lot of room for error here.

-OEMs. Ditto what everyone has said about QCing OEMs. Also, regarding OEMs for commercial software, do we just do as we have been and leave out .exe from the OEM and let the user sort out putting in their own .exe into the OEM before cooking it in... or dropping it in /windows after cooking. This is another argument for downloading OEMs locally so that users can drop in their own .exes, or build in passwords for their purchased software into their .rgus.

Thats all for now. Great work team!

-j

If that's what you all have in mind I suggest you take a look at the app called NLite (google for it). It pretty much exactly parallels what you are wanting to do, but it does its thing on Windows installation CDs for the PC. You can remove unwanted components to save space/speed, add registry tweaks, and incorporate specially-prepared applications all to be preinstalled.

It's actually kind of interesting how closely that process compares to what we're doing with ROMs on the PPC. There are lots of differences in the actual procedures used, but conceptually they are very similar.

So for inspiration, check out nlite (it may even spur you to customize your own windows installation... beware it is just as addicting as this is. I'm nowhere near hard-core and I've spent hours and hours customizing my XP CD).

Yes, I have used n-lite to slipstream stuff into windows XP, and some friends have used it to add all their programs to a base install of windows XP. Really works a lot like has been described here.

One thing though, why would we need the cleanup step? Wouldn't you want to leave the base stuff untouched? Why not instead of changing anything in the original base stuff we download, the program automatically creates a new folder along with our others, where it copies everything over as it is needed, that way the original stuff never gets touched. All that stuff should be read-only so nobody will screw it up and thus screw up their phone. Just a suggestion.

I was just thinking this very same thing.. Have the addin section for OEMs, the registry section, and since we are getting to the point we can add OEMs do we really need the Extended Roms? or could we just do what was done in the Clean and Simple ones and just include them in the base rom? Or i guess maybe have a section to make your own Extended's or import a default carrier one. I still think on the part of it being local/web i think should be like apt-get (debian linux) where you can specify servers and hit update and it downloads a list of programs.. do something similar here where we add servers and it gets a list (Not the actual OEMs) of whats available. and when they check off what they want it then 'wgets' it.. just would need a structured layout on the server and submission format. also have it scan OEM sub folder in the apps dir for local ones in case the server is down/etc. I know alot of this has already been mentioned but since the nlite reference was made i thought of apt-get for the other part as an example and wanted to share it.

Great Idea
 

I think this is also a great idea, this is best for people who dont want all that other extra stuff that someone else might want.