Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove the badge #185

Closed
wants to merge 1 commit into from
Closed

Remove the badge #185

wants to merge 1 commit into from

Conversation

mattr-
Copy link
Member

@mattr- mattr- commented Jun 16, 2013

This issue number may also refer to the older ticket #185, now #1652.

The count in the badge is highly context dependent and in many cases, it's completely unclear in the UI as to what the count actually is. This is also reflected in the code with the use of a global @count instance variable.

This removes the feature by removing the global @count variable throughout the application and the other relevant pieces that refer to it. It's left in place in one controller where it was actually overridden to serve a different purpose.

馃毀 Let's discuss. Also note that this is not finished yet. The cucumber scenarios fail, for example. 馃毀

@lrbalt
Copy link
Member

lrbalt commented Jun 16, 2013

No, please do not do this. The badge is IMHO part of the tracks identity. It is also the logo of Tracks (the red 10).

Furthermore, I use it quite frequently to see my progress in finishing todos

@mattr-
Copy link
Member Author

mattr- commented Jun 16, 2013

IMHO, there is nothing about the badge that is in the logo of Tracks. They don't even look the same. In fact, the 10 in the rectangle looks more like a stylized date in a calendar app than it does the badge.

Code and identity issues aside, there is also a serious information architecture and interaction design issue with the badge. There is no easily discoverable use for the badge as the information changes per page. On some pages, the badge isn't even present. This makes it impossible for a user to work out what the information in the badge actually means due to the inconsistency.

The information that the badge provides needs to become context dependent per area that the badge is shown and be removed from the global layout so that it actually becomes useful without having to spend more than 30-60 seconds having to do the math to work out what the information provided might actually mean.

I'm happy to entertain and discuss alternate proposals to move this information around, but the badge the way it's functioning now needs to go, IMHO.

@lrbalt
Copy link
Member

lrbalt commented Jun 17, 2013

I agree that the badge should be used consistently. On most pages it is (i.e. the total count of items being todos, projects, context, notes, etc.)

I rather improve to make it fully consistent than to see it go. Again, for me it is part of the identity where you can recognize Tracks from a mile away :-)

@mattr-
Copy link
Member Author

mattr- commented Jun 21, 2013

Fair enough. I'll see if there's something else that can be thought of.

@mattr- mattr- closed this Jun 21, 2013
@lrbalt
Copy link
Member

lrbalt commented Jun 22, 2013

I can think of some assembla tickets :- like #1058

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants