[openbeos] Re: BAppPrefs

Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx> wrote:
> On Mon, 30 Aug 2004, Axel Dörfler wrote:
> > Because file settings are usually bound to a specific application. 
> > I
> > think it might be beneficial to have a standard method for this
> > because:
> > a) finding the settings of a certain app and vice versa - have a 
> > look
> > to config/settings and try to map the files in there to existing 
> > apps
> > b) removing the settings when removing an application from your 
> > disk
> > c) probably having one file format for all settings files
> Sure, these are valid points, but they don't explain why you would 
> make 
> the functionality available through BApplication. Especially with a) 
> in 
> mind I would find it strange to ask my BApplication to get 
> information 
> about another app. BRoster seems more suitable, or probably even 
> better 
> another class.

True, but there is always a certain overlap between BRoster and 
BApplication, like BRoster::GetAppInfo()/GetRunningAppInfo() and 
BApplication::GetAppInfo().
So yes, the implementation would be somewhere else, but could be made 
available through thin wrappers in BApplication.
We would definitely need to make BApplication not the only accessor to 
that functionality, just to support add-ons having their own 
preferences and such.
A separate class would be okay with me as well, but I think BRoster 
would fit as well.

> > Wouldn't be session support something like flattening the whole 
> > running
> > app?
> Aside that this would probably be overkill, would quite likely also 
> be 
> more work for the developer. I believe, we already discussed this on 
> GE.

Yes, I vaguely remember - but flattening the app sounds interesting as 
well ;)

Bye,
   Axel.

Other related posts: