Hi, everyone,
The status line is pretty crowded, as you know, so how about making it configurable? Something like:
line: %l / %n\t col: %c\t sel: %s ...
I can write it, if you think that's a good idea.
On Wed, 23 Jun 2010 19:31:03 +0300 Dimitar Zhekov dimitar.zhekov@gmail.com wrote:
Hi, everyone,
The status line is pretty crowded, as you know, so how about making it configurable? Something like:
line: %l / %n\t col: %c\t sel: %s ...
I can write it, if you think that's a good idea.
I don't think it's worth it.
Regards, Nick
On Wed, 23 Jun 2010 17:58:11 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
On Wed, 23 Jun 2010 19:31:03 +0300 Dimitar Zhekov dimitar.zhekov@gmail.com wrote:
Hi, everyone,
The status line is pretty crowded, as you know, so how about making it configurable? Something like:
line: %l / %n\t col: %c\t sel: %s ...
I can write it, if you think that's a good idea.
I don't think it's worth it.
You're right about the status line being crowded though.
I think we shouldn't show the line count, but maybe show it in the goto line dialog instead and maybe as a tooltip to the goto line toolbar field.
Also, I don't think we need the INS / OVR indication - the cursor changes from vertical to an underline and this is probably clear enough.
Does this sound OK?
Regards, Nick
On Fri, 25 Jun 2010 12:37:52 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
Dimitar Zhekov dimitar.zhekov@gmail.com wrote:
Hi, everyone,
The status line is pretty crowded, as you know, so how about making it configurable? Something like:
line: %l / %n\t col: %c\t sel: %s ...
I can write it, if you think that's a good idea.
I don't think it's worth it.
You're right about the status line being crowded though.
I think we shouldn't show the line count, but maybe show it in the goto line dialog instead and maybe as a tooltip to the goto line toolbar field.
Also, I don't think we need the INS / OVR indication - the cursor changes from vertical to an underline and this is probably clear enough.
It can also show RO for readonly files. Which also is indicated by the green tab color, but we shoudn't rely on that for accesibility reasons...
Does this sound OK?
Personally I'd also remove the MOD indicator, the red tab color is enough _for me_... well, that's why I siggested configurable.
On Fri, 25 Jun 2010 19:55:43 +0300 Dimitar Zhekov dimitar.zhekov@gmail.com wrote:
On Fri, 25 Jun 2010 12:37:52 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
Also, I don't think we need the INS / OVR indication - the cursor changes from vertical to an underline and this is probably clear enough.
It can also show RO for readonly files. Which also is indicated by the green tab color, but we shoudn't rely on that for accesibility reasons...
In that space, but we can just save the space unless it's read-only.
Personally I'd also remove the MOD indicator, the red tab color is enough _for me_... well, that's why I siggested configurable.
As RO, it's needed when there's no tabs.
Regards, Nick
On 26 June 2010 02:59, Nick Treleaven nick.treleaven@btinternet.com wrote:
On Fri, 25 Jun 2010 19:55:43 +0300 Dimitar Zhekov dimitar.zhekov@gmail.com wrote:
On Fri, 25 Jun 2010 12:37:52 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
Also, I don't think we need the INS / OVR indication - the cursor changes from vertical to an underline and this is probably clear enough.
It can also show RO for readonly files. Which also is indicated by the green tab color, but we shoudn't rely on that for accesibility reasons...
In that space, but we can just save the space unless it's read-only.
Personally I'd also remove the MOD indicator, the red tab color is enough _for me_... well, that's why I siggested configurable.
As RO, it's needed when there's no tabs.
And for the 10-20% of males with red/green colour deficiency.
Regards, Nick _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
On Wed, 23 Jun 2010 17:58:11 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
On Wed, 23 Jun 2010 19:31:03 +0300 Dimitar Zhekov dimitar.zhekov@gmail.com wrote:
Hi, everyone,
The status line is pretty crowded, as you know, so how about making it configurable? Something like:
line: %l / %n\t col: %c\t sel: %s ...
I can write it, if you think that's a good idea.
I don't think it's worth it.
OK, having thought more about it I think it could be configurable as a hidden pref. That way we can hide any less generally useful things like line count by default.
So I'd accept a clean patch to do this.
Regards, Nick
On Sat, Jun 26, 2010 at 18:27, Nick Treleaven nick.treleaven@btinternet.com wrote:
On Wed, 23 Jun 2010 17:58:11 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
On Wed, 23 Jun 2010 19:31:03 +0300 Dimitar Zhekov dimitar.zhekov@gmail.com wrote:
Hi, everyone,
The status line is pretty crowded, as you know, so how about making it configurable? Something like:
line: %l / %n\t col: %c\t sel: %s ...
I can write it, if you think that's a good idea.
I don't think it's worth it.
OK, having thought more about it I think it could be configurable as a hidden pref. That way we can hide any less generally useful things like line count by default.
Personally I find the total number of lines quite useful - it tells you quickly how big the file is. Also the space "wasted" by its presence is relatively small because it shares the caption with the current line number. For me the least useful information is the INS/OVR indication because this is already indicated by the cursor. But in general I find the current state of the status bar OK.
Jiri
So I'd accept a clean patch to do this.
Regards, Nick _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
On Sat, 26 Jun 2010 17:27:37 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
OK, having thought more about it I think it could be configurable as a hidden pref. That way we can hide any less generally useful things like line count by default.
So I'd accept a clean patch to do this.
OK then, I'll write one.
Hi,
This is the $subject.
To preserve the status bar speed, I used only g_string_append(), as in the current code, instead of utils_string_replace_all(). There are more _append calls, but that can't be avoided.
The format speifiers are:
%l current line %c current column %n number of lines %s selected chars %w write mode: "RO ", "INS" or "OVR" %t tab mode: "TAB", "SP" or "T/S" %m eoln mode %e encoding %b byte order mark: "(with BOM)" or nothing %f file type %* "MOD" or nothing %a active scope %_ separator: 6 spaces %o current column, 1-based (alternative of %c) %r readonly mode: "RO " or nothing (alternative of %w)
Percent and any other character = that character (including %% = % and %<zero> = nothing).
The default status line is:
"line: %l / %n\t col: %c\t sel: %s\t %w%_%t%_mode: %m%_encoding: %e %_filetype: %f%_%*%_scope: %a"
I was thinking about %1..9 to set the number of spaces for %_, but that seems too much...
Hi,
Here is a slightly newer version of the $subject patch.
Support for %_ has been removed, it doesn't make sense if the number of spaces can not be set, and only makes the text harder to read.
The default status line text is _("line: %l / %n\t col: %c ..."), not _(GEANY_DEFAULT_STATUSBAR_TEMPLATE), for easier i18n.
On Sat, 26 Jun 2010 20:31:12 +0200% Jiří Techet techet@gmail.com wrote:
On Sat, Jun 26, 2010 at 18:27, Nick Treleaven nick.treleaven@btinternet.com wrote:
On Wed, 23 Jun 2010 17:58:11 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
On Wed, 23 Jun 2010 19:31:03 +0300 Dimitar Zhekov dimitar.zhekov@gmail.com wrote:
Hi, everyone,
The status line is pretty crowded, as you know, so how about making it configurable? Something like:
line: %l / %n\t col: %c\t sel: %s ...
I can write it, if you think that's a good idea.
I don't think it's worth it.
OK, having thought more about it I think it could be configurable as a hidden pref. That way we can hide any less generally useful things like line count by default.
Personally I find the total number of lines quite useful - it tells you quickly how big the file is. Also the space "wasted" by its presence is relatively small because it shares the caption with the current line number. For me the least useful information is the INS/OVR indication because this is already indicated by the cursor. But in general I find the current state of the status bar OK.
Jiri
I second that. From my opinion: - number of lines indication may be useful; - INS/OVR indication is probably excessive; - current state is ok, it's not so overcrowded.
Best regards, Eugene.
On Sun, 27 Jun 2010 15:20:24 +0300 Dimitar Zhekov dimitar.zhekov@gmail.com wrote:
Hi,
Here is a slightly newer version of the $subject patch.
Support for %_ has been removed, it doesn't make sense if the number of spaces can not be set, and only makes the text harder to read.
The default status line text is _("line: %l / %n\t col: %c ..."), not _(GEANY_DEFAULT_STATUSBAR_TEMPLATE), for easier i18n.
To preserve the status bar speed, I used only g_string_append(), as in the current code, instead of utils_string_replace_all(). There are more _append calls, but that can't be avoided.
Not sure that's necessary, I think it would be cleaner using utils_string_replace_first().
Also you need to preserve all comments as they are for the translators.
Regards, Nick
On Mon, 28 Jun 2010 13:13:11 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
On Sun, 27 Jun 2010 15:20:24 +0300 Dimitar Zhekov dimitar.zhekov@gmail.com wrote:
Hi,
Here is a slightly newer version of the $subject patch.
Support for %_ has been removed, it doesn't make sense if the number of spaces can not be set, and only makes the text harder to read.
OK.
The default status line text is _("line: %l / %n\t col: %c ..."), not _(GEANY_DEFAULT_STATUSBAR_TEMPLATE), for easier i18n.
Yes, I'm not sure that the former would work for translatation.
To preserve the status bar speed, I used only g_string_append(), as in the current code, instead of utils_string_replace_all(). There are more _append calls, but that can't be avoided.
Not sure that's necessary, I think it would be cleaner using utils_string_replace_first().
Your approach is probably good, but I'll move the switch loop into a separate function.
Also you need to preserve all comments as they are for the translators.
Here I noticed the RO comment got lost, I'll add it again.
Regards, Nick
(The list seems to not be sending mails ATM, so sorry if I missed any reply.)
On Tue, 29 Jun 2010 11:42:01 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
To preserve the status bar speed, I used only g_string_append(), as in the current code, instead of utils_string_replace_all(). There are more _append calls, but that can't be avoided.
Not sure that's necessary, I think it would be cleaner using utils_string_replace_first().
Your approach is probably good, but I'll move the switch loop into a separate function.
Also you need to preserve all comments as they are for the translators.
Here I noticed the RO comment got lost, I'll add it again.
Applied now with some changes in SVN, thanks.
Restored translator comments. I moved MOD and added spaces after it (like existing behaviour). I combined encoding and bom (like existing behaviour). I changed some format specifiers (we can use capitals too). For modularity, I used the load-settings signal to read the setting.
Regards, Nick
On Sun, 27 Jun 2010 21:41:17 +0400 Eugene Arshinov earshinov@gmail.com wrote:
Personally I find the total number of lines quite useful - it tells you quickly how big the file is. Also the space "wasted" by its presence is relatively small because it shares the caption with the current line number. For me the least useful information is the INS/OVR indication because this is already indicated by the cursor. But in general I find the current state of the status bar OK.
Jiri
I second that. From my opinion:
- number of lines indication may be useful;
Ok, I suppose so.
- INS/OVR indication is probably excessive;
I decided to keep it by default, partly as gedit does this but also you might be more likely to notice quicker if you accidentally hit the 'insert' key.
- current state is ok, it's not so overcrowded.
OK, no changes made to default. It's now configurable so just showing RO instead of INS/OVR is possible, with space saving when not RO.
Thanks for the comments.
Regards, Nick