It would be great. I mentioned something about it a couple of days ago or yesterday (I forget) in the "Proxy security and other problems" post. I think that all of the options should be kept as centralized as possible via tabs or a side menu (kind of like the settings in AIM, but simpler) in the preferences/configuration window rather than having to choose a different menu option for each project.
There is something to having a centralized settings for those with "farms" or just a bunch of computers. I think every client *should* have the option of changing locally. Changing settings online is an ok idea.
_I_ think that a good way to handle that kind of scenario would basically be able to have profiles outside of the current home, work, and school profiles, which you could name pretty much whatever you want (enabling you to have a lot of different profiles). I think that you should still select whether a profile refers to work, school, or home computers for statistical reasons though. The settings for each profile could be theen be changed and stored locally, but mirrored online for your account. The online settings would not even have to be accessible on the web, just stored there like AIM buddy lists and certain settings. Then, any other clients you had on other computers you would simply tell to use a certain profile (which could even be done as part of the installation process) and it would automatically retrieve those settings from online. From then on, if you wanted to change a setting for all of the computers, you would just change one setting locally, and internet conditionis willing, that one client would change the server settings, and it would propogate to the rest of the "farm" and update its local copy of the settings whenever it communicated with the server. Also, anytime you had to reinstall for some reason you could restore your settings from online easily. As part of the profile selection, you could also tell it not to use a profile and have the settings apply locally only.
An additional nicety of this would to be able to export settings to some sort of file (preferably with some kind of encryption if there are any sensitive settings included such as passwords) so that clients could be set up even if the server to retrieve settings faild to respond for whatever reason. Alternatively, one computer could be set up to provide settings to all other computers by setting up all of the other clients to take their settings directly from that client. Then, as long as the internal network worked, all settings on all computers could be changed at any time almost immediately.
The reason I like the idea of multiple profiles is because I have a work computer and several home computers. The home computers vary in processing power, the most powerful of which being my main computer, controlling the others via remote desktop. I generally prefer for my main computer to run SETI as its processor intensive task and thus I want to set it up so that it can process workunites as continuously as possible. My other "slave" computers I generally use for process intensive tasks other than SETI such as 3D rendering and audio/video compression. They don't do that all of the time so when they aren't doing number crunching my personal projects I want them to run SETI, but since they have other things they do, their settings need to be different. Maybe doing settings like that would require a little bit of work, but I really don't think it would be extraordinarily difficult. I have known several "amateur" programmers that could crank that type of thing (and have) in a day or 2 (since the basic structures are already in place). And I don't think it is an unreasonable request because I would imagine there are a pretty good number of people have multiple computers at one or all of the three of the current profiles that they want set up differently because of how the computers are used.