On Thursday 04 July 2013 01:28:16 Aaron J. Seigo wrote:
> On Tuesday, June 25, 2013 10:10:03 Aurélien Gâteau wrote:
> > > Why would the code be specific to kiosk? - You asked for an example, not
> > > justification.
> >
> > I asked for an example, you provided one about kiosk, I answer how your
>
On Tuesday, June 25, 2013 10:10:03 Aurélien Gâteau wrote:
> > Why would the code be specific to kiosk? - You asked for an example, not
> > justification.
>
> I asked for an example, you provided one about kiosk, I answer how your
> kiosk example is actually painful.
As someone who has done deploy
On Tuesday 25 June 2013 14:17:16 Thomas Lübking wrote:
> On Dienstag, 25. Juni 2013 10:10:03 CEST, Aurélien Gâteau wrote:
> > [Continuing the discussion started on
> > https://git.reviewboard.kde.org/r/71/ ]
>
> -
>
> > kdeglobals in mind. As such, I think this code should opt-in to
>
On Dienstag, 25. Juni 2013 10:10:03 CEST, Aurélien Gâteau wrote:
[Continuing the discussion started on
https://git.reviewboard.kde.org/r/71/ ]
-
kdeglobals in mind. As such, I think this code should opt-in to
inherit from
kdeglobals, instead of expecting all code reading configura
On Tuesday 25 June 2013 10:10:03 Aurélien Gâteau wrote:
> > Eventually the default actually should have been CascadeOnly (because
> > IncludeGlobals seems mostly interesting to libs only).
>
> I agree, especially because I assume all the code which benefits from
> inheriting from kdeglobals has be
[Continuing the discussion started on
https://git.reviewboard.kde.org/r/71/ ]
> > > Aurélien Gâteau wrote:
> > >
> > > > I see the point of having cross-app configuration files, I assume
> > > > classes
> > > > from kdelibs for example can use it to store settings. What I don't
> > > > unders
