Quote:
|
Originally Posted by colonel
A couple things to remember here: If you put it in a web based system, you cut off almost all customization for the user. Not only would it be very difficult for them to add their own OEMs, but any editing of the OS or LOC would also be difficult. I realize that this editing may not happen all the time, but personally, I am in those files a lot. Remember, anytime someone wants to change any of the graphics, sounds, themes, etc., they will either have to have a patch or do manual editing.
Also, we are gonna need some real testing and control over OEMs to "certify" them as functional. There are a lot of OEMs on the ftp and most of them are fine. But a lot of them have had corners cut (Help Files and such) and some of the OEMs are almost laughable.
Let us also remember that while it would be a great feat to have a kitchen that any "idiot noob" could use, we are still dealing with a certain level of necessary knowledge. Honestly, if someone cannot follow some detailed instructions on how to use the existing kitchens now, should they be messing with this type of thing? I am not saying that access should be restricted, but there should be a necessary level of knowledge for the users. Otherwise we will be setting ourselves up for thousands of questions about faulty roms and other noobish user errors.
|
The other thing this would lead to would be the required ongoing support: Adding and updating OEMs over the life of the application. That's in addition to Colonel's points above.
Colonel, what kind of format do you see for a standalone application, i.e., how would it work from a user standpoint?