Issue #SCB1454 () making the Scarab screen layout more modern
Hussayn Dabbous <[email protected]> Tue, 13 Jan 2009 00:31:00 +0100 (CET)
| Newsgroups | gmane.comp.java.scarab.issues |
|---|---|
| Message-ID | <[email protected]> |
Activity report on *Enhancement SCB1454 - making the Scarab screen layout more modern* Scarab Link: http://www.solitone.org/scarab/issues/id/SCB1454 Module: Scarab Activity generated by Hussayn Dabbous ([email protected]) at 01/13/2009 00:07 *Reasons for the changes* *Comments* - By Hussayn Dabbous - 01/13/2009 00:21 --- "We are currently working on a major redesign for Scarab.\\ During our investigations we stumbled over a nasty pitfall\\ with the idea about \\ "__The issueid / created / last modified can easily be put on one line__" \\ This idea has been implemented in Scarab for a while now, but...\\ Unluckily the info is only rendered into 1 single line, if the user\\ decides to use a window width of 1350 px or above. So indeed\\ there is only a reduction of scroll space when the user widens up\\ his/her screen significantly. If the user decides to hide the left navigatiopn bar, the minimum \\ needed width goes down to about 1200, which IMHO is still too\\ wide in general. I think, Scarab should be optimised for window\\ width of less then 900 and there are 3 very practical reason for this: # i guess, many (if not most) users will still work with screens of\\ width 1024. # From experiments about readability of written text, we got a rule\\ of thumb, which tells "The number of words within a line of written\\ text shall average to about 11 words". This is true for a column\\ width of about 600 with a reasonable font size. # We found by comparing user reactions: scrolling is\\ tolerated more than too long text lines. We are currently doing a redesign of the Scarab interface\\ with usability AND readability in our mind. We aim for not\\ waisting too much space, but aim for an ergonomic visual\\ interface.\\ BTW: I have forced my comment to obey the "11-words" rule\\ and you can immediately test the change of readability when\\ you widen up your Scarab window as much as you can. ;-)" - By Hussayn Dabbous - 01/13/2009 00:07 --- "We are currently working on a major redesign for Scarab.\\ During our investigations we stumbled over a nasty pitfall\\ with the idea about \\ "__The issueid / created / last modified can easily be put on one line__" \\ This idea has been implemented in Scarab for a while now, but...\\ Unluckily the info is only rendered into 1 single line, if the user\\ decides to use a window width of 1350 px or above. So indeed\\ there is only a reduction of scroll space when the user widens up\\ his/her screen significantly. If the user decides to hide the left navigatiopn bar, the minimum \\ needed width goes down to about 1200, which IMHO is still too\\ wide in general. I think, Scarab should be optimised for window\\ width of less then 900 and there are 3 very practical reason for this: # i guess, many (if not most) users will still work with screens of\\ width 1024. # From experiments about readability of written text, we got a rule\\ of thumb, which tells "The number of words within a line of written\\ text shall average to about 11 words". This is true for a column\\ width of about 600 with a reasonable font size. # We found by comparing user reactions: scrolling is\\ tolerated more than too long text lines. We are currently doing a redesign of the Scarab interface\\ with usability AND readability in our mind. We aim for not\\ waisting too much space, but aim for an ergonomic visual\\ interface.\\ BTW: I have forced my comment to obey the "11-words" rule\\ and you can immediately test the change of readability when\\ you widen up your Scarab window as much as you can. ;-)" - By Hussayn Dabbous - 01/13/2009 00:19 --- "We are currently working on a major redesign for Scarab.\\ During our investigations we stumbled over a nasty pitfall\\ with the idea about \\ "__The issueid / created / last modified can easily be put on one line__" \\ This idea has been implemented in Scarab for a while now, but...\\ Unluckily the info is only rendered into 1 single line, if the user\\ decides to use a window width of 1350 px or above. So indeed\\ there is only a reduction of scroll space when the user widens up\\ his/her screen significantly. If the user decides to hide the left navigatiopn bar, the minimum \\ needed width goes down to about 1200, which IMHO is still too\\ wide in general. I think, Scarab should be optimised for window\\ width of less then 900 and there are 3 very practical reason for this: # i guess, many (if not most) users will still work with screens of\\ width 1024. # From experiments about readability of written text, we got a rule\\ of thumb, which tells "The number of words within a line of written\\ text shall average to about 11 words". This is true for a column\\ width of about 600 with a reasonable font size. # We found by comparing user reactions: scrolling is\\ tolerated more than too long text lines. We are currently doing a redesign of the Scarab interface\\ with usability AND readability in our mind. We aim for not\\ waisting too much space, but aim for an ergonomic visual\\ interface.\\ BTW: I have forced my comment to obey the "11-words" rule\\ and you can immediately test the change of readability when\\ you widen up your Scarab window as much as you can. ;-)" - By Hussayn Dabbous - 01/13/2009 00:17 --- "We are currently working on a major redesign for Scarab.\\ During our investigations we stumbled over a nasty pitfall\\ with the idea about \\ "__The issueid / created / last modified can easily be put on one line__" \\ This idea has been implemented in Scarab for a while now, but...\\ Unluckily the info is only rendered into 1 single line, if the user\\ decides to use a window width of 1350 px or above. So indeed\\ there is only a reduction of scroll space when the user widens up\\ his/her screen significantly. If the user decides to hide the left navigatiopn bar, the minimum \\ needed width goes down to about 1200, which IMHO is still too\\ wide in general. I think, Scarab should be optimised for window\\ width of less then 900 and there are 3 very practical reason for this: # i guess, many (if not most) users will still work with screens of\\ width 1024. # From experiments about readability of written text, we got a rule\\ of thumb, which tells "The number of words within a line of written\\ text shall average to about 11 words". This is true for a column\\ width of about 600 with a reasonable font size. # We found by comparing user reactions: scrolling is\\ tolerated more than too long text lines. We are currently doing a redesign of the Scarab interface\\ with usability AND readability in our mind. We aim for not\\ waisting too much space, but aim for an ergonomic visual\\ interface.\\ BTW: I have forced my comment to obey the "11-words" rule\\ and you can immediately test the change of readability when\\ you widen up your Scarab window as much as you can. ;-)" - By Hussayn Dabbous - 01/13/2009 00:08 --- "We are currently working on a major redesign for Scarab.\\ During our investigations we stumbled over a nasty pitfall\\ with the idea about \\ "__The issueid / created / last modified can easily be put on one line__" \\ This idea has been implemented in Scarab for a while now, but...\\ Unluckily the info is only rendered into 1 single line, if the user\\ decides to use a window width of 1350 px or above. So indeed\\ there is only a reduction of scroll space when the user widens up\\ his/her screen significantly. If the user decides to hide the left navigatiopn bar, the minimum \\ needed width goes down to about 1200, which IMHO is still too\\ wide in general. I think, Scarab should be optimised for window\\ width of less then 900 and there are 3 very practical reason for this: # i guess, many (if not most) users will still work with screens of\\ width 1024. # From experiments about readability of written text, we got a rule\\ of thumb, which tells "The number of words within a line of written\\ text shall average to about 11 words". This is true for a column\\ width of about 600 with a reasonable font size. # We found by comparing user reactions: scrolling is\\ tolerated more than too long text lines. We are currently doing a redesign of the Scarab interface\\ with usability AND readability in our mind. We aim for not\\ waisting too much space, but aim for an ergonomic visual\\ interface.\\ BTW: I have forced my comment to obey the "11-words" rule\\ and you can immediately test the change of readability when\\ you widen up your Scarab window as much as you can. ;-)" - By Hussayn Dabbous - 01/13/2009 00:25 --- "We are currently working on a major redesign for Scarab.\\ During our investigations we stumbled over a nasty pitfall\\ with the idea about \\ "__The issueid / created / last modified can easily be put on one line__" \\ This idea has been implemented in Scarab for a while now, but...\\ Unluckily the info is only rendered into 1 single line, if the user\\ decides to use a window width of 1350 px or above. So indeed\\ there is only a reduction of scroll space when the user widens up\\ his/her screen significantly. If the user decides to hide the left navigatiopn bar, the minimum \\ needed width goes down to about 1200, which IMHO is still too\\ wide in general. I think, Scarab should be optimised for window\\ width of less then 900 and there are 3 very practical reason for this: # i guess, many (if not most) users will still work with screens of\\ width 1024. # From experiments about readability of written text, we got a rule\\ of thumb, which tells "The number of words within a line of written\\ text shall average to about 11 words". This is true for a column\\ width of about 600 with a reasonable font size. # We found by comparing user reactions: scrolling is\\ tolerated more than too long text lines. We are currently doing a redesign of the Scarab interface\\ with usability AND readability in our mind. We aim for not\\ waisting too much space, but aim for an ergonomic visual\\ interface.\\ BTW: I have forced my comment to obey the "11-words" rule\\ and you can immediately test the change of readability when\\ you widen up your Scarab window as much as you can. ;-)" - By Hussayn Dabbous - 01/13/2009 00:12 --- "We are currently working on a major redesign for Scarab.\\ During our investigations we stumbled over a nasty pitfall\\ with the idea about \\ "__The issueid / created / last modified can easily be put on one line__" \\ This idea has been implemented in Scarab for a while now, but...\\ Unluckily the info is only rendered into 1 single line, if the user\\ decides to use a window width of 1350 px or above. So indeed\\ there is only a reduction of scroll space when the user widens up\\ his/her screen significantly. If the user decides to hide the left navigatiopn bar, the minimum \\ needed width goes down to about 1200, which IMHO is still too\\ wide in general. I think, Scarab should be optimised for window\\ width of less then 900 and there are 3 very practical reason for this: # i guess, many (if not most) users will still work with screens of\\ width 1024. # From experiments about readability of written text, we got a rule\\ of thumb, which tells "The number of words within a line of written\\ text shall average to about 11 words". This is true for a column\\ width of about 600 with a reasonable font size. # We found by comparing user reactions: scrolling is\\ tolerated more than too long text lines. We are currently doing a redesign of the Scarab interface\\ with usability AND readability in our mind. We aim for not\\ waisting too much space, but aim for an ergonomic visual\\ interface.\\ BTW: I have forced my comment to obey the "11-words" rule\\ and you can immediately test the change of readability when\\ you widen up your Scarab window as much as you can. ;-)" - By Hussayn Dabbous - 01/13/2009 00:17 --- "We are currently working on a major redesign for Scarab.\\ During our investigations we stumbled over a nasty pitfall\\ with the idea about \\ "__The issueid / created / last modified can easily be put on one line__" \\ This idea has been implemented in Scarab for a while now, but...\\ Unluckily the info is only rendered into 1 single line, if the user\\ decides to use a window width of 1350 px or above. So indeed\\ there is only a reduction of scroll space when the user widens up\\ his/her screen significantly. If the user decides to hide the left navigatiopn bar, the minimum \\ needed width goes down to about 1200, which IMHO is still too\\ wide in general. I think, Scarab should be optimised for window\\ width of less then 900 and there are 3 very practical reason for this: # i guess, many (if not most) users will still work with screens of\\ width 1024. # From experiments about readability of written text, we got a rule\\ of thumb, which tells "The number of words within a line of written\\ text shall average to about 11 words". This is true for a column\\ width of about 600 with a reasonable font size. # We found by comparing user reactions: scrolling is\\ tolerated more than too long text lines. We are currently doing a redesign of the Scarab interface\\ with usability AND readability in our mind. We aim for not\\ waisting too much space, but aim for an ergonomic visual\\ interface.\\ BTW: I have forced my comment to obey the "11-words" rule\\ and you can immediately test the change of readability when\\ you widen up your Scarab window as much as you can. ;-)" - By Hussayn Dabbous - 01/13/2009 00:22 --- "We are currently working on a major redesign for Scarab.\\ During our investigations we stumbled over a nasty pitfall\\ with the idea about \\ "__The issueid / created / last modified can easily be put on one line__" \\ This idea has been implemented in Scarab for a while now, but...\\ Unluckily the info is only rendered into 1 single line, if the user\\ decides to use a window width of 1350 px or above. So indeed\\ there is only a reduction of scroll space when the user widens up\\ his/her screen significantly. If the user decides to hide the left navigatiopn bar, the minimum \\ needed width goes down to about 1200, which IMHO is still too\\ wide in general. I think, Scarab should be optimised for window\\ width of less then 900 and there are 3 very practical reason for this: # i guess, many (if not most) users will still work with screens of\\ width 1024. # From experiments about readability of written text, we got a rule\\ of thumb, which tells "The number of words within a line of written\\ text shall average to about 11 words". This is true for a column\\ width of about 600 with a reasonable font size. # We found by comparing user reactions: scrolling is\\ tolerated more than too long text lines. We are currently doing a redesign of the Scarab interface\\ with usability AND readability in our mind. We aim for not\\ waisting too much space, but aim for an ergonomic visual\\ interface.\\ BTW: I have forced my comment to obey the "11-words" rule\\ and you can immediately test the change of readability when\\ you widen up your Scarab window as much as you can. ;-)" ------------------------------------------------------ http://scarab.tigris.org/ds/viewMessage.do?dsForumId=458&dsMessageId=1020467 To unsubscribe from this discussion, e-mail: [[email protected]].