Le 10 oct. 08 à 20:04, Uli Kusterer a écrit :
On 10.10.2008, at 07:15, Graham Cox wrote:
On 10 Oct 2008, at 11:30 am, j o a r wrote:
Most apps use just the name, but I've never liked that and I
support your idea of using the bundle identifier. Makes a lot of
sense.
Yep, seemed to make
On Oct 10, 2008, at 3:31 AM, Graham Cox [EMAIL PROTECTED] wrote:
Why is anyone poking around in there? (Not a rhetorical question,
I'm interested in knowing what people do visit that folder for)
Since you ask, in my one-user, non-document-based scheduling app, I
keep the data file in there
On Fri, Oct 10, 2008 at 1:15 AM, Graham Cox [EMAIL PROTECTED] wrote:
I think I'll do it this way unless I hear some good arguments against.
The user might have very legitimate reason to play with things in
~/Library/Application Support. As such, I'd hesitate to confuse the
user with weird
On Oct 9, 2008, at 11:16 PM, Kyle Sluder wrote:
The user might have very legitimate reason to play with things in
~/Library/Application Support. As such, I'd hesitate to confuse the
user with weird names. In the worst case, the user might delete the
folder in confusion.
Your app's bundle
On 10/10/2008, at 4:36 PM, j o a r wrote:
The same thing could be said about preference files too though, and
they're stored using the bundle identifier per default.
The name is also not as stable as the bundle identifier. The name of
the app could, for example, be localized in the
On Fri, Oct 10, 2008 at 2:36 AM, j o a r [EMAIL PROTECTED] wrote:
The same thing could be said about preference files too though, and they're
stored using the bundle identifier per default.
Preference files are opaque; the user's interaction with preference
files should be (ideally) through the
On Oct 10, 2008, at 12:02 AM, Rob Keniger wrote:
This might be true but I have a lot of apps installed (more than
250, not counting the Apple pre-installed apps) and the count of
those that use a bundle identifier as the name of their folder in
the ~/Library/Application Support folder is
On 10 Oct 2008, at 6:06 pm, Kyle Sluder wrote:
You're going to be hardcoding the name of the folder anyway, whether
that hardcoding happens to be in the form of a string in your source
code or the CFBundleIdentifier in your Info.plist. Why needlessly
inconvenience the user when you derive no
On Fri, Oct 10, 2008 at 3:27 AM, j o a r [EMAIL PROTECTED] wrote:
Can you give a concrete example? I would argue that you're doing something
wrong if you ask your user to muck around in ~/Library. There are better
ways of solving the plugin problem - as demonstrated by both System
Preferences
On Oct 10, 2008, at 00:31, Graham Cox wrote:
I do tend to agree that it's not a place users should be visiting
routinely, and the app itself should offer an interface where
necessary to manage its own stuff in there. As with prefs, odds are
that the only time a user will ever go in there
On 10.10.2008, at 07:15, Graham Cox wrote:
On 10 Oct 2008, at 11:30 am, j o a r wrote:
Most apps use just the name, but I've never liked that and I
support your idea of using the bundle identifier. Makes a lot of
sense.
Yep, seemed to make sense to me too, but I don't think I've ever
On Friday, October 10, 2008, at 01:04PM, Uli Kusterer [EMAIL PROTECTED]
wrote:
On 10.10.2008, at 07:15, Graham Cox wrote:
On 10 Oct 2008, at 11:30 am, j o a r wrote:
Most apps use just the name, but I've never liked that and I
support your idea of using the bundle identifier. Makes a lot
On 11 Oct 2008, at 5:30 am, Ricky Sharp wrote:
Along with being readable, all my customers can easily back up
everything from my company (since all files ultimate resides in that
Instant Interactive folder). Or, they can choose individual
nested folders in case they have different backup
Hi all,
What's a good strategy for setting up a support folder in ~/
Application Support/?
I'm thinking of using my main bundle's identifier or the application
name to name the top-level folder, then maybe have a few subfolders
within there for specific types of files (such as document
On Oct 9, 2008, at 5:21 PM, Graham Cox wrote:
I'm thinking of using my main bundle's identifier or the application
name to name the top-level folder, then maybe have a few subfolders
within there for specific types of files (such as document
templates). Is that a good idea? What do others
On Oct 9, 2008, at 5:30 PM, j o a r wrote:
I'm thinking of using my main bundle's identifier or the
application name to name the top-level folder, then maybe have a
few subfolders within there for specific types of files (such as
document templates). Is that a good idea? What do others do?
On 10 Oct 2008, at 11:21 am, Graham Cox wrote:
a support folder in ~/Application Support/?
I meant ~/Library/Application Support/ of course.
G.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or
On 10 Oct 2008, at 11:30 am, j o a r wrote:
Most apps use just the name, but I've never liked that and I support
your idea of using the bundle identifier. Makes a lot of sense.
Yep, seemed to make sense to me too, but I don't think I've ever seen
it, which is why I hesitated.
I think
18 matches
Mail list logo
