You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Joachim Dreimann <jo...@wandisco.com> on 2013/03/18 19:06:11 UTC
#471: Merge activity feed + change history
I've raised ticket #471 with ideas relating to some major changes on the
ticket page, and I'd like to know what you guys think.
https://issues.apache.org/bloodhound/ticket/471
We've had many discussions about how to improve the ticket page on the
> mailing list, and I've attached a suggestions of how this could be done.
>
In essence, I propose we merge the Activity and Change History
> sections. I thought long about whether this should be done in the
> place of the current Change History or the current Activity feed, and
> settled on the latter.
>
Mockup below:
https://issues.apache.org/bloodhound/attachment/ticket/471/bh%20comments%20ticket%20without%20overlays.png
>
Comments and events have different styles to make it easier to
> differentiate between them and show the importance of comments.
>
The following highlights some key changes:
>
https://issues.apache.org/bloodhound/attachment/ticket/471/bh%20comments%20ticket%20with%20overlays.png
>
>From top to bottom this highlights:
> - Ticket changes and comments would have different styles, but when
> changes are associated with comments, this would not be lost (yellow
> highlight on hover).
> - On hover more information is also shown, such as the date/time and
> edit/reply links.
> - Subversion commit messages show up as comments
> - Long code snippets and big images are shown in an overlay
What do you all think?
--
Joe Dreimann
UX Designer | WANdisco <http://www.wandisco.com/>
Re: #471: Merge activity feed + change history
Posted by Olemis Lang <ol...@gmail.com>.
On 3/19/13, Joachim Dreimann <jo...@wandisco.com> wrote:
> On 19 March 2013 16:42, Gary Martin <ga...@wandisco.com> wrote:
[...]
>>
>> That is fair comment.. it might not be great for everyone. One aspect of
>> that is that if we make it switchable we are likely to have the new
>> comment
>> at the latest comment end. I think that is what Joe intends with the
>> buttons above the comment input in the mockup.
>>
>
> Yes in the mockup there's a switch above the comment box to switch to
> oldest first, which would reverse the arrow direction and place the comment
> box at the bottom.
sorry u r right . my mistake . I didn't notice .
> On 'oldest first' maybe also a link to jump to the
> comment box?
>
+
[...]
>>
>> As for the threaded view, perhaps we can add that later if there is
>> enough
>> demand.
>>
>
> I'd agree. I think the threaded view don't fit Bloodhound's purpose very
> well, Jeff Atwood wrote a good argument along those lines:
> http://www.codinghorror.com/blog/2012/12/web-discussions-flat-by-design.html
>
interesting .
/me reading
> If there's enough demand we can add it back in anyway.
>
> I would argue that the "Comments only" option isn't as needed with the new
> design and that we should add it back in (or do something smarter to reduce
> the noise) when there's enough demand.
>
Ok. Overall I like it .
--
Regards,
Olemis.
Re: #471: Merge activity feed + change history
Posted by Joachim Dreimann <jo...@wandisco.com>.
On 19 March 2013 16:42, Gary Martin <ga...@wandisco.com> wrote:
> On 19/03/13 16:18, Olemis Lang wrote:
>
>> On 3/19/13, Olemis Lang <ol...@gmail.com> wrote:
>>
>>> On 3/18/13, Joachim Dreimann <joachim.dreimann@wandisco.com**> wrote:
>>>
>>>> I've raised ticket #471 with ideas relating to some major changes on
>>>> the
>>>> ticket page, and I'd like to know what you guys think.
>>>> https://issues.apache.org/**bloodhound/ticket/471<https://issues.apache.org/bloodhound/ticket/471>
>>>>
>>>> :)
>>>
>>> In essence, I propose we merge the Activity and Change History
>>>>>
>>>> I forgot to mention something important , at least to me . Top posting
>> is annoying . It's so hard to follow that causes me headaches . May we
>> still stick to the selectors «Oldest first» «Newest first» «Comments
>> only» and «Threaded» ? Timeline arrow might be updated accordingly ,
>> but that's maybe just a matter of toggling css classes ...
>>
>> [...]
>>
>>
> That is fair comment.. it might not be great for everyone. One aspect of
> that is that if we make it switchable we are likely to have the new comment
> at the latest comment end. I think that is what Joe intends with the
> buttons above the comment input in the mockup.
>
Yes in the mockup there's a switch above the comment box to switch to
oldest first, which would reverse the arrow direction and place the comment
box at the bottom. On 'oldest first' maybe also a link to jump to the
comment box?
>
> We should also make sure that on the ticket page we are showing all
> changes (not just the last n days) if we are continuing to use the widget
> in that position.
>
> As for the threaded view, perhaps we can add that later if there is enough
> demand.
>
I'd agree. I think the threaded view don't fit Bloodhound's purpose very
well, Jeff Atwood wrote a good argument along those lines:
http://www.codinghorror.com/blog/2012/12/web-discussions-flat-by-design.html
If there's enough demand we can add it back in anyway.
I would argue that the "Comments only" option isn't as needed with the new
design and that we should add it back in (or do something smarter to reduce
the noise) when there's enough demand.
- Joe
>
> Cheers,
> Gary
>
--
Joe Dreimann
UX Designer | WANdisco <http://www.wandisco.com/>
Re: #471: Merge activity feed + change history
Posted by Gary Martin <ga...@wandisco.com>.
On 19/03/13 16:18, Olemis Lang wrote:
> On 3/19/13, Olemis Lang <ol...@gmail.com> wrote:
>> On 3/18/13, Joachim Dreimann <jo...@wandisco.com> wrote:
>>> I've raised ticket #471 with ideas relating to some major changes on the
>>> ticket page, and I'd like to know what you guys think.
>>> https://issues.apache.org/bloodhound/ticket/471
>>>
>> :)
>>
>>>> In essence, I propose we merge the Activity and Change History
> I forgot to mention something important , at least to me . Top posting
> is annoying . It's so hard to follow that causes me headaches . May we
> still stick to the selectors «Oldest first» «Newest first» «Comments
> only» and «Threaded» ? Timeline arrow might be updated accordingly ,
> but that's maybe just a matter of toggling css classes ...
>
> [...]
>
That is fair comment.. it might not be great for everyone. One aspect of
that is that if we make it switchable we are likely to have the new
comment at the latest comment end. I think that is what Joe intends with
the buttons above the comment input in the mockup.
We should also make sure that on the ticket page we are showing all
changes (not just the last n days) if we are continuing to use the
widget in that position.
As for the threaded view, perhaps we can add that later if there is
enough demand.
Cheers,
Gary
Re: #471: Merge activity feed + change history
Posted by Olemis Lang <ol...@gmail.com>.
On 3/19/13, Olemis Lang <ol...@gmail.com> wrote:
> On 3/18/13, Joachim Dreimann <jo...@wandisco.com> wrote:
>> I've raised ticket #471 with ideas relating to some major changes on the
>> ticket page, and I'd like to know what you guys think.
>> https://issues.apache.org/bloodhound/ticket/471
>>
>
> :)
>
>>> In essence, I propose we merge the Activity and Change History
>>
>
I forgot to mention something important , at least to me . Top posting
is annoying . It's so hard to follow that causes me headaches . May we
still stick to the selectors «Oldest first» «Newest first» «Comments
only» and «Threaded» ? Timeline arrow might be updated accordingly ,
but that's maybe just a matter of toggling css classes ...
[...]
--
Regards,
Olemis.
Re: #471: Merge activity feed + change history
Posted by Olemis Lang <ol...@gmail.com>.
On 3/18/13, Joachim Dreimann <jo...@wandisco.com> wrote:
> I've raised ticket #471 with ideas relating to some major changes on the
> ticket page, and I'd like to know what you guys think.
> https://issues.apache.org/bloodhound/ticket/471
>
:)
>> In essence, I propose we merge the Activity and Change History
>
It looks very well as it employs similarity to effectively make a
difference between comments and field changes .
well done !
[...]
>> - On hover more information is also shown, such as the date/time and
IMO this one should always be visible ...
>> edit/reply links.
>
... hiding these is just fine .
[...]
>
>> - Long code snippets and big images are shown in an overlay
>
> What do you all think?
>
... and afaics , 99% of the time there will be a lot of wasted space
under description + attachments to the left .
--
Regards,
Olemis.