January 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Phobos and printing

by Hilaire

Hi Ken, Did you have former experience using Phobos for real desktop application? Hilaire Le 30/01/2017 Ã 20:03, kmo a Ã©crit : > I think Phobos is really good. It would be great to have Pharo 6 version. > It's a pity about XULRunner being abandoned but all is not lost. There is a > fork of Firefox that is committed to keeping XULRunner support - Pale Moon - > https://www.palemoon.org/ > > Ken -- Dr. Geo http://drgeo.eu

Jan. 31, 2017

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

by Hilaire

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? 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. > -- Dr. Geo http://drgeo.eu

Jan. 31, 2017

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

by phil＠highoctane.be

Well there is no subclass of GLMBrickColorThemer so dark themes get hardcoded light colors in places for example. The Sublimish theme revealed these kind of problems. I am busy investigating. I made such a subclass and it is used by #colors now. Was missing. GLM stuff should use UITheme current xxxColor items whenever possible. Also we should have a way to reset its color registry that is cached and makes it hard to do things especially in a playground that uses it... Maybe Brick can help in the future with a clean skinning and color theme setup. Especially if Bloc can do whatever window shape (pours oil on the fire...). Phil On Tue, Jan 31, 2017 at 4:08 AM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > 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. > > >

Jan. 31, 2017

Re: [Pharo-users] GitFileTree in Pharo 5

by Pierce Ng

On Wed, Dec 14, 2016 at 02:12:40PM -0500, sergio ruiz wrote: > I am trying to install GitFileTree from the Catalog Browser. I get a warning > that itâs not tested with Pharo 5. I go ahead anyway, and it just hangs. > > Has anyone else installed it on macOS? Just tried the same on Linux Mint 17 (based on Ubuntu 14.04) and got the same. Pierce

Jan. 31, 2017

WCAG color contrast rules - was: Re: These beautiful tooltips

by Paul DeBruicker

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.

Jan. 31, 2017

Re: [Pharo-users] [NeoJSON] creating custom maps

by Sven Van Caekenberghe

> On 30 Jan 2017, at 22:32, sergio ruiz <sergio.rrd(a)gmail.com> wrote: > > This works perfectly! > > one more question.. > > how would i go about changing the default behavior in this case for NeoJSONWriterâs writeNil instance variable? I don't understand the question. The #writeNil property of NeoJSONWriter controls if you want nil values to be written out as JSON null or just have them skipped. This is independent of the mapping. The default is not to write out nil/null properties. If you want to change this, make a writer and set #writeNil: to false. For an example, see #testPointWriteNil > Thanks! > > > >> >> RadioStation class>>#neoJsonMapping: mapper >> mapper for: self do: [ :mapping | mapping mapInstVars ] >> >> > ---- > peace, > sergio > photographer, journalist, visionary > > Public Key: http://bit.ly/29z9fG0 > #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV > http://www.Village-Buzz.com > http://www.ThoseOptimizeGuys.com > http://www.coffee-black.com > http://www.painlessfrugality.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101

Jan. 30, 2017

Re: [Pharo-users] [NeoJSON] creating custom maps

by sergio ruiz

This works perfectly! one more question.. how would i go about changing the default behavior in this case for NeoJSONWriterâs writeNil instance variable?Â Thanks! RadioStation class>>#neoJsonMapping: mapper mapper for: self do: [ :mapping | mapping mapInstVars ] ---- peace, sergio photographer, journalist, visionary Public Key:Â http://bit.ly/29z9fG0 #BitMessageÂ BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.Village-Buzz.com http://www.ThoseOptimizeGuys.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Jan. 30, 2017

Re: [Pharo-users] Exercism programming exercises for Pharo

by Pau Guillot

A 2017-01-30 16:01, horrido escriguÃ©: > I created a Smalltalk track at Exercism: > https://github.com/exercism/xsmalltalk > <https://github.com/exercism/xsmalltalk> > > It would be nice if the Smalltalk community contributed some exercises > to > help budding Smalltalkers. > > Thanks. > > > > -- > View this message in context: > http://forum.world.st/Exercism-programming-exercises-for-Pharo-tp4932215.ht… > Sent from the Pharo Smalltalk Users mailing list archive at > Nabble.com. I can facilitate the exercises with test of "http://codingbat.com/" that I used to learn the syntax. I started the java but .... All of python are completed with their tests. I hang the calculator I just made with Spec, The calculator is interesting because the goal it is very simple "Get a clean string so the compiler can do the calculation from left to right" . How can I change the color of the label and the position of the text. The color method: does not seem to be the solution. All the buttons must be declared explicitly or it can be done with some method. MCHttpRepository location: 'http://www.smalltalkhub.com/mc/pauGuillot/CalculadoraSpec/main' user: '' password: '' ================================================================ Missatge enviat a travÃ©s del Webmail de Girona.com http://www.girona.com ================================================================

Jan. 30, 2017

Re: [Pharo-users] These beautiful tooltips

by Dimitris Chloupis

> Ok, I was just bugging you on this one. > > I feel abused, shame on you :D > This is your say not mine. Free software to get success really need to > have strong argument. > > Actually the GUI is a a well documented problem, many blog post and many pages have been written by , maybe I am a minority but I definitely not the only on. > > Also being a FOSS is an excuse for mere quality. > > No, free software is like Darwinism, evolve and adapt to your ecosystem > or disappear, same for proprietary software but... > > ...free software contrary to proprietary software may evolve more easily > because of the source code at the disposal of everyone, so evolution and > adaptation is easier, quicker. This is exactly what happen to Squeak, > then the Pharo fork was the promise for a better software with a > different management and more software evolution. In the long term > Squeak may just be better, nothing is written in stone as in evolution. > Pharo to attract more users in its community has no choice but to > improve its overall quality; and as well the first impression count, > little details can make some important different to retain users. > > To an extend yes FOSS is easier to move forward because it does not need money to have contributors. BUT That does not change the fact that it tends to has a lot less contributors than commercial software. Also no , FOSS will survive if does not evolve, it will lose users yes, maybe a lot of them but also a lot of people will keep using it because its free. There are still people out there coding for 30 year old technology, a small minority yes, but still tens of thousands of coders. Squeak situation was not about not wanting to evolve it was about people wanting to go different directions. Squeak still evolves , maybe not at the rate that it used to but still people contribute to it. Personally I do not blame the Squeakers or the Pharoers, it was the right choice to fork, those two different ideologies were really hard to live under one roof. > For example in DrGeo, without affordable tooltips, people will just run > it then go away, no obvious way to figure out this mess > I think you put too much value to tooltips than they deserve, I will take a well documented , easy to maintained software without any tooltips over a badly documented hard to maintain software with tooltips anyday. Ask your users, what you and I think is of little important, in the end they matter the most. There is a reason why companies spend a ridiculous amount of money on customer surveys. > Again no :) There is paid people like in proprietary software and the > bonus of unpaid talented or less talented people. Don't think the unpaid > people are the looser, they may gain other important things like > learning and improving own knowledge, experimenting/implementing new > idea (got several case like that in DrGeo history), improving > self-confidence, improving the part you need for your onw > stuff/business, etc. > > So all in all, in the long term I think free software should be superior > in quality and affordability to proprietary software. > That's just wishful thinking, in end , work is work and the more people you have the easier it is to move forward. I did not say working for free makes you a loser, dont put words in my mouth. Not that it would make sense to claim so being a very active contributor to Pharo. I may not have done a lot with bug fixing but I have done a ton of work with PBE. Does that make me a loser ? But the truth remains that there are only 3 people working part time on PBE, me , Stef and Nicolai with other contributing even less part time. We are not enough, over idealize all you want FOSS but the truth is at least in the documentation department where I have a lot of experience we have a severe lack of contributors. Its a huge problem to say to newcomers that we do not even have an up to date general purpose introductory book. It has been almost a decade of Pharo and we are not there yet. Its sad but true. On the other hand , its none's fault , thats how things are with FOSS. So no idea why you would think our documentation should be superior when we have such a hard time to find people and of course the ones we have cannot invest more than a few hours per week if we are lucky. Where is this superiority you claiming, I definitely not see it. > > > The last time I fixed a bug in Pharo , there was so much complaining > > about the way I fixed it that I decided that it would be the very last > > But I bet you learn things, especially when people were complaining: its > was feedbacks, as the tooltips in the GUI provide it ;) > > Yes I learned that being egocentric is not such a bad idea afterall, no the feedback did not help, it was just personal opinion and personal opinion is just taste. Some people wanted this way, some people wanted the other way. Personally I was ok with both approaches or my fix not being accepted. In the end my fix was integrated and later on was replaced. In the mean time everyone forgot the whole discussion and life goes on. Truth be told , I have learned a ton about Pharo by myself than with the help of others. Its really hard to find people with similar interests like mine and I have to go and explore by myself unless of course I came against a general problem, like tooltips, but I rarely am so lucky. Of course the help of this list has been extremely valuable through the years for me. Using Pharo is a lot fun but it also a ton of DIY. But you cannot have your cake and eat it too. I have been several times close to quitting Pharo but I never did it , mainly because I became more confident about myself and my ability to solve my own problems. I learned that sometimes you have to truth yourself and take the deep dive into the unknown. This is why I rarely complain about Pharo, apart for my occasional bursts of frustration. Saying all that I must note I am a huge supporter of open source because I believe in the extreme importance of open knowledge and I am proud to be part of the Pharo community.

Jan. 30, 2017

Re: [Pharo-users] These beautiful tooltips

by Hilaire

Le 30/01/2017 Ã 19:46, Dimitris Chloupis a Ã©crit : > Of course it does, glasses greatly improve the problem, they do not make > it go away. [..] Ok, I was just bugging you on this one. > "I don't buy this argument at all: tooltips were modified to become > unreadable, there are responsibility behind to be taken by someone. > FOSS is not an excuse for mere quality." > > This implies that commercial software does not have crappy GUI, to my > experience 90% of it does. Mainly because the GUI is for some weird This is your say not mine. Free software to get success really need to have strong argument. > Also being a FOSS is an excuse for mere quality. No, free software is like Darwinism, evolve and adapt to your ecosystem or disappear, same for proprietary software but... ...free software contrary to proprietary software may evolve more easily because of the source code at the disposal of everyone, so evolution and adaptation is easier, quicker. This is exactly what happen to Squeak, then the Pharo fork was the promise for a better software with a different management and more software evolution. In the long term Squeak may just be better, nothing is written in stone as in evolution. Pharo to attract more users in its community has no choice but to improve its overall quality; and as well the first impression count, little details can make some important different to retain users. For example in DrGeo, without affordable tooltips, people will just run it then go away, no obvious way to figure out this mess. > FOSS is about working for free Again no :) There is paid people like in proprietary software and the bonus of unpaid talented or less talented people. Don't think the unpaid people are the looser, they may gain other important things like learning and improving own knowledge, experimenting/implementing new idea (got several case like that in DrGeo history), improving self-confidence, improving the part you need for your onw stuff/business, etc. So all in all, in the long term I think free software should be superior in quality and affordability to proprietary software. > The last time I fixed a bug in Pharo , there was so much complaining > about the way I fixed it that I decided that it would be the very last But I bet you learn things, especially when people were complaining: its was feedbacks, as the tooltips in the GUI provide it ;) Hilaire -- Dr. Geo http://drgeo.eu

Jan. 30, 2017