On mercoledì 25 luglio 2018 12:12:58 CEST David Edmundson wrote:
> Adding 1 would mean having the relevant UIs have a separate add activity /
> add a new VD to this activity which needs some quite a few more changes.
yeah, i was talking about what would happen in the ui, of course the backend
>
> I don't have a strong opinion about
>
> * I don't have a strong opinion about what we do in the front end
On Wed, Jul 25, 2018 at 10:43 AM, Marco Martin wrote:
> On martedì 17 luglio 2018 11:16:29 CEST David Edmundson wrote:
> > > Yes, if you were to configure it to have 4 desktops per activity and
> you
> >
> > add an activity you get 4 more desktops.
> >
> > David
> shouldn't be more, add an
> shouldn't be more, add an activity you get one new virtual desktop,
> then you can add more for that activity if you want?
+1 I guess that original David's comment was about when we thought all
activities would have the same number of VDs.
Cheers,
Ivan
--
KDE, ivan.cu...@kde.org,
On martedì 17 luglio 2018 11:16:29 CEST David Edmundson wrote:
> > Yes, if you were to configure it to have 4 desktops per activity and you
>
> add an activity you get 4 more desktops.
>
> David
shouldn't be more, add an activity you get one new virtual desktop, then you
can add more for that
> Couldn't we teach each Swoosh how to have its own set of favorites,
> recents etc, but also how to inherit the "standard" or "default" set?
> Then a Swoosh could be either an Activity or a Virtual Desktop.
So, configuration? That would work if it can be made pretty.
Cheers,
Ivan
Couldn't we teach each Swoosh how to have its own set of favorites,
recents etc, but also how to inherit the "standard" or "default" set?
Then a Swoosh could be either an Activity or a Virtual Desktop.
Nate
On 07/17/2018 07:03 AM, Ivan Čukić wrote:
UI-wise:
We currently (let's pretend)
UI-wise:
We currently (let's pretend) have two options for the users (I've
replaced the terms activity and VD with 'swoosh' inspired by the
former Mozilla problem):
- have multiple swooshes where favourites, recents etc. are shared
- have multiple swooshes where favorties, recents are per-swoosh
On Tue, Jul 17, 2018 at 8:55 AM, Marco Martin wrote:
> On lunedì 16 luglio 2018 12:44:13 CEST David Edmundson wrote:
> > As for my mod, in my head it's basically what you just said above.
> Clicking
> > + creates an activity which means KAMD then creates a N desktops.
> Clicking
> > - tells KAMD
On lunedì 16 luglio 2018 12:44:13 CEST David Edmundson wrote:
> As for my mod, in my head it's basically what you just said above. Clicking
> + creates an activity which means KAMD then creates a N desktops. Clicking
> - tells KAMD to delete the activity which in turn deletes N desktops. Might
I
On Mon, Jul 16, 2018 at 12:44 PM David Edmundson
wrote:
> I'm not set in stone on that, depends a bit on getting feedback about the
> explicit problems with merging.
I think the problem is that not many people fully understand what your
proposed solution would look like in the end. I at least
For the vast majority of users my proposal is identical to your proposal.
The only real difference is in mine we explicitly say that we never assume
VD ID == activity ID which can allow for most future complexity should
someone want to both implement and opt into it.
> (switching activities
>
On Fri, Jul 13, 2018 at 1:54 PM David Edmundson
wrote:
> work - 1
> work - 2
> browsing - 1
> browsing - 2
I really don't like having a different set of desktops for each
activity, to me would be really confusing, and i don't think it would
cover my main use case? (switching activities
Perhaps i
On Sun, Jul 15, 2018 at 3:57 PM Martin Flöser wrote:
> Activities are weird and we (Thomas and I) never knew what they are and
> how we should integrate them in KWin. The existing code is just a bad
> copy of virtual desktops (bad because it copied the code 1:1 without
> understanding what it
On Fri, Jul 13, 2018 at 6:20 PM David Edmundson
wrote:
> - effects show more options
> - pager will show more options
> - set on activity desktop menu will show more options
> (not really a huge issue. Just don't change activities if you don't want to
> change activities)
To me that's
Hi all,
just chiming in to give some KWin perspective.
Activities are weird and we (Thomas and I) never knew what they are and
how we should integrate them in KWin. The existing code is just a bad
copy of virtual desktops (bad because it copied the code 1:1 without
understanding what it does
I find it very constructive in the discussion that everyone speaks its
mind in order to understand better what we are trying to accomplish
here. Based on that I think that there are some goals that almost
all agree.
G1: Simplify the Activities/VDs infrastructure for kwin and plasma desktop
in
On Fri, Jul 13, 2018 at 1:54 PM David Edmundson
wrote:
> * Windows are not directly associated with activities
>
> * Windows are on N virtual desktops
>
> * Kwin and plasmashell taskamanager/pagers only speak virtual desktops.
> References to both VDs and activities in the UI are reduced to 1
On Thu, Jul 12, 2018 at 4:43 PM Ivan Čukić wrote:
> Activities are not meant to be switched overly often. In the way that
> I see activities, you switch to an activity and work for at least half
> an hour. If a project deserves less time to focus on than half an
> hour, it is either a one of a
On Fri, Jul 13, 2018 at 5:51 PM, Ivan Čukić wrote:
> > I think kwin shouldn't filter them. Pager lists all, effects and
> shortcuts
> > cover all.
>
> Ugh... I think that will kill the group 'C'*. While it /would/ be
> possible to to use multi-VD-multi-activity setup, it would be far from
>
> Work "stack" Home "stack"
> || ||
> |VD 1| |VD 3|
> | Web browser| | Web browser|
> | IDE| |Music player|
> || ||
>
> || ||
> |VD 2| |VD
> I think kwin shouldn't filter them. Pager lists all, effects and shortcuts
> cover all.
Ugh... I think that will kill the group 'C'*. While it /would/ be
possible to to use multi-VD-multi-activity setup, it would be far from
convenient.
Or it would require an alternative set of applets that
On Fri, 13 Jul 2018 08:22:31 -0700 Ivan Čukić wrote
> This would provide the more obvious distinction - "groups" are for
> window management and "activities" are about providing different
> workspaces. "groups" would be volatile in the sense that their number
> can vary a lot
VDs to inform KWin, if they are not part of the current activity and
> therefore should not be switched to when switching through VDs. Also
> the pager must know which VDs not to display in the current activity.
> But as said this can be a porperty on the VDs and not on the Activity.
> >
>
I
@David
Regarding the backend (wherever the actual logic ends up in - kwin or
kamd), your idea does sound nice. It would also provide the ability
that some of the 'C' category users wanted - to have variable number
of VDs per activity.
But the problem is not primarily how to handle the
On Fri, Jul 13, 2018 at 1:54 PM David Edmundson
wrote:
>
> Whilst personally I am in favour of just completely unifying, I think there's
> an option that might be a happy medium.
>
> ---
>
> If we were to unify, we would do the following:
So the following is not the "happy medium", but what you
Whilst personally I am in favour of just completely unifying, I think
there's an option that might be a happy medium.
---
If we were to unify, we would do the following:
* Windows are not directly associated with activities
* Windows are on N virtual desktops
* Kwin and plasmashell
On Thursday, July 12, 2018 4:36:02 PM CDT Michail Vourlakos wrote:
> 2018-07-12 17:43 GMT+03:00 Marco Martin :
> As a plasma user I am a [Multiple Activities and 1 VD] user so I am get used
> in that workflow and I wouldnt like to miss it :)
>
>
> I have in my mind without any
> study but only
On 07/12/2018 03:36 PM, Michail Vourlakos wrote:
As a plasma user I am a [Multiple Activities and 1 VD] user so I am get used
in that workflow and I wouldnt like to miss it :)
It seems to me that if we merge the features of both, it should be
possible to not lose anything for people who use
2018-07-12 17:43 GMT+03:00 Marco Martin :
> On Wed, Jul 4, 2018 at 9:28 PM Michail Vourlakos
> wrote:
> >
> > unfortunately not David, family matters prevent me from attending
>
> That's too bad, I'm still looking forward to some day, somehow making
> an in person meeting with you and other
> And there would be quite a nice opportunity for a nice pr campaign.
IF (and that is a big "if") we can create a new feature (just don't
call it "Virtual Activated Desktops" :D) that will merge activities
and VDs in a sane way, which would not be overly limiting, I would be
more than happy.
It
> Personally i always used virtual desktops exactly for that, as "activities",
> even before activities were a thing, "i need a new physical space to stuff
> new windows" is not an use case that ever occurred to me in any way
> noted that there are people which see virtual desktops like that..
On Wed, Jul 4, 2018 at 9:28 PM Michail Vourlakos wrote:
>
> unfortunately not David, family matters prevent me from attending
That's too bad, I'm still looking forward to some day, somehow making
an in person meeting with you and other lattedock people happen..
In the meantime, can you provide
On Wed, Jul 4, 2018 at 9:12 PM Nate Graham wrote:
> very different things: Virtual Desktops are for window organization
> within the current set of tasks, and Activities are for higher-level
> task and context switching.
which is.. a pretty blurry concept, it asks the question "which of the
two
On Tue, Jul 3, 2018 at 8:03 PM Ivan Čukić wrote:
> Just read the phab discussion. If I misunderstood the situation, please
> correct me.
>
> Wondering where the original discussion happened where 'we' decided to
> merge two orthogonal concepts into one. Can you point me to the relevant
> thread
On Tue, Jul 3, 2018 at 5:36 PM Michail Vourlakos wrote:
> Example: I am working on my current actitivity and I am writing a note in a
> plasma widget. I am creating a new Activity, should that Activity look the
> same as the previous one and if I change the note in the first should it look
>
David> Are you (Michail and Ivan) at Akademy?
Not this year, I'm taking a rest from socializing ;)
Nate> very different things: Virtual Desktops are for window organization
Nate> within the current set of tasks, and Activities are for higher-level
This is exactly my view of VD vs activities.
2018-07-04 22:01 GMT+03:00 David Edmundson :
>
> Are you (Michail and Ivan) at Akademy?
>
>
unfortunately not David, family matters prevent me from attending
I used to be of the opinion that having both Activities and Virtual
Desktops was "too confusing" to users. I've changed my opinion recently,
because I finally came to understand how they're designed to be used for
very different things: Virtual Desktops are for window organization
within the
Are you (Michail and Ivan) at Akademy?
David
2018-07-03 22:19 GMT+03:00 Eike Hein :
>
> This is the relevant thread :-)
>
>
There are some technical decisions and commit reviews referencing MERGE and
this is why I proposed this thread.
Proposed technical decisions:
1. Virtual Desktops Ids from integers will be QVariants possibly strings I
> I think this is a fair recap so far:
The recap sounds great.
> When Martin and I started talking about the
> Wayland protocol, we
> were keen to do work that would reusable
> for either use case. This
I especially like this part. As I said, merging the implementation (at least to
some
On 07/04/2018 03:00 AM, Ivan Čukić wrote:
> Wondering where the original discussion happened where 'we' decided to
> merge two orthogonal concepts into one. Can you point me to the relevant
> thread on plasma-devel?
This is the relevant thread :-)
I think this is a fair recap so far:
* When
for Virtual Desktops and Activities future A discussion started by me at: https://phabricator.kde.org/D13745 about concerns related to future Activities / Virtual Desktops merge (I will call it MERGE in the future). As proposed the discussion can be moved here.In my opinion having a concrete draft how
A discussion started by me at: https://phabricator.kde.org/D13745 about
concerns related to future Activities / Virtual Desktops merge (I will call
it MERGE in the future). As proposed the discussion can be moved here.
In my opinion having a concrete draft how things are going to work from a
user
45 matches
Mail list logo
