Currently, the class names follow the pattern:

node-flagged-FLAGNAME-self
node-flagged-FLAGNAME

To prevent confusion I think that we should change it to:

node-flagged-FLAGNAME-by-self
node-flagged-FLAGNAME-by-anybody

Comments

mooffie’s picture

Title: Chnage the class names? » Change the class names?
adam_b’s picture

Hmmm... so far I've only used global flags, but this sounds good in principle.

TimelessDomain’s picture

This is a good idea.
node-flagged-FLAGNAME-by-self
node-flagged-FLAGNAME-by-anybody

Would be cool if you could increment the css class by using the flag count. So each time another person flags it, you could so special actions w/ the css. For example 1) slowly have a color gradient occur (use case: in a support ticket area to show which tickets are most important. hmm... If Drupal.org uses flags to solve the "Subscribe/ +1" issue comment problem, then we could use this feature to make the issue queues much more legible (valuable at first glance)) . Another use case 2) would be to have an image that slowly fades in or slowly assembles as more people flag the node/entity. For ex. You could use a % # to match up with the # of flags, & then have some action occur after X # of flags. If X is 10, each flagging would increase/ swap out the glag image by 10

node-flagged-FLAGNAME-by-anybody-COUNT

"node" should be removed, since flag works on other entities as well, & therefore Flag Classes should.

So final list of flag names

  • flagged-FLAGNAME-by-self
  • flagged-FLAGNAME-by-anybody
  • flagged-FLAGNAME-by-anybody-COUNT
lpalgarvio’s picture

+1. clarification is a good thing

delacosta456’s picture

Version: » 7.x-1.x-dev
Issue summary: View changes

hi is this already implemented .. i can really see how to use this module