2013/11/25 Joel Madigan <notifications@github.com>

> In src/app/settings/settings.h:
>
> > @@ -62,6 +67,9 @@
> >      virtual IToolSettings* getToolSettings(tools::Tool* tool) = 0;
> >
> >      virtual IColorSwatchesStore* getColorSwatchesStore() = 0;
> > +
> > +    // Signals
> > +    Signal1<void, const app::Color&> ChangeMoveTransparentColor;
>
> I'll go ahead and make the SettingsObserver and stubs for the App signals
> to be moved later. I wont be able to write it until later tonight so I'll
> have all day to think about it. And actually I think the specialized
> settings classes (pen, selection, etc.) will have the observer interfaces,
> so IPenSettingsObserver, etc and a IGlobalSettings for stuff that doesn't
> fit in the categorized settings.
>

Excellent, remember to use base::Observable (to create observable classes,
e.g. observable ISettings) and base::Observers (a list of observers that
you can use in UISettingsImpl)


> I just have to get my brain out of python mode and all the clever dynamic
> programming tricks for doing this kind of thing :-)
>

:) if you come from Python world, I think you will find quite interesting
to specify interfaces/requirements/constraints in static terms (the
compiler is a really useful tools).

Happy coding and let me know if you have any trouble.