I have been trying to use activities in my daily work and found some problems. I have set up two activities: <br> - the "work" activity is a folder view without any other widgets, which I use for coding.<br> - the "browse" activity is a desktop containing a lot of social and news widgets, which I use for leisure browsing.<br>
<br>I also have some windows (such as IDEs, editors, konsoles) for "work", and some other windows (such as browsers) for
"browse". Because windows are not managed by activities, I have to put them in two virtual desktops. So every time I switch activities, I also have to switch virtual desktops, which is inconvenient to me.<br><br>
I understand currently activities and virtual desktops are totally disassociated. Virtual desktop manages windows, while activity manages widgets -- they are two universes and have no business with each other, but this setting doesn't solve my case. IMHO, widgets and windows are not orthogonal, neither are activities and virtual desktops.<br>
<br><div class="gmail_quote">On Fri, Feb 25, 2011 at 9:44 AM, Aaron J. Seigo <span dir="ltr"><<a href="mailto:aseigo@kde.org">aseigo@kde.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Thursday, February 24, 2011, Hans Chen wrote:<br>
> What I want to know is the following: Are there any plans or outlines<br>
> regarding how to proceed with virtual desktop (and activities)? Are they<br>
<br>
</div>they are orthogonal concepts and i don't think we should at this time get too<br>
worked up about them.<br>
<br>
for those who don't use virtual desktops now -> not an issue<br>
for those who don't use activities -> not an issue<br>
for those who use both happily -> not an issue<br>
<br>
people who know virtual desktops but who are learning and using activities are<br>
the only ones really affected, and i think it's likely to be a "growing pains"<br>
issue as they adjust. it may just as well work itself out naturally.<br>
<br>
we don't know what their resulting work flows will be yet. that would be a<br>
matter for a field study or we can just wait and see. if/when we do know what<br>
the resulting work flow typically is for a virtual desktop and activities<br>
user, we can then take this topic up if we wish to.<br>
<br>
but imho right now it's "not an issue" :)<br>
<font color="#888888"><br>
--<br>
Aaron J. Seigo<br>
humru othro a kohnu se<br>
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43<br>
<br>
KDE core developer sponsored by Qt Development Frameworks<br>
</font><br>_______________________________________________<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>
<br></blockquote></div><br><br clear="all"><br>-- <br>Best wishes<br>ZHANG Kun<br>