Summary of NWI -- the page

Maciej Pilichowski bluedzins at wp.pl
Wed May 20 14:38:18 CEST 2009


On Tuesday 19 May 2009 21:40:42 Matthew Woehlke wrote:

> > So personally I would remove such feature, but on the other hand
> > can we force users to use NWI? I think not. So auto-collapsing
> > the same entries should be possible.
> > ( ) collapse SAI only
> > ( ) collapse similar
>
> Okay.

Adding this right away :-)

> I've been sort-of assuming we need to be able to name containers
> (i.e. user-assigned caption). 

Yes, but this is not required, right?

> Maybe there should be a class also;

Set by user?

> if non-empty, containers with the same class can group. Otherwise
> containers don't group. (And perhaps auto-assign class to certain
> containers; for example any TAI created by app request. As a
> specific example, the TAI you get from ctrl-t in konq, so TAI
> containers of konq's would generally get grouped.)

Ok.

> >> Let me try again. Do we need a context menu step to say "done
> >> selecting windows", or can we do this:
> >>
> >> - decide to create a {T,F,G}AI container
> >> - select windows mode started by previous action
> >> - select windows as described
> >> - click 'okay' button in corner of screen or hit enter*
> >> - container is created with windows
> >>
> >> [stuff about creating containers]
> >
> > Nice, better! I change the summary accordingly.
>
> Thanks. I made one further change to the menu text and added a
> mention of picking the container type.
>
> Is putting it in the "confirm" dialog okay? It should be the same
> number of clicks (maybe more mousing, though) and lets you change
> your mind any time before confirming.

YES! I like it very much. Well, next to the choices there could be 
nice icons (self-explanatory) with illustration what FAI and so on 
means.

Cheers,


More information about the Kde-usability-devel mailing list