Look Chris, I really don't get where you're coming from, I don't get all these "x"'s all over the place and I don't see what the trade off is. Like in the example I cited originally (http://dribbble.com/shots/ 303878-Growl-Notification) you can clearly see where the "x" is, there's no questions. Now, if you don't like it then I say fine, you could force all "x" (close) graphics to the top left or use your default graphic or the designer would have one ready made if that option were enforced. Otherwise the designer would be free to implement it the way they see fit, let the user flick set their preference - there's enough customisation in GROWL to justify that.
I have thought of another idea also: what about having the "x" button behave magnetic like, so that it's attached to the edge (like with Daryl Ginn's Theme), behaving like a railway train and so attracted to wherever the mouse cursor is. This way the "x" button would move to the users cursor and they wouldn't have to search as it would follow them, but just on the edge of the notification. Thoughts? On Nov 13, 3:57 pm, joeyhoer <[email protected]> wrote: > As a theme developer, would also like "close button customization" to > be available. I understand the developers concerns of usability, but I > think that there is a mutual solution that could be reached. > > First, I would like to note that OSX itself has different close > buttons for different types of windows - HUD, Standard, QuickLook. > Given that Growl is so customizable, and that the current close button > is quite outdated, I feel that there is good merit to the fact that > people would desire to customize the style of the close button. Of > particular concern are cases in which the close button is offset > drastically because a theme uses borders or animations which require a > larger frame. > > I have familiarity with the theme that "changes" the close button to > red. Actually, the theme simply uses some clever CSS to overlay the > current close button. This isn't a practical solution - a much cleaner > solution would be if you were to allow developers to customize the > close button themselves, and allow users to "opt-in" to a customized > close button of chose the default. (I hope that made sense) > > I envision an option in the preferences that would "Enable customized > close buttons" - perhaps even on a theme by theme basis. And then let > developers hook in this functionality by using a %close% class or > something similar. > > I understand the concerns about usability, but I feel like users would > be presented with a much better experience if this was themeable. -- 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.
