I like the idea; yaml is so easy to use anyway perhaps there is no need
to clothe it, maybe add it to the manual?
Bluebie, Jenna wrote:
Applications sometimes want to save a little tidbit of information. A
little customization perhaps, highscores why not?. Lets have a
'cookies' hash? When the shoes app is closed, the cookie hash
is marshaled, maybe in to yaml, and stored in a file, in wherever the
appropriate place is on that platform... ~/.shoes/appname perhaps on
unixes, ~/Library/Preferences perhaps on Mac OS, and I guess Documents
and Settings sounds like the kind of place where you put that stuff in
windows... It would of course reload in to the hash when the app is
reopened. Can I get a yay or neigh on the idea?
Sure, we /could/ use an sqlite db.. but that's /so/ boring and more
importantly, annoying if all you want to do is remember some little
bit of information. Remembering stuff shouldn't require CREATE TABLE
to be done in advanced, and sql db's suck for heirachiel structures
(like the kind ruby and shoes are full of)
Final thought: On Mac Shoes, it'd be rather cool to store the settings
in a resource fork, but given the trouble this would cause with
running apps off FAT external drives and the dangers of potentially
sharing a shoes app with someone, unknowing of the attached personal
settings, so I guess it's not such a cool idea in the real world.. oh
well.
------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG.
Version: 8.0.134 / Virus Database: 270.4.3/1529 - Release Date: 01/07/2008 19:23
