Re: Information regarding upcoming Gitlab Migration

[Olivier Churlaud]

Le 27 avril 2020 22:33:12 GMT+02:00, Ben Cooksley  a écrit :
>On Tue, Apr 28, 2020 at 8:31 AM Albert Astals Cid 
>wrote:
>>
>> El dilluns, 27 d’abril de 2020, a les 13:19:07 CEST, Ben Cooksley va
>escriure:
>> > On Mon, Apr 27, 2020 at 11:12 PM Olivier Churlaud
> wrote:
>> > >
>> > > Hi,
>> > >
>> > > Le lundi 27 avril 2020, 12:38:42 CEST Aleix Pol a écrit :
>> > > > On Mon, Apr 27, 2020 at 3:41 AM Bhushan Shah 
>wrote:
>> > > > >
>> > > > > [Please keep sysad...@kde.org list or bs...@kde.org in the CC
>for
>> > > > > replies]
>> > > > >
>> > > > > Hello Community members,
>> > > > >
>> > > > > In view of upcoming Gitlab migration, we sysadmin team wants
>to share
>> > > > > the recommended structuring for the repositories on Gitlab.
>> > > > >
>> > > > > We had multiple options,
>> > > > >
>> > > > > - Flat structure: In this option we would have everything
>under one
>> > > > > single namespace/group: https://invent.kde.org/kde/knetwalk
>> > > > > - Subgroups under top-level group: In this option we would
>have a groups
>> > > > > under KDE namespace:
>https://invent.kde.org/kde/games/knetwalk
>> > > > > - Groups at top level: In this option we would establish a
>series of
>> > > > > groups at the top level, e.g. 
>https://invent.kde.org/games/knetwalk
>> > > > >
>> > >
>> > > Thank you for having options and talking to us before
>implementing it.
>> > >
>> > > > > We have discussed this with small but representative group of
>> > > > > contributors or maintainers, and based on their suggestions,
>we
>> > > > > recommend that we go with option 3. Having sub-groups at top
>level will
>> > > > > allow us to,
>> > > > >
>> > > > > - Provides good visibility on all reviews, tasks and other
>items within
>> > > > > the groups/modules we define
>> > > > > - Provides improvements to discoverability of projects
>> > > > > - Makes it possible for groups of projects to establish a
>group level
>> > > > > task board should it fit their needs (for tracking a release
>for
>> > > > > instance)
>> > > > > - Makes the most semantic sense, as the ‘KDE’ top level group
>suggested
>> > > > > in option 2 is duplicative considering the Gitlab instance is
>under
>> > > > > kde.org.
>> > > > > - The discoverability of projects is maximised, as there is
>no need to
>> > > > > open the top level ‘KDE’ group before going into the
>subgroup.
>> > > > >
>> > > > > I've worked on draft "move" of the current set of the
>repositories in
>> > > > > their respective subgroups at the repo-metadata project's
>branch [1].
>> > > > > You can browse the directory structure to get idea of how
>final
>> > > > > structure on Gitlab would look like.
>> > > > >
>> > > > > If we don't have any objections we would like to implement
>this next
>> > > > > week and move projects to https://invent.kde.org.
>> > > > >
>> > > > > Thanks!
>> > > > > Bhushan for sysadmin team
>> > > > >
>> > > > > [1]
>https://cgit.kde.org/sysadmin/repo-metadata.git/tree/projects-invent?h=bshah/invent
>> > > >
>> > > > Does this mean that to clone it we'll have to go "git clone
>> > > > kde:games/knetwalk" or something along the lines?
>> > > >
>> > > > If that's the case I'd much prefer if we didn't do this, at the
>moment
>> > > > it's already uncomfortable for me to remember the URL for some
>of the
>> > > > repos (e.g. is it sysadmin/ or not?), this will only increase
>the
>> > > > problem and I personally don't see the advantage.
>> > > >
>> > > > e.g. Is okular graphics or office? Is gwenview plasma or
>graphics? Is
>> > > > krita graphics or its own thing?
>> > > >
>> > > > I really prefer when I don't have to guess this kind of things
>when
>> > > > fetching a repository.
>> > > 

Re: Information regarding upcoming Gitlab Migration

[Olivier Churlaud]

Le lundi 27 avril 2020, 13:19:07 CEST Ben Cooksley a écrit :
> On Mon, Apr 27, 2020 at 11:12 PM Olivier Churlaud  
> wrote:
> >
> > Hi,
> >
> > Le lundi 27 avril 2020, 12:38:42 CEST Aleix Pol a écrit :
> > > On Mon, Apr 27, 2020 at 3:41 AM Bhushan Shah  wrote:
> > > >
> > > > [Please keep sysad...@kde.org list or bs...@kde.org in the CC for
> > > > replies]
> > > >
> > > > Hello Community members,
> > > >
> > > > In view of upcoming Gitlab migration, we sysadmin team wants to share
> > > > the recommended structuring for the repositories on Gitlab.
> > > >
> > > > We had multiple options,
> > > >
> > > > - Flat structure: In this option we would have everything under one
> > > > single namespace/group: https://invent.kde.org/kde/knetwalk
> > > > - Subgroups under top-level group: In this option we would have a groups
> > > > under KDE namespace: https://invent.kde.org/kde/games/knetwalk
> > > > - Groups at top level: In this option we would establish a series of
> > > > groups at the top level, e.g.  https://invent.kde.org/games/knetwalk
> > > >
> >
> > Thank you for having options and talking to us before implementing it.
> >
> > > > We have discussed this with small but representative group of
> > > > contributors or maintainers, and based on their suggestions, we
> > > > recommend that we go with option 3. Having sub-groups at top level will
> > > > allow us to,
> > > >
> > > > - Provides good visibility on all reviews, tasks and other items within
> > > > the groups/modules we define
> > > > - Provides improvements to discoverability of projects
> > > > - Makes it possible for groups of projects to establish a group level
> > > > task board should it fit their needs (for tracking a release for
> > > > instance)
> > > > - Makes the most semantic sense, as the ‘KDE’ top level group suggested
> > > > in option 2 is duplicative considering the Gitlab instance is under
> > > > kde.org.
> > > > - The discoverability of projects is maximised, as there is no need to
> > > > open the top level ‘KDE’ group before going into the subgroup.
> > > >
> > > > I've worked on draft "move" of the current set of the repositories in
> > > > their respective subgroups at the repo-metadata project's branch [1].
> > > > You can browse the directory structure to get idea of how final
> > > > structure on Gitlab would look like.
> > > >
> > > > If we don't have any objections we would like to implement this next
> > > > week and move projects to https://invent.kde.org.
> > > >
> > > > Thanks!
> > > > Bhushan for sysadmin team
> > > >
> > > > [1] 
> > > > https://cgit.kde.org/sysadmin/repo-metadata.git/tree/projects-invent?h=bshah/invent
> > >
> > > Does this mean that to clone it we'll have to go "git clone
> > > kde:games/knetwalk" or something along the lines?
> > >
> > > If that's the case I'd much prefer if we didn't do this, at the moment
> > > it's already uncomfortable for me to remember the URL for some of the
> > > repos (e.g. is it sysadmin/ or not?), this will only increase the
> > > problem and I personally don't see the advantage.
> > >
> > > e.g. Is okular graphics or office? Is gwenview plasma or graphics? Is
> > > krita graphics or its own thing?
> > >
> > > I really prefer when I don't have to guess this kind of things when
> > > fetching a repository.
> > >
> >
> > I 100% agree with Aleix and I think it would also be detrimental for 
> > discoverability, exactly for the examples Aleix just gave.
> >
> > We came back from this subgroups ideas some times ago : wiki pages were 
> > hard to find because hidden under layers of groups. The same was true for 
> > api documentations. Now everything is flat and I think it's easier to find.
> >
> > Another bad message could also be sent by this: instead of exposing Konsole 
> > or Ark as two applications under the KDE umbrella, it would look like Utils 
> > for KDE, bringing back the KDE Desktop idea (where every application is 
> > already store in a submenu).
> >
> > As someone wrote later, if I'm looking for a given application, there is 
> > always the search function...
> 
> That requires tha

Re: Information regarding upcoming Gitlab Migration

[Olivier Churlaud]

Hi,

Le lundi 27 avril 2020, 12:38:42 CEST Aleix Pol a écrit :
> On Mon, Apr 27, 2020 at 3:41 AM Bhushan Shah  wrote:
> >
> > [Please keep sysad...@kde.org list or bs...@kde.org in the CC for
> > replies]
> >
> > Hello Community members,
> >
> > In view of upcoming Gitlab migration, we sysadmin team wants to share
> > the recommended structuring for the repositories on Gitlab.
> >
> > We had multiple options,
> >
> > - Flat structure: In this option we would have everything under one
> > single namespace/group: https://invent.kde.org/kde/knetwalk
> > - Subgroups under top-level group: In this option we would have a groups
> > under KDE namespace: https://invent.kde.org/kde/games/knetwalk
> > - Groups at top level: In this option we would establish a series of
> > groups at the top level, e.g.  https://invent.kde.org/games/knetwalk
> >

Thank you for having options and talking to us before implementing it.

> > We have discussed this with small but representative group of
> > contributors or maintainers, and based on their suggestions, we
> > recommend that we go with option 3. Having sub-groups at top level will
> > allow us to,
> >
> > - Provides good visibility on all reviews, tasks and other items within
> > the groups/modules we define
> > - Provides improvements to discoverability of projects
> > - Makes it possible for groups of projects to establish a group level
> > task board should it fit their needs (for tracking a release for
> > instance)
> > - Makes the most semantic sense, as the ‘KDE’ top level group suggested
> > in option 2 is duplicative considering the Gitlab instance is under
> > kde.org.
> > - The discoverability of projects is maximised, as there is no need to
> > open the top level ‘KDE’ group before going into the subgroup.
> >
> > I've worked on draft "move" of the current set of the repositories in
> > their respective subgroups at the repo-metadata project's branch [1].
> > You can browse the directory structure to get idea of how final
> > structure on Gitlab would look like.
> >
> > If we don't have any objections we would like to implement this next
> > week and move projects to https://invent.kde.org.
> >
> > Thanks!
> > Bhushan for sysadmin team
> >
> > [1] 
> > https://cgit.kde.org/sysadmin/repo-metadata.git/tree/projects-invent?h=bshah/invent
>
> Does this mean that to clone it we'll have to go "git clone
> kde:games/knetwalk" or something along the lines?
>
> If that's the case I'd much prefer if we didn't do this, at the moment
> it's already uncomfortable for me to remember the URL for some of the
> repos (e.g. is it sysadmin/ or not?), this will only increase the
> problem and I personally don't see the advantage.
>
> e.g. Is okular graphics or office? Is gwenview plasma or graphics? Is
> krita graphics or its own thing?
>
> I really prefer when I don't have to guess this kind of things when
> fetching a repository.
>

I 100% agree with Aleix and I think it would also be detrimental for 
discoverability, exactly for the examples Aleix just gave.

We came back from this subgroups ideas some times ago : wiki pages were hard to 
find because hidden under layers of groups. The same was true for api 
documentations. Now everything is flat and I think it's easier to find.

Another bad message could also be sent by this: instead of exposing Konsole or 
Ark as two applications under the KDE umbrella, it would look like Utils for 
KDE, bringing back the KDE Desktop idea (where every application is already 
store in a submenu).

As someone wrote later, if I'm looking for a given application, there is always 
the search function...
  
Best regards,
Olivier
> Aleix

D17076: Avoid indeterminism in kcolorschemeeditor

[Olivier Churlaud]

This revision was automatically updated to reflect the committed changes.
Closed by commit R119:c9cf4883da4e: Avoid indeterminism in 
kcolorschemeeditors compilation (authored by ochurlaud).

REPOSITORY
  R119 Plasma Desktop

CHANGES SINCE LAST UPDATE
  https://phabricator.kde.org/D17076?vs=45954=46080

REVISION DETAIL
  https://phabricator.kde.org/D17076

AFFECTED FILES
  kcms/colors/CMakeLists.txt

To: bmwiedemann, rwooninck, ochurlaud
Cc: plasma-devel, ragreen, Pitel, ZrenBot, lesliezhai, ali-mohamed, 
jensreuterberg, abetts, sebas, apol, mart

D17076: Avoid indeterminism in kcolorschemeeditor

[Olivier Churlaud]

ochurlaud accepted this revision.
ochurlaud added a comment.
This revision is now accepted and ready to land.


  The root cause is that we build twice the same elements instead of having one 
share lib used on the two contexts.
  
  I guess this is more involved to do the proper fix, so at first yours can be 
OK... Push it!

REPOSITORY
  R119 Plasma Desktop

BRANCH
  master

REVISION DETAIL
  https://phabricator.kde.org/D17076

To: bmwiedemann, rwooninck, ochurlaud
Cc: plasma-devel, ragreen, Pitel, ZrenBot, lesliezhai, ali-mohamed, 
jensreuterberg, abetts, sebas, apol, mart

D17076: Avoid indeterminism in kcolorschemeeditor

[Olivier Churlaud]

ochurlaud added a comment.


  Well it's not really a dependency, is it? They only use the same sources to 
build up two different views of the same widget. This patch is hacky as the 
original cmakefile... I understand the need but can't the patch fix the root 
cause instead?

REPOSITORY
  R119 Plasma Desktop

REVISION DETAIL
  https://phabricator.kde.org/D17076

To: bmwiedemann, rwooninck, ochurlaud
Cc: plasma-devel, ragreen, Pitel, ZrenBot, lesliezhai, ali-mohamed, 
jensreuterberg, abetts, sebas, apol, mart

Re: Closing old Plasma 4 bugs

[Olivier Churlaud]

Hello,

Just to remind you that companies using KDE/Plasma on RHEL7 are still using 
plasma 4. 
I don't know if it has an impact but in case I wanted to point it out.

Cheers,
Olivier

Le samedi 26 mai 2018, 05:09:06 CEST Nate Graham a écrit :
> Kubuntu 18.04  has now now been out for a month, so if there are no 
> further objections, I'll begin preparations for this Plasma 4 mass bug 
> close.
> 
> Nate
> 
> 
> 
> On 02/14/2018 10:16 AM, Christoph Feck wrote:
> > On 10.02.2018 21:24, Nate Graham wrote:
> >> Hello folks,
> >> We have more than 2,500 Plasma 4 bugzilla tickets that we don't intend
> >> to look at or triage. We've already prevented new tickets from being
> >> filed, but it doesn't do anyone any good to just have the old ones
> >> sitting there. My sense is that most of the relevant bugs and wishlist
> >> items are already represented in the plasmashell product, so what do you
> >> think about doing a mass-close?
> >>
> >> I was thinking of closing them all with one of the following two
> >> messages (top one for bugs, bottom one for wishlist items). What do you
> >> think?
> >>
> >> Nate
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> For bugs:
> >> =
> >>
> >> Hello!
> >>
> >> This bug was filed for KDE Plasma 4, which reached end-of-support status
> >> in October 2015. Developers have not been triaging Plasma 4 bugs since
> >> that time. Happily, because KDE Plasma 5's desktop shell was been almost
> >> completely rewritten for better performance and usability, it is likely
> >> that this bug has already been resolved in Plasma 5. Additionally, bug
> >> triaging resources are extremely limited; if you would like to get
> >> involved in this effort, please see
> >> https://community.kde.org/Get_Involved#Bug_Triaging
> >>
> >> Accordingly, and we hope you understand why we must close this bug. If
> >> the issue described  here is still present in KDE Plasma 5.12 or later,
> >> please feel free to open a new ticket in the "plasmashell" product after
> >> reading https://community.kde.org/Get_Involved/Bug_Reporting
> >>
> >> Thanks for your understanding!
> >>
> >> Nate Graham
> >>
> >>
> >>
> >>
> >>
> >>
> >> For wishlist items:
> >> ===
> >>
> >> Hello!
> >>
> >> This feature request was filed for KDE Plasma 4, which reached
> >> end-of-support status in October 2015. Developers have not been triaging
> >> Plasma 4 requests since that time. Happily, because KDE Plasma 5's
> >> desktop shell was been almost completely rewritten, it is likely that
> >> this feature request has already been implemented in Plasma 5, or is no
> >> longer applicable. Additionally, bug triaging resources are extremely
> >> limited; if you would like to get involved in this effort, please see
> >> https://community.kde.org/Get_Involved#Bug_Triaging
> >>
> >> Accordingly, and we hope you understand why we must close this feature
> >> request. If the requested feature is still not implemented in KDE Plasma
> >> 5.12 or later, please feel free to open a new ticket in the
> >> "plasmashell" product after reading
> >> https://community.kde.org/Get_Involved/Bug_Reporting
> >>
> >> Thanks for your understanding!
> >>
> >> Nate Graham
> >>
> > 
> > Hi Nate,
> > 
> > had that on my TODO list, but happy to see you taking over for this task.
> > 
> > I suggest to wait until Ubuntu 18.04 LTS is released, ideally a month 
> > longer to give people with LTS requirements time to update it.
> 
> 
> 

Re: Splash screen translation

[Olivier Churlaud]

Thx for your answer. I was expecting something like this : let's see what the 
French team says :) 

Cheers 
Olivier

Le 3 août 2017 22:29:57 GMT+02:00, Marco Martin <notm...@gmail.com> a écrit :
>On Thursday 03 August 2017 21:00:26 Olivier Churlaud wrote:
>> I've seen on my French version of Plasma that the string "Plasma,
>made by
>> KDE" on the loading screen (after entering your credentials) was
>translated
>> in French. I think it's a mistake to translate this, because it just
>> doesn't sound as cool as the english one.
>> 
>> Maybe it's just french, or my feeling about it, but I think the "made
>by"
>> works very well in English.
>> 
>> What do you think?
>> Please add me in copy of your answer, as I'm not anymore in the
>mailing
>> list.
>
>iirc my first intention was to make it a non translatable string, but 
>understanably several translator teams didn't like it. so probably this
>
>decision should be done language by language with decision by the
>single 
>teams?
>
>-- 
>Marco Martin

-- 
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma 
brièveté.

Splash screen translation

[Olivier Churlaud]

[English below, for plasma people]

Bonjour,

J'ai vu que récemment la string "Plasma, made by KDE" a été traduit en 
"Plasma, fait par KDE". 

Mon avis n'est peut-être pas partagé, mais je trouve que ça en jette moins.

Revenir vers du made by KDE serait préférable, non?

Qu'en pensez vous?

Si vous pouviez me mettre en copie de la réponse, je ne suis pas dans la 
mailing-list.

Olivier

---
Hi!

I've seen on my French version of Plasma that the string "Plasma, made by KDE" 
on the loading screen (after entering your credentials) was translated in 
French. I think it's a mistake to translate this, because it just doesn't 
sound as cool as the english one. 

Maybe it's just french, or my feeling about it, but I think the "made by" 
works very well in English. 

What do you think?
Please add me in copy of your answer, as I'm not anymore in the mailing list.

Cheers,
Olivier

Re: Review Request 129902: fix some bugs in kcm_colors

[Olivier Churlaud]

> On Jan. 29, 2017, 2:58 p.m., Olivier Churlaud wrote:
> > Ship It!

I didn't test it but everything seems reasonable


- Olivier


---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/129902/#review102309
---


On Jan. 29, 2017, 2:39 p.m., Martin Koller wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/129902/
> ---
> 
> (Updated Jan. 29, 2017, 2:39 p.m.)
> 
> 
> Review request for Plasma, Marco Martin and Olivier Churlaud.
> 
> 
> Bugs: 372309 and 372407
> https://bugs.kde.org/show_bug.cgi?id=372309
> https://bugs.kde.org/show_bug.cgi?id=372407
> 
> 
> Repository: plasma-desktop
> 
> 
> Description
> ---
> 
> the new kcm_colors has some bugs which this patch addresses:
> 
> 1) memory leak when opening SchemeEditorDialog (is never deleted)
> 2) The color preview widget can be reduced in height to nearly zero, which 
> makes no sense
> 3) The scheme editor does not reflect any color change in the preview widget
> 4) triple-redundant widgets in the scmeditorcolors.ui file
> 5) user unfriendly current tab when opening the SchemeEditorDialog (I want to 
> change a color, so the color tab shall be active)
> 6) Unneeded and incorrect tab index enum (enum values were not corresponding 
> to the index the tab was inserted)
> 7) The SchemeEditorDialog did not just only expand the color table when 
> enlarging the dialogs height
> 
> 
> Diffs
> -
> 
>   kcms/colors/colorscm.cpp de5b04df 
>   kcms/colors/preview.ui 0eef1ca8 
>   kcms/colors/scmeditorcolors.cpp a975aea9 
>   kcms/colors/scmeditorcolors.ui 87a72445 
>   kcms/colors/scmeditordialog.h a49052eb 
>   kcms/colors/scmeditordialog.cpp 83ab53da 
> 
> Diff: https://git.reviewboard.kde.org/r/129902/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Martin Koller
> 
>

Re: Review Request 129902: fix some bugs in kcm_colors

[Olivier Churlaud]

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/129902/#review102309
---


Ship it!




Ship It!

- Olivier Churlaud


On Jan. 29, 2017, 2:39 p.m., Martin Koller wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/129902/
> ---
> 
> (Updated Jan. 29, 2017, 2:39 p.m.)
> 
> 
> Review request for Plasma, Marco Martin and Olivier Churlaud.
> 
> 
> Bugs: 372309 and 372407
> https://bugs.kde.org/show_bug.cgi?id=372309
> https://bugs.kde.org/show_bug.cgi?id=372407
> 
> 
> Repository: plasma-desktop
> 
> 
> Description
> ---
> 
> the new kcm_colors has some bugs which this patch addresses:
> 
> 1) memory leak when opening SchemeEditorDialog (is never deleted)
> 2) The color preview widget can be reduced in height to nearly zero, which 
> makes no sense
> 3) The scheme editor does not reflect any color change in the preview widget
> 4) triple-redundant widgets in the scmeditorcolors.ui file
> 5) user unfriendly current tab when opening the SchemeEditorDialog (I want to 
> change a color, so the color tab shall be active)
> 6) Unneeded and incorrect tab index enum (enum values were not corresponding 
> to the index the tab was inserted)
> 7) The SchemeEditorDialog did not just only expand the color table when 
> enlarging the dialogs height
> 
> 
> Diffs
> -
> 
>   kcms/colors/colorscm.cpp de5b04df 
>   kcms/colors/preview.ui 0eef1ca8 
>   kcms/colors/scmeditorcolors.cpp a975aea9 
>   kcms/colors/scmeditorcolors.ui 87a72445 
>   kcms/colors/scmeditordialog.h a49052eb 
>   kcms/colors/scmeditordialog.cpp 83ab53da 
> 
> Diff: https://git.reviewboard.kde.org/r/129902/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Martin Koller
> 
>

[Differential] [Abandoned] D3048: [Colors KCM] Default scheme is now installed as a file

[ochurlaud (Olivier Churlaud)]

ochurlaud abandoned this revision.

REPOSITORY
  rPLASMADESKTOP Plasma Desktop

REVISION DETAIL
  https://phabricator.kde.org/D3048

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, #plasma, broulik, mart
Cc: plasma-devel, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas

[Differential] [Commented On] D3048: [Colors KCM] Default scheme is now installed as a file

[ochurlaud (Olivier Churlaud)]

ochurlaud added a comment.


  In https://phabricator.kde.org/D3048#56488, @mart wrote:
  
  > i am in favor  of this chane, but i think the real reson of the breakage 
should be investigated as well, uf there may be problems in kconfigwidget itself
  
  
  Then I need help :)

INLINE COMMENTS

> mart wrote in colorscm.cpp:118
> is this name localized?

No, it's not. But next line should be:

new QListWidgetItem(icon, i18nc("Default color scheme", "Default"));

REPOSITORY
  rPLASMADESKTOP Plasma Desktop

REVISION DETAIL
  https://phabricator.kde.org/D3048

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, #plasma, broulik, mart
Cc: plasma-devel, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas

[Differential] [Commented On] D3048: [Colors KCM] Default scheme is now installed as a file

[ochurlaud (Olivier Churlaud)]

ochurlaud added a comment.


  One draw back of this way is that if `Default.colors` is erased or not found, 
there is no "Default", and in case no `*.colors` are found, the kcm will be 
empty...

REPOSITORY
  rPLASMADESKTOP Plasma Desktop

REVISION DETAIL
  https://phabricator.kde.org/D3048

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, #plasma, mart, broulik
Cc: plasma-devel, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas

[Differential] [Updated] D3048: [Colors KCM] Default scheme is now installed as a file

[ochurlaud (Olivier Churlaud)]

ochurlaud added reviewers: Plasma, mart, broulik.

REPOSITORY
  rPLASMADESKTOP Plasma Desktop

REVISION DETAIL
  https://phabricator.kde.org/D3048

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, #plasma, mart, broulik
Cc: plasma-devel, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas

[Differential] [Request, 184 lines] D3048: [Colors KCM] Default scheme is now installed as a file

[ochurlaud (Olivier Churlaud)]

ochurlaud created this revision.
Restricted Application added a project: Plasma.
Restricted Application added a subscriber: plasma-devel.

REVISION SUMMARY
  The default values are not anymore taken from the hardcoded ones in 
kconfigwidget.
  
  BUG: 370305

REPOSITORY
  rPLASMADESKTOP Plasma Desktop

BRANCH
  master

REVISION DETAIL
  https://phabricator.kde.org/D3048

AFFECTED FILES
  kcms/colors/colorscm.cpp
  kcms/colors/schemes/Default.colors
  kcms/colors/scmeditordialog.cpp

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud
Cc: plasma-devel, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas

Re: A Plasma Vision draft

[Olivier Churlaud]

Hi,

Le mardi 27 septembre 2016, 18:24:36 CEST Jens Reuterberg a écrit :
> This is actually fairly tricky because what is needed is a metric to work
> towards: sayiing "fast and stable" is not very exact.
> 
> But you raise fair points - how do we ensure that it doesn't exclude anyone?
> To me a vision is a statement of intent, but not a boundary beyond
> practical choices. "Should we pick Y or X, we can only pick one?" Should be
> something that you can answer with it. In this case "Does one of them help
> professional users? Pick that!".
> Not "I want to do Y!" and then someone going "No you can't because X and Z
> would be more for professional users".
> 
> One is a boundary, the other is a vision I feel. We can't make a few
> sentences work as a complete boundary - that would take a way longer
> document. This is more like the header for a longer text, a statement of
> intent or coming things but it can't be something that defines complete
> usage.
> 
> Still, you bring up good points - but how can we realize them as a vision?
> How can "fast/stable" function except as something that would work for
> everyone, all DE's etc?
> 

My understanding of the vision is "what do we want". So if you say "Plasma 
targets professional users", it means "we do not care at all about the 
others".

I might be wrong, but it seems to me that what you want to say to the world is 
"we have the most reliable, proof of that: our products are used by 
professionals". So when reading this, I really think that the vision is about 
reliability, efficiency and good experience. Your target is just a way to 
access 
to this quality, so it's more part of your strategy.

Now I must be clear: in my mind the vision is shown everywhere when you speak 
about the product. To me, it should be used as a marketing weight to say "this 
is who/what we are". If you have that in mind, you don't want to have in big 
on the front page of your website and on your stickers "for professional 
users", because people will exclude themselves. I'm more afraid of this 
(people excluding themselves) than of people excluding others.

However, if you don't see the vision as what I just presented, it means that 
we don't speak of the exact same thing, and in this case I don't have anything 
against the current formulation.

Cheers
Olivier

> (also added plasma-devel since the thread is made for plasma-devel the reply
> got weird though halfway through)
> 
> /Jens
> 
> > IMO, the first step is to get rock-solid stable, performant (whatever you
> > call that in English) and productive desktop, so that everyone says: "I
> > want to use that". This is, to me, a nice vision.
> > 
> > 
> > Also, most of my friends (often using Ubuntu+Unity) told me "KDE
> > (understand Plasma) is the most good looking desktop out there those
> > days". Don't look boring, please (Office=boring). Also when I think
> > office, I think excel + word + firefox. You don't need a nice desktop for
> > that, anything would  be ok. Geeks and private people have more needs.
> > 
> > Disclaimer: I might have had one beer to many, and I mostly speak with my
> > kind of user case in mind, and try to extrapolate. I'm not always using
> > Plasma at work, but I think it's the best at home, and as a geek as well.
> > 
> > > If on the other hand this is a real worry, and an issue then the
> > > discussion
> > > shouldn't be what the vision statement should say but if it should say
> > > something at all. Which is not something negative but an actual option
> > > :)
> > 
> > I agree with that, but I don't agree that my point of view doesn't say
> > anything: see above.
> > 
> > Cheers
> > Olivier
> > 
> > > On 26 September 2016 18:33:00 CEST, Olivier Churlaud
> > > <oliv...@churlaud.com>
> > 
> > wrote:
> > > >Le lundi 26 septembre 2016, 15:12:08 CEST Thomas Pfeiffer a écrit :
> > > >> On 26.09.2016 13:27, Olivier Churlaud wrote:
> > > >> > Hi,
> > > >> > Sorry if I come late, I wasn't aware of this thread...
> > > >> > 
> > > >> > Le lundi 26 septembre 2016, 12:56:25 CEST Jens Reuterberg a écrit :
> > > >> >> "Plasma is for people using a computing device in a professional
> > > >
> > > >context,
> > > >
> > > >> >> where productivity, performance and privacy are essential"
> > > >> > 
> > > >> > I find that the "is for people .." kind of restrict

[Differential] [Closed] D2846: Let kicker display executable items instead of empty buttons.

[ochurlaud (Olivier Churlaud)]

This revision was automatically updated to reflect the committed changes.
Closed by commit rPLASMADESKTOP5c966a42554f: Let kicker display executable 
items instead of empty buttons. (authored by ochurlaud).

REPOSITORY
  rPLASMADESKTOP Plasma Desktop

CHANGES SINCE LAST UPDATE
  https://phabricator.kde.org/D2846?vs=6909=6910

REVISION DETAIL
  https://phabricator.kde.org/D2846

AFFECTED FILES
  applets/kicker/plugin/recentusagemodel.cpp

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, hein, #plasma, davidedmundson, mart
Cc: mart, broulik, plasma-devel, lesliezhai, ali-mohamed, jensreuterberg, 
abetts, sebas

[Differential] [Updated, 5 lines] D2846: Let kicker display executable items instead of empty buttons.

[ochurlaud (Olivier Churlaud)]

ochurlaud updated this revision to Diff 6909.
ochurlaud added a comment.


  Use !contains() instead of index() == -1

REPOSITORY
  rPLASMADESKTOP Plasma Desktop

CHANGES SINCE LAST UPDATE
  https://phabricator.kde.org/D2846?vs=6906=6909

BRANCH
  master

REVISION DETAIL
  https://phabricator.kde.org/D2846

AFFECTED FILES
  applets/kicker/plugin/recentusagemodel.cpp

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, #plasma, hein
Cc: mart, broulik, plasma-devel, lesliezhai, ali-mohamed, jensreuterberg, 
abetts, sebas

[Differential] [Updated, 5 lines] D2846: Let kicker display executable items instead of empty buttons.

[ochurlaud (Olivier Churlaud)]

ochurlaud updated this revision to Diff 6906.
ochurlaud added a comment.


  Check for type, as asked by Sho

REPOSITORY
  rPLASMADESKTOP Plasma Desktop

CHANGES SINCE LAST UPDATE
  https://phabricator.kde.org/D2846?vs=6896=6906

BRANCH
  master

REVISION DETAIL
  https://phabricator.kde.org/D2846

AFFECTED FILES
  applets/kicker/plugin/recentusagemodel.cpp

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, hein, #plasma
Cc: mart, broulik, plasma-devel, lesliezhai, ali-mohamed, jensreuterberg, 
abetts, sebas

[Differential] [Changed Subscribers] D2846: Let kicker display executable items instead of empty buttons.

[ochurlaud (Olivier Churlaud)]

ochurlaud added a subscriber: broulik.
ochurlaud added a comment.


  @broulik remarked that a .desktop file should not define a `Exec=""` when it 
is `Type=Service`.
  
  If we want to respect this, we could split all kcm files in one part which 
defines the service, and one that defines the Exec line, as a 
`Type=Application` instead of this patch.
  
  It might be more work, but it would respect the rules. (and say that Krunner 
can only execute if it's of type Application).

REPOSITORY
  rPLASMADESKTOP Plasma Desktop

REVISION DETAIL
  https://phabricator.kde.org/D2846

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, hein, #plasma
Cc: broulik, plasma-devel, lesliezhai, ali-mohamed, jensreuterberg, abetts, 
sebas

[Differential] [Updated] D2846: Let kicker display executable items instead of empty buttons.

[ochurlaud (Olivier Churlaud)]

ochurlaud added a reviewer: Plasma.

REPOSITORY
  rPLASMADESKTOP Plasma Desktop

REVISION DETAIL
  https://phabricator.kde.org/D2846

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, hein, #plasma
Cc: plasma-devel, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas

[Differential] [Updated] D2846: Let kicker display executable items instead of empty buttons.

[ochurlaud (Olivier Churlaud)]

ochurlaud added a reviewer: hein.

REPOSITORY
  rPLASMADESKTOP Plasma Desktop

REVISION DETAIL
  https://phabricator.kde.org/D2846

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, hein
Cc: plasma-devel, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas

[Differential] [Request, 2 lines] D2846: Let kicker display executable items instead of empty buttons.

[ochurlaud (Olivier Churlaud)]

ochurlaud created this revision.
Restricted Application added a project: Plasma.
Restricted Application added a subscriber: plasma-devel.

REVISION SUMMARY
  This would partially fix https://bugs.kde.org/show_bug.cgi?id=369242
  Another patch is required not to show empty elements (in case `data()` 
returns `QVariant()`).

REPOSITORY
  rPLASMADESKTOP Plasma Desktop

BRANCH
  master

REVISION DETAIL
  https://phabricator.kde.org/D2846

AFFECTED FILES
  applets/kicker/plugin/recentusagemodel.cpp

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud
Cc: plasma-devel, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas

Re: Review Request 128965: Update color kcm docbook to 5.8

[Olivier Churlaud]

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/128965/#review99344
---


Ship it!




Ship It!

- Olivier Churlaud


On Sept. 21, 2016, 5:42 a.m., Burkhard Lück wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/128965/
> ---
> 
> (Updated Sept. 21, 2016, 5:42 a.m.)
> 
> 
> Review request for Documentation, Plasma and Olivier Churlaud.
> 
> 
> Repository: plasma-desktop
> 
> 
> Description
> ---
> 
> Adapt docbook to changed kcm in 5.8
> 
> 
> Diffs
> -
> 
>   doc/kcontrol/colors/index.docbook 75548b5 
> 
> Diff: https://git.reviewboard.kde.org/r/128965/diff/
> 
> 
> Testing
> ---
> 
> passes checkXML5
> 
> 
> Thanks,
> 
> Burkhard Lück
> 
>

[Differential] [Closed] D2631: Correct regression introduced during color kcm rewritting.

[ochurlaud (Olivier Churlaud)]

This revision was automatically updated to reflect the committed changes.
Closed by commit rPLASMADESKTOPb5fd8c353448: Colors KCM: Correct regression in 
previews introduced during rewritting (authored by ochurlaud).

CHANGED PRIOR TO COMMIT
  https://phabricator.kde.org/D2631?vs=6374=6375#toc

REPOSITORY
  rPLASMADESKTOP Plasma Desktop

CHANGES SINCE LAST UPDATE
  https://phabricator.kde.org/D2631?vs=6374=6375

REVISION DETAIL
  https://phabricator.kde.org/D2631

AFFECTED FILES
  kcms/colors/scmeditorcolors.cpp
  kcms/colors/scmeditorcolors.ui

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, andreask, pino, mart, #plasma, davidedmundson
Cc: andreask, plasma-devel, lesliezhai, ali-mohamed, jensreuterberg, abetts, 
sebas

[Differential] [Request, 124 lines] D2631: Correct regression introduced during color kcm rewritting.

[ochurlaud (Olivier Churlaud)]

ochurlaud created this revision.
ochurlaud added reviewers: andreask, Plasma, pino, mart.
ochurlaud added a subscriber: andreask.
ochurlaud set the repository for this revision to rPLASMADESKTOP Plasma Desktop.
Restricted Application added a project: Plasma.
Restricted Application added a subscriber: plasma-devel.

REVISION SUMMARY
  @andreask  told me that using the combo box in the color kcm was not doing 
anything. This corrects this.

TEST PLAN
  It compiles, and acts correctly

REPOSITORY
  rPLASMADESKTOP Plasma Desktop

REVISION DETAIL
  https://phabricator.kde.org/D2631

AFFECTED FILES
  kcms/colors/scmeditorcolors.cpp
  kcms/colors/scmeditorcolors.ui

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, andreask, #plasma, pino, mart
Cc: andreask, plasma-devel, lesliezhai, ali-mohamed, jensreuterberg, abetts, 
sebas

[systemsettings] [Bug 367619] icon kcm: remove advanced tab

[Olivier Churlaud via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367619

Olivier Churlaud <oliv...@churlaud.com> changed:

   What|Removed |Added

 CC||oliv...@churlaud.com
   Assignee|unassigned-b...@kde.org |plasma-devel@kde.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Differential] [Accepted] D2478: make kcolorschemeditor desktop entry spec compliant and refine it

[ochurlaud (Olivier Churlaud)]

ochurlaud accepted this revision.
ochurlaud added a comment.


  After discussion on IRC: the nodisplay bit will be removed in a next 
iteration when the app will have more context.

REPOSITORY
  rPLASMADESKTOP Plasma Desktop

BRANCH
  master

REVISION DETAIL
  https://phabricator.kde.org/D2478

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: sitter, bshah, ochurlaud
Cc: ochurlaud, bshah, plasma-devel, lesliezhai, ali-mohamed, jensreuterberg, 
abetts, sebas

[Differential] [Updated] D2478: make kcolorschemeditor desktop entry spec compliant and refine it

[ochurlaud (Olivier Churlaud)]

ochurlaud added a comment.


  In https://phabricator.kde.org/D2478#46347, @sitter wrote:
  
  > Pulling in @ochurlaud
  >
  > The NoDisplay remark from Bhushan got me wondering how the KCM actually 
starts the app. And it turns out that it doesn't.
  >
  >   SchemeEditorDialog* dialog = new SchemeEditorDialog(path, this);
  >   dialog->setModal(true);
  >   dialog->show();
  >   
  >
  > Which is now raising the question why kcolorschemeditor was made a 
standalone application to begin with seeing as it adds no value?
  
  
  I would not put that in no-display but rather so that it goes in the tools or 
something similar

REPOSITORY
  rPLASMADESKTOP Plasma Desktop

BRANCH
  master

REVISION DETAIL
  https://phabricator.kde.org/D2478

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: sitter, bshah, ochurlaud
Cc: ochurlaud, bshah, plasma-devel, lesliezhai, ali-mohamed, jensreuterberg, 
abetts, sebas

[Differential] [Closed] D2409: Update Color KCM

[ochurlaud (Olivier Churlaud)]

ochurlaud closed this revision.
ochurlaud added a comment.


  This was submitted  in commit 
https://phabricator.kde.org/rPLASMADESKTOPb9e2664cc7aa50aa9e6be8368f34390bc756b73a

REVISION DETAIL
  https://phabricator.kde.org/D2409

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, andreask, #vdg, mart, #plasma, bshah
Cc: whiting, colomar, andreaska, plasma-devel, lesliezhai, ali-mohamed, 
jensreuterberg, abetts, sebas

[Differential] [Updated] D2409: Update Color KCM

[ochurlaud (Olivier Churlaud)]

ochurlaud reclaimed this revision.

REVISION DETAIL
  https://phabricator.kde.org/D2409

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, andreask, #vdg, mart, #plasma, bshah
Cc: whiting, colomar, andreaska, plasma-devel, lesliezhai, ali-mohamed, 
jensreuterberg, abetts, sebas

[Differential] [Commandeered] D2409: Update Color KCM

[ochurlaud (Olivier Churlaud)]

ochurlaud commandeered this revision.
ochurlaud edited reviewers, added: bshah; removed: ochurlaud.

REVISION DETAIL
  https://phabricator.kde.org/D2409

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, andreask, #vdg, mart, #plasma, bshah
Cc: whiting, colomar, andreaska, plasma-devel, lesliezhai, ali-mohamed, 
jensreuterberg, abetts, sebas

[Differential] [Updated] D2409: Update Color KCM

[ochurlaud (Olivier Churlaud)]

ochurlaud updated the summary for this revision.

REVISION DETAIL
  https://phabricator.kde.org/D2409

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, #plasma, andreask, #vdg, mart
Cc: whiting, colomar, andreaska, plasma-devel, lesliezhai, ali-mohamed, 
jensreuterberg, abetts, sebas

[Differential] [Updated, 5,202 lines] D2409: Update Color KCM

[ochurlaud (Olivier Churlaud)]

ochurlaud removed rPLASMADESKTOP Plasma Desktop as the repository for this 
revision.
ochurlaud updated this revision to Diff 5843.
ochurlaud added a comment.


  Added a desktop file, finished the app (KAboutData, CommandLineParser,...)
  
  Ready to ship, I just wait for your remarks.

CHANGES SINCE LAST UPDATE
  https://phabricator.kde.org/D2409?vs=5837=5843

REVISION DETAIL
  https://phabricator.kde.org/D2409

AFFECTED FILES
  kcms/colors/CMakeLists.txt
  kcms/colors/colorscm.cpp
  kcms/colors/colorscm.h
  kcms/colors/colorsettings.ui
  kcms/colors/kcolorschemeeditor.cpp
  kcms/colors/kcolorschemeeditor.desktop
  kcms/colors/scmeditorcolors.cpp
  kcms/colors/scmeditorcolors.h
  kcms/colors/scmeditorcolors.ui
  kcms/colors/scmeditordialog.cpp
  kcms/colors/scmeditordialog.h
  kcms/colors/scmeditordialog.ui
  kcms/colors/scmeditoreffects.cpp
  kcms/colors/scmeditoreffects.h
  kcms/colors/scmeditoreffects.ui
  kcms/colors/scmeditoroptions.cpp
  kcms/colors/scmeditoroptions.h
  kcms/colors/scmeditoroptions.ui

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, #plasma, andreask, #vdg, mart
Cc: whiting, colomar, andreaska, plasma-devel, lesliezhai, ali-mohamed, 
jensreuterberg, abetts, sebas

[Differential] [Commented On] D2409: Update Color KCM

[ochurlaud (Olivier Churlaud)]

ochurlaud added a comment.


  In https://phabricator.kde.org/D2409#45058, @whiting wrote:
  
  > I like it. Nice work. I agree I would change Config Scheme to Edit Scheme.
  
  
  Done locally.
  
  The executable is now KColorSchemeEditor.
  
  If someone could tell me what the kcolorschemeditor.desktop should be as 
well? Then I'll update the review.

REPOSITORY
  rPLASMADESKTOP Plasma Desktop

REVISION DETAIL
  https://phabricator.kde.org/D2409

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, #plasma, andreask, #vdg, mart
Cc: whiting, colomar, andreaska, plasma-devel, lesliezhai, ali-mohamed, 
jensreuterberg, abetts, sebas

[Differential] [Commented On] D2409: Update Color KCM

[ochurlaud (Olivier Churlaud)]

ochurlaud added a comment.


  In https://phabricator.kde.org/D2409#45025, @andreaska wrote:
  
  > Thanks Oliver,
  >
  > can you post some screenshots cause I can't compile it.
  
  
  Updated

REPOSITORY
  rPLASMADESKTOP Plasma Desktop

REVISION DETAIL
  https://phabricator.kde.org/D2409

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, #plasma, mart, andreask, #vdg
Cc: andreaska, plasma-devel, lesliezhai, ali-mohamed, jensreuterberg, abetts, 
sebas

[Differential] [Updated] D2409: Update Color KCM

[ochurlaud (Olivier Churlaud)]

ochurlaud updated the summary for this revision.

REPOSITORY
  rPLASMADESKTOP Plasma Desktop

REVISION DETAIL
  https://phabricator.kde.org/D2409

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, #plasma, mart, andreask, #vdg
Cc: andreaska, plasma-devel, lesliezhai, ali-mohamed, jensreuterberg, abetts, 
sebas

[Differential] [Request, 5,159 lines] D2409: Update Color KCM

[ochurlaud (Olivier Churlaud)]

ochurlaud created this revision.
ochurlaud added reviewers: Plasma, mart, andreask, VDG.
ochurlaud set the repository for this revision to rPLASMADESKTOP Plasma Desktop.
Restricted Application added a project: Plasma.
Restricted Application added a subscriber: plasma-devel.

REVISION SUMMARY
  As discussed with the VDG, the color KCM had to be split in a very simple KCM 
to choose a color scheme, and a color scheme editor.
  
  What is here?
  -
  
  - I rewrote/refactor almost all the code so that it's easier to understand 
(hopefully).
  - I created a standalone app to edit.
  
  Here are the current issues:
  
  
  1. I reuse the headers/cpp files of the standalone app in the kcm. It would 
be better to directly call the app, but then I don't know how to repopulate the 
list when I'm done with the app (see in KColorCm::on_schemeEditButton_clicked)
  
  2. The standalone app has not a correct name (How should I call the 
executable and the app?)
  
  3. The standalone app doesn't have all the KAboutData + CommandParser things, 
because I'm a little lazy.
  
  To test directly, you can use the branch `andreas/kcm_update`

REPOSITORY
  rPLASMADESKTOP Plasma Desktop

REVISION DETAIL
  https://phabricator.kde.org/D2409

AFFECTED FILES
  kcms/colors/CMakeLists.txt
  kcms/colors/colorscm.cpp
  kcms/colors/colorscm.h
  kcms/colors/colorsettings.ui
  kcms/colors/schemeeditor.cpp
  kcms/colors/scmeditorcolors.cpp
  kcms/colors/scmeditorcolors.h
  kcms/colors/scmeditorcolors.ui
  kcms/colors/scmeditordialog.cpp
  kcms/colors/scmeditordialog.h
  kcms/colors/scmeditordialog.ui
  kcms/colors/scmeditoreffects.cpp
  kcms/colors/scmeditoreffects.h
  kcms/colors/scmeditoreffects.ui
  kcms/colors/scmeditoroptions.cpp
  kcms/colors/scmeditoroptions.h
  kcms/colors/scmeditoroptions.ui

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, #plasma, mart, andreask, #vdg
Cc: plasma-devel, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas

[Powerdevil] [Bug 366402] Closing the lid triggers Sleep

[Olivier Churlaud via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366402

--- Comment #2 from Olivier Churlaud <oliv...@churlaud.com> ---
In this case, Powerdevil should be able to change this..

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 366402] New: Closing the lid triggers Sleep

[Olivier Churlaud via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366402

Bug ID: 366402
   Summary: Closing the lid triggers Sleep
   Product: Powerdevil
   Version: 5.7.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-devel@kde.org
  Reporter: oliv...@churlaud.com

Since last update, if I close the lid my laptop go to sleep.

In Energy saving is set: When the lid is closed: "Don't do anything"

I spoke with Kai and here are the info I gave him:

- Starting KDED from konsole:

kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/qt/plugins/kf5/kded/ksysguard.so"
kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/qt/plugins/kf5/kded/networkwatcher.so"
kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/qt/plugins/kf5/kded/statusnotifierwatcher.so"
kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/qt/plugins/kf5/kded/solidautoeject.so"
kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/qt/plugins/kf5/kded/ktimezoned.so"
kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/qt/plugins/kf5/kded/networkmanagement.so"
kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/qt/plugins/kf5/kded/khotkeys.so"
kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/qt/plugins/kf5/kded/networkstatus.so"
kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/qt/plugins/kf5/kded/soliduiserver.so"
kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/qt/plugins/kf5/kded/powerdevil.so"
kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/qt/plugins/kf5/kded/keyboard.so"
kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/qt/plugins/kf5/kded/device_automounter.so"
kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/qt/plugins/kf5/kded/proxyscout.so"
kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/qt/plugins/kf5/kded/recentdocumentsnotifier.so"
kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/qt/plugins/kf5/kded/kscreen.so"
kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/qt/plugins/kf5/kded/bluedevil.so"
kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/qt/plugins/kf5/kded/remotedirnotify.so"
kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/qt/plugins/kf5/kded/desktopnotifier.so"
kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/qt/plugins/kf5/kded/baloosearchmodule.so"
kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/qt/plugins/kf5/kded/freespacenotifier.so"
kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/qt/plugins/kf5/kded/appmenu.so"
kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/qt/plugins/kf5/kded/kwrited.so"
Reusing existing ksycoca
Recreating ksycoca file
("/home/olivier/.cache/ksycoca5_en_tzuXy0i69O7VECxsx72nVId6iK0=", version 303)
Still in the time dict (i.e. deleted files) ("apps")
kf5.kservice.sycoca: Parse error in 
"/home/olivier/.config/menus/applications-merged/xdg-desktop-menu-dummy.menu" ,
line  1 , col  1 :  "unexpected end of file"
kf5.kservice.sycoca: The menu spec file contains a Layout or DefaultLayout tag
without the mandatory Merge tag inside. Please fix your file.
kf5.kservice.sycoca: The menu spec file contains a Layout or DefaultLayout tag
without the mandatory Merge tag inside. Please fix your file.
kf5.kservice.sycoca: The menu spec file contains a Layout or DefaultLayout tag
without the mandatory Merge tag inside. Please fix your file.
kf5.kservice.sycoca: The menu spec file contains a Layout or DefaultLayout tag
without the mandatory Merge tag inside. Please fix your file.
kf5.kservice.sycoca: The menu spec file contains a Layout or DefaultLayout tag
without the mandatory Merge tag inside. Please fix your file.
Saving
kf5.kded: found kded module "accounts" by prepending 'kded_' to the library
path, please fix your metadata.
kf5.kded: found kded module "printmanager" by prepending 'kded_' to the library
path, please fix your metadata.
powerdevil: Backend loaded, loading core
powerdevil: Core loaded, initializing backend
powerdevil: Using XRandR
powerdevil: Screen brightness value:  703
powerdevil: Screen brightness value max:  937
powerdevil: current screen brightness value:  703
powerdevil: Backend is ready, KDE Power Management system initialized
powerdevil: Battery with UDI "/org/freedesktop/UPower/devices/battery_BAT0" was
detected
XSync seems available and ready
XSync Inited
Supported, init completed
powerdevil: Session path: "/org/freedesktop/login1/session/c5"
powerdevil: ACTIVE SESSION PATH: "/org/freedesktop/login1/session/c5"
powerdevil: Current session is now active
powerdevil: fd passing available: true
powerdevil: systemd powersave events handling inhibited, descriptor: 25
powerdevil: systemd support initialized
powerdevil: Got a valid offer for  "DPMSControl"
powerdevil: Core is ready, registering various services on the bus...
powerdevil: Can't contact ck
powerdevil: We are now into activity  "----"

Re: Selecting a Plasma logo

[Olivier Churlaud]

Ivan a écrit :

The one that stands out for me is one of the Kver's mesh-ups. The one
with a part of the current plasma logo '>' inside two pieces of a
gear.

The reason I find that one interesting is that we could use a part of
it for the launcher icon if we wanted - just the '>'.

We could include the gear part, or two. It is open to modification.
The first thing that came to me was that we could easily make t-shirts
for a conference where the 'bumps' on the top gear would be
recognizable buildings of the city we are in.

I like the idea!

I really think the 4th of Ken look like a IM logo. It's the very first 
thing I think about when I see it.


Olivier
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Differential] [Commented On] D2270: Try to be more clever about what sink to use for volume control

[ochurlaud (Olivier Churlaud)]

ochurlaud added a comment.


  Just tested, in my case it solves https://bugs.kde.org/show_bug.cgi?id=365771

REPOSITORY
  rPLASMAPA Plasma Audio Volume Applet

REVISION DETAIL
  https://phabricator.kde.org/D2270

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: drosca, #plasma
Cc: ochurlaud, plasma-devel, jensreuterberg, abetts, sebas
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Differential] [Abandoned] D2212: Reduce Calendar size in Digital clock

[ochurlaud (Olivier Churlaud)]

ochurlaud abandoned this revision.
ochurlaud added a comment.


  Screen too small, and would be a fix only for a niche type of users

REPOSITORY
  rPLASMAWORKSPACE Plasma Workspace

REVISION DETAIL
  https://phabricator.kde.org/D2212

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, #plasma:_design, #plasma, davidedmundson
Cc: colomar, sebas, mart, broulik, drosca, andreaska, mck182, plasma-devel, 
jensreuterberg, abetts
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Differential] [Commented On] D2212: Reduce Calendar size in Digital clock

[ochurlaud (Olivier Churlaud)]

ochurlaud added a comment.


  So just to show exactly my issue:
  F189465: comments.png 
  
  Other applets are very fine! but look at the font size difference between the 
clock and the different parts of the calendar.
  
  I think on big screens it's good but not for people with 14'' screens...  
1366x768...

REPOSITORY
  rPLASMAWORKSPACE Plasma Workspace

REVISION DETAIL
  https://phabricator.kde.org/D2212

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, #plasma:_design, #plasma, davidedmundson
Cc: colomar, sebas, mart, broulik, drosca, andreaska, mck182, plasma-devel, 
jensreuterberg, abetts
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Differential] [Commented On] D2212: Reduce Calendar size in Digital clock

[ochurlaud (Olivier Churlaud)]

ochurlaud added a comment.


  In https://phabricator.kde.org/D2212#41485, @sebas wrote:
  
  > -1, the calendar is only going to look more cramped like this.
  >
  > Whitespace is useful and part of the visual language, don't just remove it.
  >
  > Also, the size of the calendar is oriented with the size of the systray 
popup, this change will make it inconsistent, and making the systray popup 
smaller is not an option since it's already pretty densely populated (e.g. 
networkmanager, bluetooth don't looked especially spacious).
  
  
  But it takes more than half of my screen !!! I tend to think it should follow 
the size of the panel, but this is more work

REPOSITORY
  rPLASMAWORKSPACE Plasma Workspace

REVISION DETAIL
  https://phabricator.kde.org/D2212

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, #plasma:_design, #plasma, davidedmundson
Cc: sebas, mart, broulik, drosca, andreaska, mck182, plasma-devel, 
jensreuterberg, abetts
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Differential] [Commented On] D2212: Reduce Calendar size in Digital clock

[ochurlaud (Olivier Churlaud)]

ochurlaud added a comment.


  @sebas: just for info, is here my panel config:
  
  [PlasmaViews][Panel 97][Horizontal1366]
  length=1164
  thickness=24
  
  the thickness is very small, and changing the font *does not* change the font 
in the calendar.

REPOSITORY
  rPLASMAWORKSPACE Plasma Workspace

REVISION DETAIL
  https://phabricator.kde.org/D2212

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, #plasma:_design, #plasma, davidedmundson
Cc: colomar, sebas, mart, broulik, drosca, andreaska, mck182, plasma-devel, 
jensreuterberg, abetts
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Differential] [Commented On] D2212: Reduce Calendar size in Digital clock

[ochurlaud (Olivier Churlaud)]

ochurlaud added a comment.


  In https://phabricator.kde.org/D2212#41483, @mck182 wrote:
  
  > In https://phabricator.kde.org/D2212#41055, @drosca wrote:
  >
  > > The calendar popup size is fine for me (with patched plasma-framework), 
what I *still* think is broken is the gridSize scaling - see 
https://git.reviewboard.kde.org/r/125773/
  > >
  > > You can also test it simply by switching font to DejaVu Sans.
  >
  >
  > Olivier, have you tried David's suggestion^? Does it make any difference? I 
also think the patch mentioned above should be in.
  
  
  Changing the font to DejaVuSans only changes the time font, but not the 
calendar one.
  
  I'll try his patch.

REPOSITORY
  rPLASMAWORKSPACE Plasma Workspace

REVISION DETAIL
  https://phabricator.kde.org/D2212

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, #plasma:_design, #plasma, davidedmundson
Cc: mart, broulik, drosca, andreaska, mck182, plasma-devel, jensreuterberg, 
abetts, sebas
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Differential] [Commented On] D2212: Reduce Calendar size in Digital clock

[ochurlaud (Olivier Churlaud)]

ochurlaud added a comment.


  In https://phabricator.kde.org/D2212#41053, @andreaska wrote:
  
  > the reduced calender size in the widget is way better than before, but 
what's with the text (time) in the panel? the time height in the panel should 
be the same height than the system tray icon
  
  
  This is because on the "before" i use plasmashell from my distrib, "after" 
compiled from myself and the latter has font issues.
  
  In https://phabricator.kde.org/D2212#41057, @broulik wrote:
  
  > The spacing is completely off now and the pin overlaps the calendar...
  
  
  True, I haven't see that. Sh*t!
  
  Anyway, it's really too big ATM. it takes more than half of my screen, with 
huge fonts: it's ridiculous I think.
  I can work on this, but I'll need some pointers on what and where to change 
things.

REPOSITORY
  rPLASMAWORKSPACE Plasma Workspace

REVISION DETAIL
  https://phabricator.kde.org/D2212

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, #plasma:_design, #plasma, davidedmundson
Cc: broulik, drosca, andreaska, mck182, plasma-devel, jensreuterberg, abetts, 
sebas
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Differential] [Commented On] D2212: Reduce Calendar size in Digital clock

[ochurlaud (Olivier Churlaud)]

ochurlaud added a comment.


  Before: 
  F188019: Screenshot_20160719_101221.png 
  
  After:
  F188021: Screenshot_20160719_101336.png 

REPOSITORY
  rPLASMAWORKSPACE Plasma Workspace

REVISION DETAIL
  https://phabricator.kde.org/D2212

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, #plasma:_design, #plasma, davidedmundson
Cc: mck182, plasma-devel, jensreuterberg, abetts, sebas
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Differential] [Updated] D2212: Reduce Calendar size in Digital clock

[ochurlaud (Olivier Churlaud)]

ochurlaud updated the summary for this revision.

REPOSITORY
  rPLASMAWORKSPACE Plasma Workspace

REVISION DETAIL
  https://phabricator.kde.org/D2212

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, #plasma:_design, #plasma, davidedmundson
Cc: plasma-devel, jensreuterberg, abetts, sebas
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Differential] [Request, 4 lines] D2212: Reduce Calendar size in Digital clock

[ochurlaud (Olivier Churlaud)]

ochurlaud created this revision.
ochurlaud added reviewers: Plasma: Design, Plasma, davidedmundson.
ochurlaud set the repository for this revision to rPLASMAWORKSPACE Plasma 
Workspace.
ochurlaud added a project: Plasma.
Restricted Application added a subscriber: plasma-devel.

REVISION SUMMARY
  I reduced so that it looks better on my screen. I cannot try on HDPI ...
  
  What I would like to do as well is:
  
  - to reduce the month name size  and the day + day number which are very huge
  - to have the day numbers (in the grid) filling more each cell
  
  Both seem to be done by the theme, so no idea where to look.

REPOSITORY
  rPLASMAWORKSPACE Plasma Workspace

REVISION DETAIL
  https://phabricator.kde.org/D2212

AFFECTED FILES
  applets/digital-clock/package/contents/ui/CalendarView.qml

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: ochurlaud, #plasma:_design, #plasma, davidedmundson
Cc: plasma-devel, jensreuterberg, abetts, sebas
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 358859] New: Screen not always locked when lid closed

[Olivier Churlaud via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358859

Bug ID: 358859
   Summary: Screen not always locked when lid closed
   Product: Powerdevil
   Version: 5.5.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-devel@kde.org
  Reporter: oliv...@churlaud.com

When I close the lid of my computer, it's quite often that when I open it I
don't need to type my password.

The network takes some seconds to reconnect, which means that is was suspended. 

Of course in the settings I said: lock screen on suspend. It however doesn't
always happen.

=> Security issue: so I raise the severity to major.

I don't know how to debug further...

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 358859] Screen not always locked when lid closed

[Olivier Churlaud via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358859

--- Comment #1 from Olivier Churlaud <oliv...@churlaud.com> ---
next time it happens I'll send the journalctl concerned part..

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 349750] Laptop does not suspend when lid closed in lock screen

[Olivier Churlaud via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=349750

Olivier Churlaud <oliv...@churlaud.com> changed:

   What|Removed |Added

 CC||oliv...@churlaud.com

--- Comment #2 from Olivier Churlaud <oliv...@churlaud.com> ---
Created attachment 96950
  --> https://bugs.kde.org/attachment.cgi?id=96950=edit
dump of the interesting part of journalctl

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 358859] Screen not always locked when lid closed

[Olivier Churlaud via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358859

Olivier Churlaud <oliv...@churlaud.com> changed:

   What|Removed |Added

   Platform|Other   |Archlinux Packages

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 349750] Laptop does not suspend when lid closed in lock screen

[Olivier Churlaud via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=349750

--- Comment #3 from Olivier Churlaud <oliv...@churlaud.com> ---
Oups wrong thread...  please forget this last one...

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: 5.5 video

[Olivier Churlaud]

Hi,

Great job!

I have some feedback, maybe for the next version.. Don't take it bad, I 
really value your work: it's just another view point I wanted to give.


After having seen the gnome video, I think that music doesn't contribute 
to seem "pro".


I don't know how they achieve this quality (it really looks like a pro 
advertisement), but it seems like the direction to follow, isn't it?


A company should be able to show the presentation video to it's 
stockholders and say: "we move to this". I don't know if the current 
video can be used like this.


Again, it's only my very personal opinion, and I wouldn't be able to do 
half of what you did, so I totally respect what you did.


Cheers
Olivier

Date: Mon, 7 Dec 2015 06:56:53 +0100
From: Lucas S 
To: plasma-devel@kde.org
Subject: 5.5 video
Message-ID:

Content-Type: text/plain; charset=UTF-8

Hi
Thanks for all comments. I think that I fixed most (all?) remaining issues.

- Improved  visibility of the text by adding black transparent
background and by moving to the beginning of the sequences
- Fixed a typo
- Added 2 more activities so filtering looks more natural now. (With
more than 5 activities there is a scrollbar visible, which looks kinda
out of place)
- Removed a window with activities settings
- Improved muon part (cropped "freedom")
- Added simple fade in/fade out effect for the first and last title
(but still think that 3d dissolving animation looked the best ;))

Link:
https://youtu.be/DsSyPpHS6HI

Cheers
Lucas



___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: Fwd: Custom shell and corona

[Olivier Churlaud]

Hi,

Meanwhile I registered on the list. However there is so much traffic 
that I am in digest mode.


Le 30/11/2015 15:25, Marco Martin a écrit :

Hi, resending to you as i noted now you aren't subscribed (perhaps if
you subscribe for a while would make things faster)



On Sun, Nov 29, 2015 at 9:08 PM, Olivier Churlaud <oliv...@churlaud.com> wrote:


  - Put some connections between the main app and the plasmoid. I don't know
how to do that because I've never really used QML, but I think it should not
be to complicated.
  -> Question: do we do this by QDbus, or by DataEngine (I think it's the
name of the thing)?

You have several ways, that all are quite simple:
you can do a DataEngine (how did Amarok1 do? if it was based on
dataengines they can all be just ported as the api there didn't
change)
Or you can have amarok applets using a subclass of Plasma::Applet ,
which shares a singleton with the Amarok app. Being in the same
process, everybody can just communicate by reading and writing that
single object instance (I can tell you the more detailed steps)
Just for your information, applets in amarok were all inheriting from 
Plasma::Applet. Now it's a pure functional class (no view in it) and I 
think that if we want to let people create 3rd party applets that they 
can easily install from KDE-apps, we should stay in full QML-plasmoids 
for our applets.


Is it compatible with the Plasma::Applet use?

Feedback about plasma-framework
===
  - To add a container, one must use PlasmaQuick::ContainmentView, which is a
QQuickWindow and should therefore be toplevel. It's not so good, if I want
to put it as a widget in a QDialog or something else. Another class would be
good for applications.

The problem there is that QML stuff can't be directly used in QWidget
based applications because they are two different kinds of windows,
you can embed them with
http://doc.qt.io/qt-5/qwidget.html#createWindowContainer
(not a problem of plasma, it's an issue in the use of QML in general)
I'm already using this function, but what I was pointing out is that the 
QML view is a QQuickWindow and coul be a simple Item or something like 
this, to be easily added in a simple widget.

  - The Shortcuts defined for the desktop are also defined for the custom
shell, even with a minimal Shell that contains only

  Item { id: root; property Item containment; }

In my case, if I scroll on the QML object it changes my virtual desktop !!

for both those things it will need a custom shell package that
disables the shortcut setting dialog and the action plugins (mouse
wheel, context menus)
I was thinking to add one ready for this in plasma-framework, so you
can ignore that for now
Ok: if I can help, please tell me, I can use your branch or create a new 
one from this one.


Cheers
Olivier
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Custom shell and corona

[Olivier Churlaud]

 Hi,

I'm now done with this first custom shell we spoke about with Marco.  If 
you answer, please put me in copy since I'm not registered on this 
MailingList.


You can see it at 
https://quickgit.kde.org/?p=scratch%2Fochurlaud%2Fplasma-skratch.git


What is currently missing

 - Define the size of the QML object when inserted. I'm not able to do 
this, I don't know why.
 - Put some connections between the main app and the plasmoid. I don't 
know how to do that because I've never really used QML, but I think it 
should not be to complicated.
 -> Question: do we do this by QDbus, or by DataEngine (I think it's 
the name of the thing)?


Feedback about plasma-framework
===
 - To add a container, one must use PlasmaQuick::ContainmentView, which 
is a QQuickWindow and should therefore be toplevel. It's not so good, if 
I want to put it as a widget in a QDialog or something else. Another 
class would be good for applications.
 - The Shortcuts defined for the desktop are also defined for the 
custom shell, even with a minimal Shell that contains only


 Item { id: root; property Item containment; }

In my case, if I scroll on the QML object it changes my virtual desktop !!

I'll be slowly trying to implement this on amarok, if any help on your 
side is very welcomed (about this missing classes, mainly)


Cheers!
Olivier
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Custom shell and corona

[Olivier Churlaud]

 Hi,

I'm now done with this first custom shell we spoke about with Marco.

You can see it at 
https://quickgit.kde.org/?p=scratch%2Fochurlaud%2Fplasma-skratch.git


What is currently missing

 - Put some connections between the main app and the plasmoid. I don't 
know how to do that because I've never really used QML, but I think it 
should not be to complicated.
 -> Question: do we do this by QDbus, or by DataEngine (I think it's 
the name of the thing)?


Feedback about plasma-framework
===
 - To add a container, one must use PlasmaQuick::ContainmentView, which 
is a QQuickWindow and should therefore be toplevel. It's not so good, if 
I want to put it as a widget in a QDialog or something else. Another 
class would be good for applications.
 - The Shortcuts defined for the desktop are also defined for the 
custom shell, even with a minimal Shell that contains only


 Item { id: root; property Item containment; }

In my case, if I scroll on the QML object it changes my virtual desktop !!

I'll be slowly trying to implement this on amarok, if any help on your 
side is very welcomed (about this missing classes, mainly)


Cheers!
Olivier
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel