The fonts are of your own choosing... the fonts used in eah theme are those specified in preferences. Watery uses plain labels, Vistary "fuzzy" ones (have an alpha redraw around then to help contrast). Vistary benefits from having a nice FreeType fonts (all themes do). The standard bitmapped ones can lead to illegibility dependent on font size. The fuzzy labels come at a performance cost, of course. 5 times the redraw for the label itself. I guess the colour/alpha of the edges could also be themed and (see later) user selectable at some point.
As for colour scheme, Watery (and Watery2) take a consistent colour approach. Vistary, SoftSqueak and StandardSqueak use the window/model colours. Vistary, by virtue of increased use of translucency, will inevitable "tone-down" the rather brash standard Squeak colours for various windows. I feel we have a good spread of the potential available with the use of Polymorph. Of course nobody can be totally pleased any of the time... but, the potential is there. All feedback welcomed. Getting the more flexible fillstyles and borderstyles in has really helped with the possibilities for the look of morphs. For the moment some (theme based) settings are essentially hardcoded (you can change via inspectors, for instance, Watery's window colour). Once Settled I envisiage a Theme settings tool (won't take long, all that kind of thing has already been done for our ReportBuilder). I am slightly disappointed in the responses wrt sound themes... perhaps most people don't produced end-user applications! Thanks for the feedback. ----- Original Message ----- From: "Bill Schwab" <[email protected]> To: <[email protected]> Sent: Wednesday, January 14, 2009 7:07 PM Subject: Re: [Pharo-project] Watery2 > Gary, > > No argument here. I find Watery a little bright for my taste, but > suspect that will ease off when I set the background colors to my > preference. There are aspects of Vistary that I like, though at least > in the older versions that I have used more extensively, there is a > little bit of a performance hit, and the button text can be hard to > read. Given the choice between two non-ugly options, I will invariably > go for the snappy one over the eye candy. > > FWIW, I think one of the things I like most about Vistary is that the > notifiers and debuggers are easier to identify than they are in recent > Watery with OB. STV had really strong red notifiers, and I hated them. > The clay rose that eventually evolved in Squeak was nice because it drew > attention w/o being overpowering. I am _not_ saying we should regress - > I greatly appreciate what you have been doing. I will do something to > get my ledger green editors back, and might try a subtle toning of the > stack list in the debugger; I'd have to see it to know whether it is a > useful clue or something Steve Jobs would have erased from my disk :) > > Another plus on Vistary is that the title bar text ends up being easy to > read; Watery's title bar font seems a little thin to me. But, simply > thickening it might be too much?? > > Most of this is editorial background noise. You offer great options and > they will no doubt get better over time. Watery does appear to be > standing out as the leader right now. Whether that is because it is > truly more effective or simply because we have a lot of mac users giving > attention to it is largely irrelevant. > > Thanks for the making choice so difficult!!!! > > Bill > > > > > Wilhelm K. Schwab, Ph.D. > University of Florida > Department of Anesthesiology > PO Box 100254 > Gainesville, FL 32610-0254 > > Email: [email protected] > Tel: (352) 273-6785 > FAX: (352) 392-7029 > >>>> [email protected] 01/14/09 1:18 PM >>> > Guess Watery2 will be the Pharo look-and-feel... not had any > correspondence > from Samuel for some time now... > > So, I'm focussing on Watery2 for the moment. The SVGs and exports do > take > some time. Square button corners next then the window controls > (experimented > with Vistary as proof-of-concept). > > Regards, Gary. > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
