The problem with everyone being able to implement this themselves is that everyone has their own take on how it should be implemented and therefore each implementation will differ. Because of this, users of Shoes apps would end up with pref files (or whatever you want to refer to them as) stored all over the place, not just in the places deemed best practice by the OS.
Which is why if something like this is needed, it should be implemented as part of the framework. Those who need it can use it, and those that don't can ignore it. But at least it would be consistent across the board, regardless of the Shoes developer. Just my two-cents! -Mic 2008/7/4 Bluebie, Jenna <[EMAIL PROTECTED]>: > Sure, nothing about this can't be implemented by a shoes app developer, but > I think it's a common enough thing to be worth having in Shoes. Games like > to store Highscores and the colour of your pony, (Micro)Blogging clients > need to remember your blog's address and auth credentials. Even the > classbook sample could be made better by having it remember which story you > were reading last. But who can really be bothered writing a bunch of if's > and junk to figure out where to store the file and when to serialize and > deserialize and yadda yadda yadda just to remember which page you were on? > Making repetitive unfun tasks really easy and, heck, even a little fun, is a > sure fire path to great applications! Lets be nice and dry. This is > something that can be implemented in shoes for just a few lines of code > sprinkled here and there (I hope), and save us all one common repetitive > task on the road ahead. :) > > > And on that note, I think I'll go checkout the latest shoes and see if I can > implement this right now myself. >
