<div class="gmail_quote">2011/2/11 Martin Gräßlin <span dir="ltr"><<a href="mailto:kde@martin-graesslin.com">kde@martin-graesslin.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
----- Ursprüngliche Mitteilung -----<br>
<div class="im">> (There's a lot of replies, so I'm going to answer to the topics).<br>
><br>
> As for the "Windows inside plasmoids is ugly" part, when I said my idea<br>
> was to make applications and plamoids the same thing, I meant it form<br>
> the POV of the user. Internally, they would remain different -- note<br>
> that, in my mockups, a plasmoid does not leave background (although this<br>
> is not very clear, I admit). Actually, they would still remain different<br>
> at all, just with more interaction.<br>
</div>Currently Plasma is just a window. The contents of the plasma window is unknown to anything outside Plasma. Each other window could just destroy your idea by overlapping the interaction areas. To make it work plasmoids and windows need to be in the same layer. Either each Plasmoid is a window or each window is a plasmoid. For technical reasons the latter is not useful with X but might be with Wayland </blockquote>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
><br>
> As for "You'll need to create a whole new WM from scratch", I don't<br>
> understand why. This new plasma shell wouldn't drop any KWin feature a<br>
> priori, it would just, as I said, make it interact with plasma and,<br>
> perhaps, hide the titlebar and/or modify window's borders. It would be<br>
> just like Marco said.<br>
</div>Yes that gets in the area where a new window manager is needed. Kwin does not support the required functionality and it's very unlikely to be added.<br>
<div class="im">><br>
> By the way, how does resizing work? I think KWin sends some kind of<br>
> signal to the application, but I don't know X, so I don't know. But, if<br>
> so, could it be used for this matter?<br>
</div>Resizing is a complex operation involving windowmanager, X and the client.<br>
<div class="im">><br>
> About "KWin scripting is not powerful enough", maybe we could extend it<br>
> to do whatever is needed. But I don't think it would be necessary --<br>
> not, at least, in the beginning.<br>
</div>No sorry extending kwin to support it is out of bounds at the current stage.<br>
<div class="im">><br>
> About "Sorry for being the bad guy", there's no problem at all.<br>
> Actually, I want you to show me what's possible and what's not. My<br>
> intention here is not to make a shell that resembles exactly my mockups,<br>
> but rather showing an ideal mockup and see what I can do out of it.<br>
><br>
> Oh, and thank you guys for the answers. I'm doing some more mockups right<br>
> now, btw.<br>
<br>
</div><div><div></div><div class="h5">_______________________________________________<br>
Plasma-devel mailing list<br>
<a href="mailto:Plasma-devel@kde.org">Plasma-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/plasma-devel" target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br>
</div></div></blockquote></div><br>Well... I see now how it's complex. But what if I removed all this complex interaction from my ideas for a (big) while and just wanted to create a more dynamic plasma shell? I mean, I can't have all geometries of all windows updated at the same time, but I at least can know whether there's any window opened, can't I -- IIRC kdeworkspace provides a list of opened windows? If so, we'd have a plasma dashboard when no window is opened and a bar with all plasmoids iconfied when there are windows, for example. Is that feasible?<br clear="all">
<br>-- <br>Luiz Romário Santana Rios<br>