Startup preferences infrastructure

[LisaAlmarode]

JforD has a lot of toggle settings and startup preferences. I don't find a compelling need for any of them currently... there are a lot more important things.

However, we probably eventually will want some way to set preferences on startup. This may be handled differently in a Pharo dev environment than it would be on a windows-based application; it would be nice to not have to use a file, although a file may make it easier to move from image to image. It would be good to have a design for this in place.

I suggest autocommitEnabled as a preference that would be useful and easy (you'll need something for testing with).

[ericwinger]

I've ported the beginnings of the JfD preferences on startup system to JfP. Several things work like opening browsers, etc. a51f50b

[ericwinger]

• @dalehenrich reports that the autocommit preference isn't working yet

[ericwinger]

• Also, make sure Jadeite.prefs writes to the pharo directory on the client. Not sure why it's trying to go to the server.

[ericwinger]

Preferences file was using superclass workspace file menu options it shouldn't. Ctrl-S saves locally and a local save option was added to the menu. 0ab209e

Autocommit button display updates properly in console now. Preference was working but not displaying correctly.

[ericwinger]

I did some experimenting and was able to integrate a JfP setting into the Pharo settings browser.
Pharo settings are, by default, universal to all images so (in theory) you'd just need to hit Store Settings in the Pharo browser to save the settings for all your images.

Not sure which settings are universally helpful, but autocommit is one. Need to explore further.

[ericwinger]

Added open browser on class after connect setting. 7312ad0