[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-panel-devel
Subject:    D8444: Define default Action when we plug unknown monitor
From:       Daniel_Vrátil <noreply () phabricator ! kde ! org>
Date:       2017-12-06 13:30:56
Message-ID: 20171206133056.97455.CC82D19C3BEC3AC2 () phabricator ! kde ! org
[Download RAW message or body]

dvratil added a comment.


  @sebas suggested we approach it as an OSD that would appear on screen and allow the \
user to select an action they want to take. I think it's a good approach, even more \
flexible than an option in the KCM.  And IIRC it was also what we planned long time \
ago when I was working on KScreen, but never got around to implement it :-).  
  Now the question is how should we approach it code-wise: should we write our own \
OSD in the KScreen KDED module, or should we extend the Plasmashell OSD code and \
expose it on the org.kde.osdService interface and only have KScreen interact with it \
via DBus? What would you guys prefer?

REPOSITORY
  R104 KScreen

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

To: mlaurent, davidedmundson
Cc: mwolff, sebas, graesslin, dvratil, davidedmundson, ngraham, plasma-devel, \
ZrenBot, progwolff, lesliezhai, ali-mohamed, jensreuterberg, abetts, apol, mart


[Attachment #3 (unknown)]

<table><tr><td style="">dvratil added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: \
right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: \
#F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: \
inline-block; border: 1px solid rgba(71,87,120,.2);" \
href="https://phabricator.kde.org/D8444" rel="noreferrer">View \
Revision</a></tr></table><br /><div><div><p><a \
href="https://phabricator.kde.org/p/sebas/" style="  border-color: #f1f7ff;
              color: #19558d;
              background-color: #f1f7ff;
                border: 1px solid transparent;
                border-radius: 3px;
                font-weight: bold;
                padding: 0 4px;" rel="noreferrer">@sebas</a> suggested we approach it \
as an OSD that would appear on screen and allow the user to select an action they \
want to take. I think it&#039;s a good approach, even more flexible than an option in \
the KCM.  And IIRC it was also what we planned long time ago when I was working on \
KScreen, but never got around to implement it :-).</p>

<p>Now the question is how should we approach it code-wise: should we write our own \
OSD in the KScreen KDED module, or should we extend the Plasmashell OSD code and \
expose it on the org.kde.osdService interface and only have KScreen interact with it \
via DBus? What would you guys prefer?</p></div></div><br \
/><div><strong>REPOSITORY</strong><div><div>R104 KScreen</div></div></div><br \
/><div><strong>REVISION DETAIL</strong><div><a \
href="https://phabricator.kde.org/D8444" \
rel="noreferrer">https://phabricator.kde.org/D8444</a></div></div><br \
/><div><strong>To: </strong>mlaurent, davidedmundson<br /><strong>Cc: \
</strong>mwolff, sebas, graesslin, dvratil, davidedmundson, ngraham, plasma-devel, \
ZrenBot, progwolff, lesliezhai, ali-mohamed, jensreuterberg, abetts, apol, mart<br \
/></div>



[prev in list] [next in list] [prev in thread] [next in thread]