Re: generating bundles without an extension?
Re: generating bundles without an extension?
- Subject: Re: generating bundles without an extension?
- From: Rua Haszard Morris <email@hidden>
- Date: Thu, 15 Feb 2007 08:47:43 +1300
Cheers both for your comments, lending weight to my understanding of
the situation. We're going to have an extension of some sort...
basically because of the "swimming upstream" issue (as opposed to any
clear info in the documentation).
only nitpicking remains...
but there seem to be some problems related to this:
1. The finder starts showing the bundle as a folder if no
extension is used (doesn't seem to matter if the extension is
something random).
Packages/bundles are folders with names whose extensions are
registered with Launch Services as belonging to a package. Look
at the plist of an application that supports some kind of package
document such as TextEdit (.rtfd documents are packages).
LSTypeIsPackage is documented as describing whether the app is
packaged, http://developer.apple.com/documentation/Carbon/
Conceptual/LaunchServicesConcepts/.
I've just tried setting it to true for the appropriate OSType in
the launch services bit of our plist, to no avail.
You'll need to use an extension you define for that to work.
Will I? Why? Where's this documented? The launch services
documentation doesn't say anything about LSTypeIsPackage applying
only to document types with an extension. And you can define a
document type based on OSType only. It's not stated that OSTypes are
only supported for legacy reasons, or that they only apply for non-
packaged (file) files.
And this has nothing to do with the finder anyway right? Or, doesn't
the finder implement part of launch services?
For example, is there somewhere that documents the fact that a
bundle _must_ have an extension in order to be displayed
correctly in the finder?
Mac OS X is extension-oriented. Not using an extension would be
nonstandard and could confuse some users. FWIW, you can set the
bit to hide the extension.
Yet Launch Services still supports OSTypes. I have nothing against
extensions, and have not seen any documentation encouraging me not
to use OSType in isolation for this purpose.
Understood, but that isn't the same as saying that you won't
encounter any issues if you don't use an extension. You may and you
may not, but I doubt Apple is investing a lot of resources to
ensure that bundles without extensions work without issues.
Yep, exactly, you're right.. like the finder may not do the right
thing..
Interestingly the CFBundle apis and our plugin loading/
management code works correctly even when the finder doesn't
show the plugin as a bundle.
That's a different system.
It is related though?! The "what is a bundle" rules are
consistent, right?
Yes, but you're talking about two distinct technologies: Launch
Services and CFBundle, and they can use different rules even though
within each technology the rules are consistent.
I guess 3 technologies including the finder.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden