• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Newbie: Current Apps Directory
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Newbie: Current Apps Directory


  • Subject: Re: Newbie: Current Apps Directory
  • From: Brant Vasilieff <email@hidden>
  • Date: Tue, 15 Apr 2003 22:52:04 -0700

Permits is a nice word. Please, just don't require them to be placed beside the application.

There are already enough applications that don't behave nicely within the Applications folder. This isn't Mac OS9 anymore. Many prefer to keep their Application folder populated with only launch-able items, not folders of applications.

If you have supporting data files, like plug-ins or books, the user or admin should be able to configure their system to find those computer wide in "/Library/Application Support/YourApp/", or user specific in "~/Library/Application Support/YourApp/". Any help books that you ship by default could easily be packaged within you application.

Attn: Douglas
It would be nice if there was a mechanism for handling dropping support files into the "Applications" folder. Something similar to the way Mac OS9 handles dropping fonts and extensions into the "System Folder." Let applications define their plug-in extension names, and a default installation installation path for when support files are dropped into the "Applications" folder. The system could then ask the user if they want to automatically move the items into the proper folders like in Mac OS9.

Whatever happened to the finder info pane for installing plug-ins?

Until then, we could allow our applications to handle the drop and, if it wasn't already installed, ask to place it in the correct location. This probably won't work as well for help books as it would for plug-ins.

You could always handle the help books the way OmniWeb does plug-ins within the finder's Get Info.

In the end there's not much difference between suggesting "~/Library/Application Support/YourApp/" and in "/Applications". If you only allow one, they're both restrictive. You should however make sure at least look in the Application Support varieties, because they're the standard locations.

Cheers,
Brant

On Tuesday, April 15, 2003, at 07:07 PM, email@hidden wrote:

Please don't make applications that do this sort of thing. Just put
the data file in the application bundle and access it via NSBundle's
-pathForResource:ofType: or put the data file in a
~/Libary/ApplicationSupport directory. Don't search the entire
Applications directory or clutter file systems with random data files.
This is just my opinion, and I don't mean to be insulting. I am just
expressing my (and I think Apple's) wishes.

Hi,
Hold on here. My application permits the user to place files in the
same folder as the application so the application can access the files
(all the files). I did not want the user doing complex selection in an
open panel. I felt the user experience would be simplified. Writing a
help book that tells the user to place a file in this or that ~/Library
folder is not a good idea (my opinion).

Is there any apple employee out there that knows of a "don't do
this...." file access rule?

Craig Bakalian
www.eThinkingCap.com
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Prev by Date: Re: Inconsistent Memory Management Rules
  • Next by Date: Re: Inconsistent Memory Management Rules
  • Previous by thread: Re: Newbie: Current Apps Directory
  • Next by thread: Array of variable types
  • Index(es):
    • Date
    • Thread