On 5 Feb 2009, at 18:29, I. Savant wrote:
On Thu, Feb 5, 2009 at 1:21 PM, Josh de Lioncourt
<overl...@lioncourt.com> wrote:
There are several reasons we're not doing it this way. One is that
our
application data will be stored in a customized format that is
*not* a
.plist file, because we need to maintain cross-platform support.
Yes, I
know that technically I could write WIndows code to parse
the .plist, but
the better, simpler solution for our specific situation is
customized data
files. It doesn't seem wise to me to store non-.plist files in
~/Library/Preferences. Believe me, I'm very familiar with Mac. I
actually
realy dislike Windows, and if I could drop cross-platform
necessities, I
would. :)
Your reasoning doesn't quite seem ... reasonable to me. :-)
Specifically, when would your Windows version be reading the Mac
version's preferences and vice-versa? Presumably your user has *data*
they wish to share between their Mac and their Windows computers,
which is one thing, but the *preferences* are specific to the app /
machine (and even more specifically, the user), right? Why not use
each platform's native preferences/settings interfaces to store this
information where it belongs?
I think this reasoning makes even more sense when you consider those
users out there having MobileMe synchronise their preferences. With
your custom approach, this would break, against the user's expectations.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
