Mick Semb Wever wrote:
>I see a number of solutions:
> * 3 columns is immediately possible by merging Date
& Author.
> * Duplicate text removed between Actions and Reason (as
you have done
>already).
> * Instead of merging Date & Author into one column
merging it into a
>header row (like you have done already).
So we aren't too far away from each other.
>problem with this is i feel it
>adds an extra line to the page for every changeset.
> * Always putting the body of the comment changed/added
into the Reason
>column. Most likely then the Actions column could be
much narrower since
>all the long-text text would be appearing under the
Reason column.
>
Option-changes don't require the whole with of the screen.
Changes of text-attributes or long-text-attributes will
profit from it.
Comments/Reasons will profit too.
How about still aligning the three sections(timestamp,
actions, comments) vertically,
but making a clear visual distinction between the sections
and especially highlighting user/timestamp and the
attribute-names in each action.
The sections for actions and comments are only displayed if
there is something to display.
...ok, I think I will have to mock up a sample-history. ;)
>> Btw. all the popular Trackers I have used or tested
(like Bugzilla,
>> Jira, Mantis, Trac,FogBugz,...) have some kind of
one-column history. I
>> don’t think they're all wrong. (And I don’t
think this is a good unique
>> selling point for Scarab.)
>
>Sorry but i just don't buy this sort of rationale:
>"We should do it that way because they did it that
way"
Right.
I should have written: I used/use some of the other trackers
and I found/find their one-column-history quite convenient.
Ronny
|