|
Why not K.I.S.S. (keep it simple stupid) an ap would be the simplest to implement which would include the base kitchen and then it could search for whatever OEMs are in the local OEM folder and include them in the build. There could be a couple of other folders such as EXTENDED_ROM and perhaps CABS posibly even TWEAKS and REGISTRATIONS for further customizations.
One strong vote for an ap (in my opinion) is that it is a standlone entity. If it were only a web based page/ap it could easily disapear if something happened to the host, or if MS didn't like it being available.
As well it would take a huge hit on the servers: let's say I build a rom today and tomorrow I decide I wish I had included something else - or wish I hadn't included something, with an ap I would only dl the new OEM, or just remove the one I don't like from the OEM folder... Not re-download the whole package every time I want to tweak a little something.
As well if I wanted an assortment of options I would only need to keep extra OEMs not try to name the resulting file something that would let me know everything that I chose oem-wise to make it.
If we were a OEM provider, or manufacturer ourselves the web version would be best, but since we're not, and ms did what they did to xda...
I really feel it should be an ap.
|