|
||||
Having multiple kitchens didn't seem like a good idea to me in the first place. As a programmer myself, I understand all too well how easy it is to dig into the code and make dozens of modifications and not document everything.
Unfortunately this is all too often the fate of undocumented (unsubstantiated?) code changes. It gets purged. Also, it felt that a "Clean And Simple" ROM Kitchen was to somehow imply that the others were not. From the "Clean And Simple" ROM Kitchen anyone could make their ROM as dirty and complicated as they wanted...just like any of the others. Perhaps a better public service would be to post the apps that are known to cause issues, and then say "leave these out for best performance" and then give the underlying reasons. Also, any other changes could be listed and/or debated by the core project members on usability, and then potentially incorporated into the unified Kitchen - or left to the user's discretion. I don't think anyone has problems with others creating new ROMs from the Kitchen and distributing them, but rather the creating of a new Kitchen and distributing it is the issue. So I don't see what the big deal is here.... just release your version as a standalone ROM. I know it sucks sometimes to work on something for days and then to pass it to the next guy who then just puts it in the system and just announces "Fixed ___" in the next release of product....but such is the evil/beauty of open source.
__________________
Microsoft, Helmi_C, No2Chem, NexVision, tiermann, Colonel, gguruusa, luv2chill, imcokeman, jakdillard...many others. Thank you. We are all on shoulders of giants.
What's in a name? That which we call a genius by any other name would be just as smart. I beat up Sprint and all I have to show for it is this lousy When you were in diapers and wetting the sheets I was out hacking with the ppcgeeks. |
|
||||
Backlight timer problem
I ran Jeff's new modified kitchen and flashed the new ROM last night and I'm having the same problem. Keeps automatically reverting back to 10 second backlight timeout no matter what I change it to. So far, everything else has been working great. Any suggestions on how to fix this one little annoyance?
Thanks for everything! Quote:
|
|
||||
Quote:
Also I think that limiting the ability to create and distribute our own kitchens goes against what this site is all about, sure someone could use the C&S and make a kitchen dirty and complex...but they could also make it cleaner and simpler as well as learn something. I think arguing that route is a moot point. Either way I guess we really do not know why it was taken down, maybe an official reason why would help us all understand. |
|
||||
Does/did this have the palm threaded SMS app? If not is copying that OEM folder in all thats necessary to get it working?
thanks Jeff looks like you did some very nice work!
__________________
verizon 6700
|
|
||||
This is very disappointing. I just downloaded the C & S a few weeks ago and it is awsome. Then I saw this last night and thought great, I wanted to learn the kitchen stuff. Then saw this morning that it was taken down.
maybe it will pop up somewhere. I still love this site though! |
|
||||
Quote:
As for my comments, the point is if you and I and countless others start releasing new kitchens we will have many different(?) versions of the same thing, and each with uncertain integrety. I could release one with a better name OR a higher version number than yours (although being the same in every other respect) and then I'd get all the attention and see my name in praise and contributions.... That's one of the many reasons I'm all for version control.... But on your side as well, I think people should be able to distribute whatever masterpiece/garbage they so choose, and keep all their secrets to themselves if they wish.... Each situation is different, and in this one if there was a vote - I'd vote YES - in favor of version control on the Kitchen within the context of this forum. |
|
||||
I am locking this thread. If Jeff Kirvin or anyone else here would like to create their own ROM kitchen for the Apache from scratch and put their name on it, feel free. But don't take someone else's work, make a few changes and call it yours. Don't be fooled people, that is all Jeff did here.
I personally have put in countless hours making tweaks and changes to the kitchen, but do I call it "Luv2chill's Amazingly good Apache kitchen"? No, I don't becuase I didn't make it. Making changes to something does not give me or anyone else the right to call it mine. Also, we are cracking down on this because it just has the potential to get out of hand. For one, it makes troubleshooting a nightmare. I personally have had several people ask me for help with "the kitchen" (both via PM and in the chatroom) and only after troubleshooting for a while do they admit that they were using "jbabey's kitchen" (which, again is not jbabey's kitchen at all but a bastardization of helmi's kitchen). Having one kitchen at least gives us some kind of constant to use whilst troubleshooting all the very many variables that can come up. There is absolutely NO NEED to have more than one kitchen. Everything Kirvin did (had he bothered to document it) could be done with correctly-designed OEMs, along with a batch file to make the file system and page pool modifications. You should also know that over a week ago I notified Jeff that releasing his "own" kitchen was not OK, and he acknowledged that and agreed not to, only to turn around and do it anyway without any notification whatsoever. Seemed to me a pretty crappy thing to do. |
|
|
|