A problem I've now found with the whatIsThis()/isPackage() idea is
that though all the .bundle and .app folders I've looked at have a /
Contents/info.plist file, a .rtfd (rich text with additions) does not.
In TextEdit, create a rich text document. Type in some text, then
paste in an image. Save.
You'll now have a .rftd document. In the finder, control-click and
select 'show package contents'. All I can see is two files : 'Pasted
Graphic.tiff' and 'TXT.rtf'.
How would one identify this .rtfd document as a bundle/package? Of
course there's the file extension, but I think simply storing a list
of likely file extensions is going to fail sooner or later, as any
app may create document bundles if the developers so wish.
I've had a pretty good search around, and I can't find any useful
shell or applescript stuff, so it seems like the only reliable
methods involve system-level api calls - which implies an external or
an engine change...
And, as I think Chipp may have pointed out, bundles seem to show up
in the 'answer file' dialog, but not in 'the files'. This is surely
an inconsistency?
Best,
Mark
On 7 Dec 2007, at 12:21, Ian Wood wrote:
>> On 7 Dec 2007, at 10:41, Chipp Walters wrote:
>>> Kay and Ian,
>>>> Perhaps you both, being such fans of the simplicity and elegance of
>> bundles, wouldn't mind starting a revLibrary which provides file
>> operations on files/folders/bundles and share it with us less
>> enlightened?
> [...]
>>>> Here are some I'd like to see implemented, and might provide you a
>> start...
>> Sounds like a good idea to me, and the NewDelete functions would be
> useful to anyone on *any* platform as a workaround versus the
> dreaded 'kill the HD' bug.
>>> get theNewFiles()
>> get theNewFolders()
>> I think the starting point for these two would be something like:
>> get theNewContent()
>> which would return:
> filenameA folder
> filenameB bundle
> filenameC file
> filenameD file
> filenameE bundle
> filenameF folder
>> Which itself could start from some kind of whatIsThis() function?
>> theNewFiles() and theNewFolders() would then be a couple of lines.
>>> NewCopyFile pStartPath,pDestinationPath
>>>> which copies files and folders which are supposed to be
>> files...keeping their creator and type codes intact.
>>>> (is this the same as a revCopyFile?)
>> Yes, that's what revCopyFile will do currently.
>>> Maybe others can think of more?
>>>> -Chipp
>> _______________________________________________
>> use-revolution mailing list
>>use-revolution at lists.runrev.com>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>>http://lists.runrev.com/mailman/listinfo/use-revolution>> _______________________________________________
> use-revolution mailing list
>use-revolution at lists.runrev.com> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
>http://lists.runrev.com/mailman/listinfo/use-revolution