[krita] [Bug 344659] New: The workspace switcher does not show what workspace is currently active.

[s***@gmail.com]

https://bugs.kde.org/show_bug.cgi?id=344659

Bug ID: 344659
Summary: The workspace switcher does not show what workspace is
currently active.
Product: krita
Version: 2.9
Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: NOR
Component: usability
Assignee: krita-bugs-***@kde.org
Reporter: ***@gmail.com

I'm refering as the workspace switcher,the button from the top right(to the
left are the mirror vertical and horizontal buttons) on the brushes and stuff
toolbar.
There are 2 aspects here:
1.I created my own custom workspace,at program start on screen are my
dockes(witch i've selected),toolbars,but the workspace switcher does not
specifically tell what workspace is currently active(i know the name of it
because it's a custom one,but it should have some kind of visual flag so that i
know it is active).If i select my workspace then a blue bar appears over it and
remains there until program close.If i close and restart krita,that blue bar is
gone,it get's confusing because,unless you created your own workspace,you do
not know(unless you select it) what workspace is active.
2.I like shrinking my tools bar from 2 rows to 1 row.If i do this then save my
custom workspace it's all ok.After closing and restarting krita,all my dockers
and toolbars are in their place,but my tool bar has 2 rows and not 1 row as i
wanted,i have to select that custom workspace(or resize evrey time to 1 row) so
that my tools bar has 1 row.
I think this bug may be similar(or it is an effect) from this one
https://bugs.kde.org/show_bug.cgi?id=314824

Reproducible: Always

Steps to Reproduce:
Aspect 1:
1.Create custom workspace
2.Save workspace
3.Close krita
4.Reopen krita
5.Create document(dosen't matter size or rezolution)
6.Check workspace switcher, and there is nothing there to tell witch workspace
is active
7.Select my custom workspace and now a blue bar appears on the selected
workspace witch indicates that it is active,but after program close and
restart,it dissapears

Aspect 2:
1.Create custom workspace(resize tools bar from 2 rows to 1 row)
2.Save custom workspace
3.Close krita
4.Reopen krita
5.Create document(dosen't matter size or rezolution)
6.All my dockes and toolbars are where they are supposed to be,but the tool bar
has 2 rows and not 1 as i wanted.I have to,either resize evrey time or select
my workspace evrey time so that the tools bar becomes 1 row.


Expected Results:
Aspect1:
After creating a new document,and checking the workspace switcher,there should
be a visual indicator that shows what workspace is currently
active(suggestions:you could preserve the blue bar over the active one or on
the right side of the workspace name the word "active" or "selected" may
appear,indicating the workspace in use)

Aspect2:
After saving the workspace,closing and restarting krita,the tools bar needs to
remain at 1 row.

I installed krita 2.9 from krita lime ppa with the command sudo apt-get install
krita-testing.
I don't know if this is an overlook or not(i apologize if i'm wrong),but on
krita.org,download section,GNU/Linux,at the moment of writing this bug
report,there are listed both commands:
sudo apt-get install krita
sudo apt-get install krita-testing
if sudo apt-get install krita is first,wouldn't this install krita from the
official repositories(not the recent version) first and then install 2.9?Maybe
the point of this to have the calligra libs installed,but i've used only
krita-testing and evreything seems ok,so what is the point of having install
krita alongisde install krita-testing?
I don't think sudo apt-get install krita should be there,only sudo apt-get
install krita-testing.

Another thing,i would suggest that on krita lime ppa,make a package called
krita-2.9(like there is one now called krita-2.8)(and separate packages for
bugfix releases like 2.9.1,2.9.2,2.9.3 and so on) separate from
krita-testing.At this point krita-2.9 and krita-testing packages are
identical,but by doing so,in my opinion,it separates the bleeding edge
version(krita-testing) from the stable version(krita-2.9.),and users will get
the sense that they are using a stable version and not a development
one,although it is true that krita-testing is quite stable.But,on the other
hand krita-testing changes with git so depending on what modifications where
made to the master branch it might not be considered,in some moments,a true
stable and workable version and users might get THE WRONG idea that krita is
not a proffesional,workable,stable program.
I'm using Kubuntu 14.04,so,before i end my bug report,i would like to suggest a
better maintenance of krita lime ppa(i don't know,for other distros,what are
the current equivalents for krita lime).For example there is a krita-2.8
package in krita lime,but now that krita-2.9 was released what is the point of
keeping that krita-2.8 package?It should be removed from the
repository.Another argument in favor is from krita lime description:"The Krita
Lime PPA is setup to provide *Buntu users with an always fresh version of
Krita, without the need to update the whole system",so keeping obsolete
packages in the repository is not an optimal solution.

[s***@gmail.com]

https://bugs.kde.org/show_bug.cgi?id=344659

--- Comment #1 from ***@gmail.com ---
I think i need to clarify some things.When i wanted to install krita2.9 i got
over to krita.org ,download section,gnu/linux,there i see those 2
commands,witch at first glance,may seem confusing one alonside the other:
sudo apt-get install krita
sudo apt-get install krita-testing
my first reaction was to copy pasted them so that i can gen krita up and
running asap,but then it struck me,how can it be install krita and after
install krita-testing,this cannot be right.With install krita i'm installing
from the official repositories and with install krita-testing,i'm installing
from krita-lime ppa,so basically what i'm doing is installing 2 version of
krita,one after the other?
My first thought was that ok,with install krita i'm installing the calligra
libs +other libs and with install krita-testing i'm updating to krita2.9.But it
still didn't feel right,so i thought again what might be happening.It is clear
that krita2.9 was launch on 25 Feb,and distro's need time to update their
repositories,but from my experience with Ubuntu and Kubuntu,only for a few
programs(like web browsers),the repositories are updated to the next
version,for the majority of programs in a *Buntu distro,the repositories are
updated with the next version of the distro.
So by putting install krita there,the developers where pointing the instalation
method from the official repositories,but krita-2.9 just got launched and who
knows how many distors will update/have updated the official repositories,until
the next distro release,and at this point in time installing krita-2.9 from
there may not be possible.Ok,what is the alternative?Installing from krita lime
ppa,the krita-testing package,so what is the utility of having install krita
there,at this point in time.
The point of what i'm trying to say is that,at this point in time, writing in
the downloads section
sudo apt-get install krita
sudo apt-get install krita-testing
is confusing and may be problematic,if,let's say you are an artist,you saw
krita-2.9 running on a windows machine(at your friend's PC),you liked it and
decided that you want to give it a try.In the same time,you heard from another
friend that krita was born on the Linux platform and later on was ported to
Windows,and although the Windows version is good,the Linux version may run
better.You are not experienced with Linux,but decide to give it a go,you ask
someone to install a *Buntu distro for you,go to the downloads section,gnu
linux,copy paste those 2 command,input you password,and something happens,you
don't understand what is happening,try to debug the problem but at the end you
didn't manage to install krita,you get frustrated and give up on using krita on
linux,all because of a confusion.
So my suggestion would the that on the website there are some clarifications:
Option 1: leave only apt-get install krita-testing,until the next cycle of
*Buntu distros(april is not that far away),and after that replace with apt-get
install krita
Option 2: On the website,have to sections:
a.Install krita form the official *Buntu repositories
Option3:On krita lime,create a specific krita-2.9 package,and advise to add the
ppa and install that package, sudo apt-get install krita-2.9, and leave it as
is,withought changing it after april passes.

[s***@gmail.com]

https://bugs.kde.org/show_bug.cgi?id=344659

--- Comment #2 from ***@gmail.com ---
I'm sorry i did not finish writing Options too,and i hit enter:
Option 2:
a.Install krita form the official *Buntu repositories
sudo apt-get install krita
Notice: keep in mind that krita 2.9 was recently launched and your official
distro repositories may not have been updated to 2.9,we belive that until the
end of april 2015 all official repositories will be updates,but until then we
advise to use option b. for installing krita 2.9:
b. Add Krita Lime ppa:
sudo add-apt-repository ppa:dimula73/krita
update your sistem:
sudo apt-get update
Install the awesome krita2.9:
sudo apt-get install krita-testing
Have fun painting

This is my clarification,thank you for your time,i apologize for not sticking
only to the bug report(i understand that a bug report is not the ideal place to
write about the website or krita lime),and hope it helped.

[s***@gmail.com]

https://bugs.kde.org/show_bug.cgi?id=344659

***@gmail.com changed:

What |Removed |Added
----------------------------------------------------------------------------
Summary|The workspace switcher does |The workspace switcher does
|not show what workspace is |not show what workspace is
|currently active. |currently active+website
| |and krita lime suggestions

[s***@gmail.com]

https://bugs.kde.org/show_bug.cgi?id=344659

--- Comment #3 from ***@gmail.com ---
I'm reformulating the notice from option 2,because part of it is wrong(i'm
sorry)
Notice: Krita 2.9 was launched on 25 Feb 2015,for that reason it is possible
that your official distro repositories may not have been updated to 2.9.
For *Buntu distros launched after April 2015,we belive that all the official
repositories will be updated,so we recommend using option a.
For *Buntu distros launched before April 2015(or for the bleeding edge version
of krita or if evreything else fails),please use option b.
(this notice should be placed after options a and b)

[mmolch]

https://bugs.kde.org/show_bug.cgi?id=344659

--- Comment #4 from mmolch <***@moritzmolch.de> ---
Created attachment 91399
--> https://bugs.kde.org/attachment.cgi?id=91399&action=edit
this patch sets the minimum size for docker titlebars to 0

[mmolch]

https://bugs.kde.org/show_bug.cgi?id=344659

mmolch <***@moritzmolch.de> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@moritzmolch.de

--- Comment #5 from mmolch <***@moritzmolch.de> ---
Thank you for reporting your problems.

Unfortunately your first issue is a little tricky to solve because krita's
current behaviour when starting up doesn't involve workspace presets at all. So
at least at the moment I don't think that this is easily fixable.

For the second issue, I attached a small patch that fixes the bug but I am not
sure whether it would be accepted upstream because it might be viewed as
slightly hackish (although in my humble opinion this this is the right thing to
do in this case)

Kind regards,
Moritz

[Boudewijn Rempt]

https://bugs.kde.org/show_bug.cgi?id=344659

Boudewijn Rempt <***@valdyas.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@valdyas.org

--- Comment #6 from Boudewijn Rempt <***@valdyas.org> ---
Yes, the thing is: Krita doesn't so much switch to a particular workspace that
then is the workspace krita shows: every 'workspace' is just a set of defaults,
and if you move a docker, or make it larger, then that creates a potential new
workspace you can save.

I remember looking into this a couple of years ago, but I didn't like any of
the easy solutions. On closing krita, the current state is remembered, not the
last selected workspace.

[Sven Langkamp]

https://bugs.kde.org/show_bug.cgi?id=344659

Sven Langkamp <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #7 from Sven Langkamp <***@gmail.com> ---
Well you could easily do the same that we do for presets where we just store
the name of the last activated one. There isn't much useful information gained
by knowing the the workspace though.

[mmolch]

https://bugs.kde.org/show_bug.cgi?id=344659

--- Comment #8 from mmolch <***@moritzmolch.de> ---
I think that the complete workspace chooser needs a complete overhaul in the
future. It just has so many flaws (you can't easily rename presets, you can
have multiple with the same name, they should be taggable, there should be a
resource filter, it should be possible to set workspaces as the startup and
fullscreen ones etc. etc.)
It's just something that has to be well thought of and worked on together with
the artists to get a pleasing and productive result. And unfortunately those
things need a long time to implement.

[Boudewijn Rempt via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344659

Boudewijn Rempt <***@valdyas.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX

--- Comment #9 from Boudewijn Rempt <***@valdyas.org> ---
True, but that is out of scope for a bug report. It's for sure good to think
about improving the workspaces system -- they should, for instance, also be
available in the menu, but that needs to start with discussions on the forum,
then an interaction design, then a mockup, then implementation.