On Sun, Jan 18, 2015 at 01:49:27PM +0100, Ingo Weinhold wrote: > On 01/17/2015 02:49 PM, Adrien Destugues wrote: > >I am trying to use BPathFinder to iterate over available add-ons for an > >application. It works for the system-wide directories, but doesn't > >include the app-local ones (%A/add-ons). There is a similar behaviour > >for libraries. > > > >Should these be added to the paths BPathFinder returns (possibly with a > >specific flag to enable them)? This would be good for symetry with > >load_add_on, which does search there when given a relative path. Or > >should we leave this up to apps (getting the application path from > >BApplication, etc)? > > I guess a flag for that purpose doesn't harm. Regarding the add-ons, I > wonder, if there's any application that actually uses the feature to > override global add-ons. And looking e.g. at the TranslatorRoster code, it > doesn't seem to support that anyway; I suspect it's even less likely for > media add-ons. I'm trying to write one :) I'm porting an application from MorphOS and I want to use the same locale catalog format as the original so the translations can be shared. I wrote a locale add-on to parse Amiga-format catalogs, which I would like to distribute with the app, without requiring the user to install it, and without having it trying to load catalogs for other applications. I will keep this under a flag then. -- Adrien.