Re: global vs local bonobo-conf properties

[Dietmar Maurer <dietmar ximian com>]

Jeroen Zwartepoorte wrote:

> Hi,
>
> Global properties for a Bonobo component are pretty simple: use a
> "config:/component" PropertyBag. When someone changes something, all the
> instances of that component will get notified and update themselves.
>
> For local properties (properties that only take effect in 1 application)
> it is not so clear. You can't have a "config:/component/local"
> PropertyBag since changes to that PropertyBag will still be propagated
> to the entire system. On the other hand, creating a PropertyBag in
> memory during initialization is also not good since that doesn't allow
> you to save the settings.
>
> What is the correct approach here?

Why do you need such local configuration?

>
>
> Should we use a "config:/application/component" PropertyBag and let the
> application update the Bonobo component? Are there any examples/design
> documents about this?
>