On 23 Jan 2011, at 13:20, Fred Kiefer wrote: > A simple solution here could be to add some special handling for the > current application into NSWorkspace. Adding its plist contents even > when it isn't installed in a normal directory. But this may lead to > inconsistent behaviour later one, when make_services gets executed by a > different application and wont find the original application any more.
Perhaps NSApplication would be a better place for this? A lot of applications won't touch NSWorkspace in normal operation, but they will all use NSApplication (or UIApplication, in the future...). The NSWorkspace code, called by make_services, would then: 1) Look in the cache and check that all apps in the cache still exist. 2) Scan Applications directories for new apps and add them to the cache. This would mean that anything using NSWorkspace would see all apps that were either installed in their normal locations, or had been explicitly launched at least once by the user from another location. David -- Sent from my brain _______________________________________________ Discuss-gnustep mailing list [email protected] http://lists.gnu.org/mailman/listinfo/discuss-gnustep
