February 2017 - Pharo-users

Re: [Pharo-users] WCAG color contrast rules - was: Re: These beautiful tooltips

by denker

> On 3 Feb 2017, at 09:21, Hilaire <hilaire(a)drgeo.eu> wrote: > > A UI quality team review would be needed before each Pharo release, I > mean with a real constraint to postpone release until a good enough > quality is reached! > In that context I can help. > > There are many place where tiny efforts could make the UI so much better > for newcomers. > > For example when I saw the debugger tooltips, there are just helpless, > their contents are the same as the button label, not acceptable!!! > > I can't understand the difference between 'over' and 'through'. I guess > other may think I don't understand the difference because I am an idiot, > but I guess there are a lot of idiots out there, and these are the ones > we want to come and *to stay* with Pharo! > > So any wish to *really* improve the UI quality, or just words? > Yes, words is the problem: it is *so* easy to know what others have to do. Trivial. *Doing* is hardâ¦ maybe you should be in charge of reviewing all changes for pharo for one month? Marcus

Feb. 3, 2017

Re: [Pharo-users] WCAG color contrast rules - was: Re: These beautiful tooltips

by Hilaire

A UI quality team review would be needed before each Pharo release, I mean with a real constraint to postpone release until a good enough quality is reached! In that context I can help. There are many place where tiny efforts could make the UI so much better for newcomers. For example when I saw the debugger tooltips, there are just helpless, their contents are the same as the button label, not acceptable!!! I can't understand the difference between 'over' and 'through'. I guess other may think I don't understand the difference because I am an idiot, but I guess there are a lot of idiots out there, and these are the ones we want to come and *to stay* with Pharo! So any wish to *really* improve the UI quality, or just words? Hilaire Le 02/02/2017 Ã 19:38, stepharong a Ã©crit : > On Tue, 31 Jan 2017 13:52:54 +0100, Hilaire > <hilaire(a)drgeo.eu> wrote: > >> I would like to help in both accessibility and implementation detail of >> the theme. In the other hand I fell we are in such flux with the future >> UI in Pharo. What are the grounds we can stand on regarding UI? > > Improve now. > Think later. > Bloc/Brick will not be ready before some versions of Pharo. -- Dr. Geo http://drgeo.eu

Feb. 3, 2017

Re: [Pharo-users] WCAG color contrast rules - was: Re: These beautiful tooltips

by phil＠highoctane.be

And there are useful A11Y (Accessibility combos down the page) http://clrs.cc/a11y/ Phil On Thu, Feb 2, 2017 at 7:38 PM, stepharong <stepharong(a)free.fr> wrote: > On Tue, 31 Jan 2017 13:52:54 +0100, Hilaire <hilaire(a)drgeo.eu> wrote: > > I would like to help in both accessibility and implementation detail of >> the theme. In the other hand I fell we are in such flux with the future >> UI in Pharo. What are the grounds we can stand on regarding UI? >> > > Improve now. > Think later. > Bloc/Brick will not be ready before some versions of Pharo. > > >> Hilaire >> >> Le 31/01/2017 Ã 11:21, phil(a)highoctane.be a >> Ã©crit : >> >>> Well there is no subclass of GLMBrickColorThemer so dark themes get >>> hardcoded light colors in places for example. >>> >>> >> > > -- > Using Opera's mail client: http://www.opera.com/mail/ > > >

Feb. 3, 2017

Re: [Pharo-users] WCAG color contrast rules - was: Re: These beautiful tooltips

by phil＠highoctane.be

About colors, I am using these ones for some projects: http://clrs.cc/ Phil On Thu, Feb 2, 2017 at 7:38 PM, stepharong <stepharong(a)free.fr> wrote: > On Tue, 31 Jan 2017 13:52:54 +0100, Hilaire <hilaire(a)drgeo.eu> wrote: > > I would like to help in both accessibility and implementation detail of >> the theme. In the other hand I fell we are in such flux with the future >> UI in Pharo. What are the grounds we can stand on regarding UI? >> > > Improve now. > Think later. > Bloc/Brick will not be ready before some versions of Pharo. > > >> Hilaire >> >> Le 31/01/2017 Ã 11:21, phil(a)highoctane.be a >> Ã©crit : >> >>> Well there is no subclass of GLMBrickColorThemer so dark themes get >>> hardcoded light colors in places for example. >>> >>> >> > > -- > Using Opera's mail client: http://www.opera.com/mail/ > > >

Feb. 3, 2017

Re: [Pharo-users] Grabbed Morph, black rectangular shadow

by Hilaire

Ok, found it, I was looking in the wrong place. Related to #wantsRoundedCordner and #handlesDropShadowInHand. Hilaire Le 02/02/2017 Ã 17:57, Hilaire a Ã©crit : > Hi, > > In Phratch, between Pharo4 and Pharo5, we have this difference when > grabbing/dragging a costume, it gots now with P5 a black rectangular > shadow, while there were no shadow with P4. > > https://github.com/janniklaval/phratch/issues/213 > > > I took a look at HandMorph but cannot find the issue. > > Any ideas? > > Hilaire -- Dr. Geo http://drgeo.eu

Feb. 2, 2017

Re: [Pharo-users] WCAG color contrast rules - was: Re: These beautiful tooltips

by stepharong

On Tue, 31 Jan 2017 13:52:54 +0100, Hilaire <hilaire(a)drgeo.eu> wrote: > I would like to help in both accessibility and implementation detail of > the theme. In the other hand I fell we are in such flux with the future > UI in Pharo. What are the grounds we can stand on regarding UI? Improve now. Think later. Bloc/Brick will not be ready before some versions of Pharo. > > Hilaire > > Le 31/01/2017 Ã 11:21, phil(a)highoctane.be a > Ã©crit : >> Well there is no subclass of GLMBrickColorThemer so dark themes get >> hardcoded light colors in places for example. >> > -- Using Opera's mail client: http://www.opera.com/mail/

Feb. 2, 2017

Re: [Pharo-users] WCAG color contrast rules - was: Re: These beautiful tooltips

by stepharong

+1 there are colors that I cannot see well in the drak theme and I'm not disabled or color blind. > One way to address this going forward is for theme developers to check > their > color selections against the e.g. Web Content Accessibility Guidelines > (https://www.w3.org/TR/WCAG20/) > > Using a readily available tool: > > https://leaverou.github.io/contrast-ratio/ > > > And/or one that makes suggestions of contrasting colors for a palette: > > http://colorsafe.co > > > And all themes could be subject to passing at a minimum contrast grade > (AA > seems not too hard?) before being added to the core. And in that way we > have > a standard of 'good enough' that is more widely accepted than 'works on > my > machine, for my eyes, in this physical space, with this ambient lighting' > > > Paul > > > > > > > > HilaireFernandes wrote >> Hi, >> >> So in Pharo5 we have these 'beautiful' unreadable tooltips: tiny black >> font on light gray (ie. take a look to its squeak counter part, it looks >> so much more pro) >> >> Is there a way to programmatically change the backround color? >> >> Thanks >> >> Hilaire >> >> -- >> Dr. Geo >> http://drgeo.eu > > > > > > -- > View this message in context: > http://forum.world.st/These-beautiful-tooltips-tp4932206p4932319.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > -- Using Opera's mail client: http://www.opera.com/mail/

Feb. 2, 2017

Re: [Pharo-users] self in Nautilus

by stepharong

On Tue, 31 Jan 2017 16:02:38 +0100, Siemen Baader <siemenbaader(a)gmail.com> wrote: > > > On Fri, Jan 27, 2017 at 9:11 PM, stepharong <stepharong(a)free.fr> wrote: >> I should tell you that I do not like it at all.Hey students inside >> comments self means the class and outside the instance! WTF? > > Which behaviour do you no like, Stef? The current or the one we are > discussing? I do not like the current one even if I remember that I push its usage. >> >> I think that we should have another kind of pseudo variable but not >> self. > > Also an option and more explicit than `self `working, but meaning > something else than at run-time. In the case where `self` is the current > object (as in the debugger) the code >can be executed with DO like when > it is later run. That is what I would find useful for prototyping. > > -- Siemen > >> >> >> >>>>> Hi all, >>> >>> in Nautilus, `self` is always the current class instance. This is >>> great for coding class side methods because we can test code fragments >>> live in the editor, but for instance side >>>methods I have not seen >>> the usefulness of it. At times it can even be confusing and cause >>> errors since a "print it" of it looks quite like an instance (`a >>> Listener` vs `Listener`). >>> >>> Is there a rationale why `self` in instance view does not raise an >>> error or is nil? And, more importantly, could there be a way to set it >>> to a specific value (= can we browse a >>>class with self bound to an >>> specific instance). >> >> In Pharo 6 if you tag a class method with >> <sampleInstance> ... >> ^ return the instance >> >> then you get automatically an icon to get an inspector on the instance. >> From there you can do whatever you want. >> >>>>>> This would resemble programming in the debugger, but provide the >>>>>> overview that a class browser provides. >>> >>> cheers, >>> Siemen >>> >>> >> >> >> >> --Using Opera's mail client: http://www.opera.com/mail/ > -- Using Opera's mail client: http://www.opera.com/mail/

Feb. 2, 2017

Re: [Pharo-users] [Seaside] Pharo 6 and Seaside

by Cyril Ferlicot D.

Le 02/02/2017 Ã 18:41, olivier auverlot a Ã©crit : > Hi, > > I try to install Seaside on Pharo 6 but the installation procedures fail. > > If I use the Catalog Browser and I choose to install the stable version > of Seaside3, I get a error message but no description of the problem. > The installation is simply not possible. > > If I use the method described on the Seaside website: > > Gofer new > > url:'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; > package: 'ConfigurationOfSeaside3'; > load. > ((Smalltalk at: #ConfigurationOfSeaside3) project version: #stable) load. > > Seaside seems installed but I can't launch the Seaside Control Panel. I > get the error message "KeyNotFound: key #NewListModel not found in > SystemDictionary". > > If I try to install all the Seaside packages: > > Gofer new > > url:'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; > package: 'ConfigurationOfSeaside3'; > load. > ((Smalltalk at: #ConfigurationOfSeaside3) project version: #stable) > load: 'CI'. > > I get the error message "Could not resolve: Zinc-Seaside". > > Someone have a method to install Seaside in Pharo 6 ? > > Best regards > Olivier :) > > Hi Olivier, I use this script to load Seaside: Metacello new smalltalkhubUser: 'Seaside' project: 'MetacelloConfigurations'; configuration: 'Seaside3'; version: #'release3.2'; load And in a baseline: spec configuration: 'Seaside30' with: [ spec className: 'ConfigurationOfSeaside3'; version: #'release3.2'; repository: 'http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main' ] I hope it helps :) > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > -- Cyril Ferlicot http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Feb. 2, 2017

Pharo 6 and Seaside

by olivier auverlot

Hi, I try to install Seaside on Pharo 6 but the installation procedures fail. If I use the Catalog Browser and I choose to install the stable version of Seaside3, I get a error message but no description of the problem. The installation is simply not possible. If I use the method described on the Seaside website: Gofer new url:'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main '; package: 'ConfigurationOfSeaside3'; load. ((Smalltalk at: #ConfigurationOfSeaside3) project version: #stable) load. Seaside seems installed but I can't launch the Seaside Control Panel. I get the error message "KeyNotFound: key #NewListModel not found in SystemDictionary". If I try to install all the Seaside packages: Gofer new url:'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main '; package: 'ConfigurationOfSeaside3'; load. ((Smalltalk at: #ConfigurationOfSeaside3) project version: #stable) load: 'CI'. I get the error message "Could not resolve: Zinc-Seaside". Someone have a method to install Seaside in Pharo 6 ? Best regards Olivier :)

Feb. 2, 2017