Nintendo Maniac 64 wrote:Better, but as the primary user of the PC that Moonfox3 was being used on is a 63 year old man that has trouble learning and remembering new GUI concepts and in general prefers text buttons to icon-only buttons (he's been quite vocal about that when it comes to center consoles in cars), I try to keep all things UI-related as familiar as possible (it's a big reason why Pale Moon and Moonfox3 are being used in the first place, and why the PC in question runs Linux Mint with XP-styled window border theme).
This is also why I would prefer to just stick with v1.6.0 rather than making the previously-mentioned modification - there's less for me to manage and keep track of (which is ideal when I'm not the PC's primary user).
If it was just myself that was using this theme, then everything would be fine...but in that case I would probably be using something like the "Dark Moon" theme anyway.
It's possible to do this with a very small userChrome.css tweak:
Code: Select all
#appmenu-toolbar-button .toolbarbutton-text {
display: -moz-box !important;
}
#main-window:not([privatebrowsingmode=temporary]) #appmenu-toolbar-button {
list-style-image: none !important;
}
As for why this isn't the default? I had a few discussions prior to implementing this with others (including Moonchild himself), mainly on our IRC channel, where we identified the key factors that people want with a button like this:
1. The button must be uniquely recognisable (i.e. keep it blue; separately-styled to the rest of the buttons in the interface)
2. The button must represent the application (i.e. feature a Pale Moon logo, or whichever icon the application has been built with)
3. The button must indicate it is a menu (i.e. have a dropmarker)
4. The button must be compact (to not waste valuable screen real estate on the tab bar)
This satisfies those points, and the responses I received for this were positive. I can't please everyone, you know; the reason that userChrome.css exists at all is so that the user interface can be tweaked in a way that works best for YOU. If that's an unreasonable thing to suggest, then by all means use an older version, but all things considered this design is here to stay.
jez9999 wrote:Yeah. This is exactly why I was porting this theme over to PM myself, because I just knew if I left it to someone else they wouldn't be able to resist screwing around with it for no good reason. I guess I'll just keep using 1.6.0 but it's a shame I didn't finish the port and I don't have the time now. Why can't people just follow the old adage "if it aint broke, don't fix it"?
I do the best that I can for my themes given time and resource constraints in my own personal life. If there are any issues I generally fix them within a reasonable timeframe.
If you'd prefer to do things differently, I'd welcome a fork.
With that said, if you have an actual bug with the theme to report rather than my methodology, I'd be happy to hear it. Otherwise I don't have anything further to discuss with you.