Review Request 127979: [WIP] Implement color scheme selection from these installed in the system using KColorSchemeManager
Alexander Zhigalin
alexander at zhigalin.tk
Fri May 27 20:47:41 UTC 2016
> On Май 21, 2016, 7:31 п.п., Aleix Pol Gonzalez wrote:
> > shell/thememanager.h, line 37
> > <https://git.reviewboard.kde.org/r/127979/diff/1/?file=465304#file465304line37>
> >
> > Maybe it should be called `ColorSchemeManager`? I'd also change other `Theme` uses for `ColorScheme`.
Why?
> On Май 21, 2016, 7:31 п.п., Aleix Pol Gonzalez wrote:
> > shell/thememanager.cpp, line 55
> > <https://git.reviewboard.kde.org/r/127979/diff/1/?file=465305#file465305line55>
> >
> > Why isn't it a `Q_GLOBAL_STATIC(ThemeManager, object)`? Also usually static members have a `s_` prefix. I suggest: `s_themeManager`.
Digikam heritage, will look there when the thing will get working.
> On Май 21, 2016, 7:31 п.п., Aleix Pol Gonzalez wrote:
> > shell/thememanager.cpp, line 137
> > <https://git.reviewboard.kde.org/r/127979/diff/1/?file=465305#file465305line137>
> >
> > The only reason we are passing the QApplication is so that `d->manager` has a parent?
> >
> > I'd rather manage it within ThemeManager by using QScopedPointer or such. `d->manager` can be initialized the first time it's used. Or `this`.
>The only reason we are passing the QApplication is so that d->manager has a parent?
I think KColorSchemeManager wants the main application object as his parent.
>I'd rather manage it within ThemeManager by using QScopedPointer or such. d->manager can be initialized the first time it's used. Or this.
Can you please explain?
> On Май 21, 2016, 7:31 п.п., Aleix Pol Gonzalez wrote:
> > shell/thememanager.cpp, line 155
> > <https://git.reviewboard.kde.org/r/127979/diff/1/?file=465305#file465305line155>
> >
> > Again QScopedPointer.
Again, explain please.
- Alexander
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/127979/#review95679
-----------------------------------------------------------
On Май 20, 2016, 7:44 п.п., Alexander Zhigalin wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/127979/
> -----------------------------------------------------------
>
> (Updated Май 20, 2016, 7:44 п.п.)
>
>
> Review request for KDevelop and Kevin Funk.
>
>
> Bugs: 279592
> http://bugs.kde.org/show_bug.cgi?id=279592
>
>
> Repository: kdevplatform
>
>
> Description
> -------
>
> [WIP] Implement color scheme selection from these installed in the system using KColorSchemeManager
>
>
> Diffs
> -----
>
> CMakeLists.txt ec521ab8f5dcdd1cc175809f56169259e241ea34
> shell/CMakeLists.txt 752c435b81d60e6bf9d438a0367662a8be346a33
> shell/mainwindow.h 8340064ee7e1a3b95695b430270cc848ac69eeac
> shell/mainwindow.cpp cf1b15d99365a1274f49bbde18bf3c5c17ba7ccb
> shell/mainwindow_p.cpp 70b56db7bed09aeea7a0e57307fb870f65471574
> shell/thememanager.h PRE-CREATION
> shell/thememanager.cpp PRE-CREATION
>
> Diff: https://git.reviewboard.kde.org/r/127979/diff/
>
>
> Testing
> -------
>
> Not tested yet
>
>
> Thanks,
>
> Alexander Zhigalin
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20160527/01ec356d/attachment-0001.html>
More information about the KDevelop-devel
mailing list