The request was to customize the look and location from a lot of people. So it 
comes down to whether we'd be able to accept the usability loss when 
considering that. 

We're not adding yet another option for something like this. It's either in or 
it's not. So far I haven't seen a compelling argument for it, other than "hey 
it'd be neat!". That doesn't address my concern though. I'd like to think about 
it a bit more. Do we care more about usability, or do we care more about 
theming? That's so far what this is coming down to for me. So since you're 
advocating theming, that's why I've been asking for you to help account for the 
usability concerns. I've not been able to resolve them within the last year of 
thinking on this issue. Yes, there are different width themes and that makes 
you move the mouse slightly between the two. But that's not anything like the 
example I have.

Here's your example in mouse clicks:

  x
x 
 x
  x
  x
x 
 x
  x

  x
x 
 x
  x


Here's mine:

x
                     x
x
                      x
x
              x
x 
        x
                     x
x
x
x    
                x

Give or take a few displays. See how the first example works better than the 
second from a sheer usability standpoint? That's what we have now, we allow for 
different width notifications which seems to be acceptable. But what you're 
proposing is a close button that can be anywhere, which can look like anything. 
So not only does the user have to search around for it because it's visually 
different. They also have to possibly do something like my example after 
hunting each different looking one down.

If we were going to do theming of the close button and random positioning like 
you want, we have to take these scenario's into account and address them. The 
scenario I'm showing here can very well happen, so I want to make sure we 
account for it. Thoughts? 

-- 
Chris Forsythe


On Friday, November 11, 2011 at 4:02 PM, tenderhooks wrote:

> Well, I'm not sure I see why they have to go to two points, unless
> it's designed like that. But I have multiple styles in use and they
> vary in size, so while I may play around with the one's I am happy to
> see, it is my choice. I also think that most of the time the
> notification will just disappear itself, I only have one notification
> kept on screen, simply hovering over it will display the close button
> and "I get it" strait away.
> 
> I appreciate that you're trying to fit in with OS X and provide some
> familiarity but they styles are anything but that, they're all
> different and I think you don't appreciate that people quickly adapt.
> 
> How about having an override option: so that, when enabled, the close
> button is always in the same place (as it is now), but if unchecked
> then the designer can have that final tweak to do as they will. This
> way you please everybody and it's not like you don't allow full
> customisations of transparencies and lines of text etc... now, this
> would just be the icing on the cake don't you think?
> 
> Thanks.
> 
> 
> On Nov 10, 4:48 pm, Chris Forsythe <[email protected] (http://growl.info)> 
> wrote:
> > And that's what I'm having a hard time with. If the button can be in random 
> > places for different displays AND an end user can use multiple displays, 
> > then they have to go searching for the close button.
> > 
> > Our close button matches Dashboard, Launchpad, and a few other instances 
> > within OS X of a close button. I don't need a poll to know that style 
> > authors want to style everything, but we also need to consider usability 
> > here. So I'm trying to have a rather frank discussion with you about how to 
> > handle this, since you brought it up. If you want to participate in that 
> > discussion, I need you to think about the problem here and help us come up 
> > with a solution to it.
> > 
> > Here is an example of the problem:
> > 
> > (x) [NOTIFICIATION]
> > [NOTIFICATION] (X)
> > 
> > Now the user has to go to two separate locations to close two 
> > notifications, in a diagonal fashion. Then say the get something like this:
> > 
> > (x) [NOTIFICIATION]
> > [NOTIFICATION] (X)
> > 
> > (x) [NOTIFICIATION]
> > [NOTIFICATION] (X)
> > 
> > (x) [NOTIFICIATION]
> > [NOTIFICATION] (X)
> > 
> > (x) [NOTIFICIATION]
> > [NOTIFICATION] (X)
> > 
> > (x) [NOTIFICIATION]
> > [NOTIFICATION] (X)
> > 
> > That just doesn't seem good to me. Thoughts?
> > 
> > --
> > Chris Forsythe
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > On Thursday, November 10, 2011 at 1:58 AM, tenderhooks wrote:
> > > I'm not entirely sure what you mean, I am referring to the colour of
> > > the button, I'e noticed that it can be red at times. Not a programmer/
> > > designer I was not aware the button could be altered, except for it's
> > > position. I am calling for the button's position to be freely
> > > manageable as well as it's size and style as the default can look
> > > clumsy compared to a good designers efforts.
> > > 
> > 
> > 
> > > Maybe you should have a poll, email the designers who've made popular
> > > styles and ask them, they're the ones who keep your program relevant.
> > > 
> > 
> > 
> > > On Nov 10, 3:37 am, Christopher Forsythe <[email protected] 
> > > (http://growl.info)> wrote:
> > > > If a user has 2 styles they use. One is using a pink close button at the
> > > > top right, and the other is the bottom left and and purple, how does 
> > > > that
> > > > affect usability?
> > > > 
> > > 
> > > 
> > 
> > 
> > > > Chris
> > 
> > > > On Sat, Nov 5, 2011 at 7:00 AM, tenderhooks <[email protected] 
> > > > (http://gmail.com)> wrote:
> > > > > No, no, I mean, allow it be customised as your presently do with the
> > > > > entire box. As it stands the whole box can be modified, but this style
> > > > > is applicable to itself only, I just mean allow the "x" close button
> > > > > to be customisable and ring-fensed to that style, which wouldn't
> > > > > affect any of the others, like the different styles now happily co-
> > > > > exist together.
> > > > > 
> > > > 
> > > > 
> > > 
> > 
> > 
> > > > > Thanks.
> > 
> > > > > On Nov 5, 10:59 am, Chris Forsythe <[email protected] 
> > > > > (http://growl.info)> wrote:
> > > > > > Because then if the end user is using a different display for 
> > > > > > another
> > > > > 
> > > > > 
> > > > 
> > > 
> > 
> > 
> > > > > application, the close buttons do not match.
> > 
> > > > > > --
> > > > > > Chris Forsythe
> > > > > > 
> > > > > 
> > > > 
> > > 
> > 
> > 
> > > > > > On Saturday, November 5, 2011 at 5:39 AM, tenderhooks wrote:
> > > > > > > I can't believe it, the concept is a beautiful one and visually 
> > > > > > > much
> > > > > > > more appealing than your present one, this is a Mac application 
> > > > > > > we're
> > > > > > > talking about. Why not allow for this small part to be customised 
> > > > > > > as
> > > > > > > you do the rest of the object, it doesn't make much sense?!
> > > > > > > 
> > > > > > 
> > > > > > 
> > > > > 
> > > > 
> > > 
> > 
> > 
> > > > > > > On Nov 4, 5:47 pm, Christopher Forsythe <[email protected] 
> > > > > > > (http://growl.info) (
> > > > > http://growl.info)> wrote:
> > > > > > > > We don't agree with the idea of making this themable due to 
> > > > > > > > usability
> > > > > > > > concerns.
> > > > > > > > 
> > > > > > > 
> > > > > > 
> > > > > 
> > > > > 
> > > > 
> > > 
> > 
> > 
> > > > > > > > Chris
> > 
> > > > > > > > On Fri, Nov 4, 2011 at 12:37 PM, joelw135 <[email protected] 
> > > > > > > > (http://waxman.org) (
> > > > > http://waxman.org)> wrote:
> > > > > > > > > Where is the download link?
> > > > > > > > 
> > > > > > > 
> > > > > > 
> > > > > 
> > > > > 
> > > > 
> > > 
> > 
> > 
> > > > > > > > > On Nov 4, 1:30 pm, tenderhooks <[email protected] 
> > > > > > > > > (http://gmail.com) (
> > > > > http://gmail.com)> wrote:
> > > > > > > > > > I found an excellent skin for GROWL by Daryl Ginn, it's 
> > > > > > > > > > eloquent
> > > > > > > > > 
> > > > > > > > 
> > > > > > > 
> > > > > > 
> > > > > 
> > > > > 
> > > > 
> > > 
> > 
> > 
> > > > > and
> > > > > > > > > > has a snazzy horizontal flip transition, but he wasn't able 
> > > > > > > > > > to do
> > > > > > > > > > anything about the "x" (close) button. You can see from the
> > > > > > > > > > conversations on his design page that he tried a lot of 
> > > > > > > > > > things,
> > > > > > > > > > 
> > > > > > > > > 
> > > > > > > > 
> > > > > > > 
> > > > > > 
> > > > > 
> > > > > 
> > > > 
> > > 
> > 
> > 
> > > > > it's
> > > > > > > > > > just not configurable.
> > > > > > > > > 
> > > > > > > > 
> > > > > > > 
> > > > > > 
> > > > > 
> > > > > 
> > > > 
> > > 
> > 
> > 
> > > > > > > > > > I've noticed this now, I think the "x" button is the weakest
> > > > > part of
> > > > > > > > > > the design and it would be great if this part were 
> > > > > > > > > > customisable
> > > > > > > > > 
> > > > > > > > 
> > > > > > > 
> > > > > > 
> > > > > 
> > > > > 
> > > > 
> > > 
> > 
> > 
> > > > > for a
> > > > > > > > > > designer!
> > > > > > > > > 
> > > > > > > > 
> > > > > > > 
> > > > > > 
> > > > > 
> > > > > 
> > > > 
> > > 
> > 
> > 
> > > > > > > > > > ref:http://dribbble.com/shots/303878-Growl-Notification
> > 
> > > > > > > > > --
> > > > > > > > > You received this message because you are subscribed to the 
> > > > > > > > > Google
> > > > > > > > > 
> > > > > > > > 
> > > > > > > 
> > > > > > 
> > > > > 
> > > > 
> > > 
> > 
> > 
> > > > > Groups
> > > > > > > > > "Growl Discuss" group.
> > > > > > > > > To post to this group, send email to 
> > > > > > > > > [email protected] 
> > > > > > > > > (mailto:[email protected])(mailto:
> > > > > > > > > 
> > > > > > > > 
> > > > > > > 
> > > > > > 
> > > > > 
> > > > > 
> > > > 
> > > 
> > 
> > 
> > > > > [email protected] (mailto:[email protected])).
> > > > > > > > > To unsubscribe from this group, send email to
> > > > > > > > > [email protected] 
> > > > > > > > > (mailto:[email protected]) (mailto:
> > > > > > > > > 
> > > > > > > > 
> > > > > > > 
> > > > > > 
> > > > > 
> > > > > 
> > > > 
> > > 
> > 
> > 
> > > > > [email protected] 
> > > > > (mailto:[email protected])).
> > > > > > > > > For more options, visit this group at
> > > > > > > > > http://groups.google.com/group/growldiscuss?hl=en.
> > > > > > > > > 
> > > > > > > > 
> > > > > > > 
> > > > > > 
> > > > > 
> > > > > 
> > > > 
> > > 
> > 
> > 
> > > > > > > --
> > > > > > > You received this message because you are subscribed to the Google
> > > > > > > 
> > > > > > 
> > > > > 
> > > > 
> > > 
> > 
> > 
> > > > > Groups "Growl Discuss" group.
> > > > > > > To post to this group, send email to 
> > > > > > > [email protected] 
> > > > > > > (mailto:[email protected])(mailto:
> > > > > > 
> > > > > 
> > > > > 
> > > > 
> > > 
> > 
> > 
> > > > > [email protected] (mailto:[email protected])).
> > > > > > > To unsubscribe from this group, send email to
> > > > > > 
> > > > > 
> > > > > 
> > > > 
> > > 
> > 
> > 
> > > > > [email protected] 
> > > > > (mailto:[email protected]) (mailto:
> > > > > [email protected] 
> > > > > (mailto:[email protected])).
> > > > > > > For more options, visit this group athttp://
> > > > > > 
> > > > > 
> > > > > 
> > > > 
> > > 
> > 
> > 
> > > > > groups.google.com/group/growldiscuss?hl=en 
> > > > > (http://groups.google.com/group/growldiscuss?hl=en).
> > 
> > > > > --
> > > > > You received this message because you are subscribed to the Google 
> > > > > Groups
> > > > > "Growl Discuss" group.
> > > > > To post to this group, send email to [email protected] 
> > > > > (mailto:[email protected]).
> > > > > To unsubscribe from this group, send email to
> > > > > [email protected] 
> > > > > (mailto:[email protected]).
> > > > > For more options, visit this group at
> > > > > http://groups.google.com/group/growldiscuss?hl=en.
> > > > > 
> > > > 
> > > 
> > 
> > 
> > > --
> > > You received this message because you are subscribed to the Google Groups 
> > > "Growl Discuss" group.
> > > To post to this group, send email to [email protected] 
> > > (mailto:[email protected]).
> > > To unsubscribe from this group, send email to 
> > > [email protected] 
> > > (mailto:[email protected]).
> > > For more options, visit this group 
> > > athttp://groups.google.com/group/growldiscuss?hl=en.
> > > 
> > 
> > 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Growl Discuss" group.
> To post to this group, send email to [email protected] 
> (mailto:[email protected]).
> To unsubscribe from this group, send email to 
> [email protected] 
> (mailto:[email protected]).
> For more options, visit this group at 
> http://groups.google.com/group/growldiscuss?hl=en.
> 
> 


-- 
You received this message because you are subscribed to the Google Groups 
"Growl Discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/growldiscuss?hl=en.

Reply via email to