On Jul 31, 2008, at 10:56 AM, Norman Palardy wrote:
Apple has basically said "don't use resource fork resources"
But that does not mean you cannot use resources
They'd just be in the data fork
And you might want to label the resource fork as dont use for future
development. But it should not be removed simply because of how truly
pervasive it was in preOSX and early OSX days. The resource fork was
used for EVERYTHING in the mac world up until very recently. So while
I wouldn't design a file format today that needed it, I still need to
be able to read the files I created in the past and the files that
other apps created in the past. There are a huge number of these out
there that we all still need to be able to read.
I got a nice response from Geoff at RS about this when I emailed him
my concerns and he is looking into perhaps pulling the resource fork
support out into a separate and potentially open sourced plugin. This
way it would remain around for those of us that needed it and yet not
continue to clutter up the RS toolbox of things they need to maintain
and test. I thought this was a perfectly reasonable response and would
be quite happy if that could happen.
So if you wish to have this around for maintaining compatibility with
older versions and older files (and really, they aren't that old!) you
might drop RS a note supporting having someone take the time to pull
those things out and into a plugin, rather than just removing them
completely. I haven't heard yet that any final decision was made,
there is some work involved in doing this, but I think it would be
well spent.
Thanks,
James
James Sentman http://sentman.com
http://MacHomeAutomation.com
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|