Hi, With all due respect for chasers of coolness (we need you idealists) Applications preferences are different from serializing the users's meta data with the document's meta-data together. Not the same. It's completely application specific but that's up to you where the line is drawn. Or should be up to you.
If you want to package a shoes script as an "Application", one that needs meta-data state (preferences) between invocations of your program, that's a lot different than the cookies meme that work every where you can copy them. A Shoes Registry, eh? Downloaded executable scripts with unknown user meta-data, with persistent settings. Nice idea but it fails the float test here. Most of what these proposed Preferences things could be done in simple Ruby script that your app 'requires'. No need for _why to go all #ifdef again and make up some API and embedded that cramp when we can do it ourselves in Ruby. So I did. I just know I'm reinventing a well worn wheel. A google search could save me hours but I like reinventing metaphors the manly way. Maybe, by ShoesFest July I'll have some script to share that you can debug or discard or replace. You can probably re-purpose your own scripts config code. I hope you do. It's not that hard until you let the abstractions and metaphors mingle and bubble up and down while waiting for someone else to do it. Then again, I suspect I'm clueless.
