realbasic-nug
[Top] [All Lists]

Re: Best way to handle loss of ResourceFork

To: REALbasic NUG <realbasic-nug@lists.realsoftware.com>
Subject: Re: Best way to handle loss of ResourceFork
From: Norman Palardy <npalardy@great-white-software.com>
Date: Thu, 31 Jul 2008 08:56:47 -0600
Authentication-results: mx.google.com; spf=neutral (google.com: 74.124.194.228 is neither permitted nor denied by best guess record for domain of realbasic-nug-bounces@lists.realsoftware.com) smtp.mail=realbasic-nug-bounces@lists.realsoftware.com
Delivered-to: listarchive@realsoftware.com
In-reply-to: <p0600200cc4b777ca6932@[137.187.213.59]>
References: <mailman.3026.1217477886.19703.realbasic-nug@lists.realsoftware.com> <p0600200cc4b777ca6932@[137.187.213.59]>
Reply-to: REALbasic NUG <realbasic-nug@lists.realsoftware.com>
Sender: realbasic-nug-bounces@lists.realsoftware.com

On 31-Jul-08, at 8:25 AM, jda wrote:

ResourceFork is deprecated and scheduled for oblivion

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

That said you might look at other means of storing this data so it's easy to get at

When you initially open the application and list all the files load the meta data about them into an in memory database Then when you add / remove or alter things about the files you can update that database
This should be an order of magnitude faster than resources





_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>


<Prev in Thread] Current Thread [Next in Thread>