[haiku-development] Re: Separation of application configuration, data and cache
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Wed, 11 Nov 2009 14:50:51 +0100
PulkoMandy <pulkomandy@xxxxxxxxx> wrote:
> Yes it makes more work for porters. But it also avoids having 2
> different
> APIs for doing the same thing, which is something we could call
> "bloat".
It would still be possible to provide an extra (static) library (or a
set of source code) that provides this API, and can be reused by porters
without too much effort.
Bye,
Axel.
Other related posts:
- » [haiku-development] Separation of application configuration, data and cache- Christoph .J Thompson
- » [haiku-development] Re: Separation of application configuration, data and cache- François Revol
- » [haiku-development] Re: Separation of application configuration, data and cache- Axel Dörfler
- » [haiku-development] Re: Separation of application configuration, data and cache- scott mc
- » [haiku-development] Re: Separation of application configuration, data and cache- Christoph .J Thompson
- » [haiku-development] Re: Separation of application configuration, data and cache- PulkoMandy
- » [haiku-development] Re: Separation of application configuration, data and cache- François Revol
- » [haiku-development] Re: Separation of application configuration, data and cache- Christoph .J Thompson
- » [haiku-development] Re: Separation of application configuration, data and cache - Axel Dörfler
- » [haiku-development] Re: Separation of application configuration, data and cache- scott mc