May 2015 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50030 Home: https://github.com/pharo-project/pharo-core

May 5, 2015

Re: [Pharo-dev] Case 15309 - Adding message for test result

by Ben Coman

On Tue, May 5, 2015 at 7:46 AM, Sergio Fedi <sergio.fedi(a)gmail.com> wrote: > Hi, I'm planning to solve Case 15309: > > https://pharo.fogbugz.com/f/cases/15309/adding-message-for-test-result > > Personally, I'm not sure what is needed, and I would prefer to do this > change at the request of an actual color blind person who needs it and can > provide real feedback on the issue. > > But that's why I'm tackling this case: > > To determine *whether we should do something about it, and what* > *or **to close it* > > > There are different types of colour-blindess. I have a friend with one that see predominantly one colour (e.g blue) and the other kid sees predominantly another colour(e.g.yellow). I don't think any one colourblind person will give broadly applicable results. I think we'll do better addressessing general design principles [1] [2] and testing software[3]. [1] http://designshack.net/articles/accessibility/tips-for-designing-for-colorb… [2] http://stackoverflow.com/questions/1498669/gui-design-for-color-blindness [3] http://colororacle.org (disclaimer, I haven't used it, just a recommendation from some lists) cheers -ben

May 5, 2015

Case 7256 - TestRunner should not deal with UI

by Sergio Fedi

I'm plannig to tackle this case https://pharo.fogbugz.com/f/cases/7256/TestRunner-should-not-deal-with-UI I am all in for decoupling the TestRunner UI from the functionality it provides. And even making a new object that both the CommandLineTestRunner and the TestRunner use. I wouldn't do that subclassifying both from a common superclass. That is, I would use composition, not inheritance. Before I begin with this, anyone have some insight or thoughts to share?

May 5, 2015

Re: [Pharo-dev] Case 15309 - Adding message for test result

by Cyril Ferlicot

That can be an easy fix so that would be sad to close it that fast. You can maybe use the method "Object inform: 'text' ". This method will display a little window at the bottom left of your World. On 5 May 2015 at 01:46, Sergio Fedi <sergio.fedi(a)gmail.com> wrote: > Hi, I'm planning to solve Case 15309: > > https://pharo.fogbugz.com/f/cases/15309/adding-message-for-test-result > > Personally, I'm not sure what is needed, and I would prefer to do this > change at the request of an actual color blind person who needs it and can > provide real feedback on the issue. > > But that's why I'm tackling this case: > > To determine whether we should do something about it, and what > or to close it > > -- Cheers Cyril Ferlicot

May 4, 2015

Case 15309 - Adding message for test result

by Sergio Fedi

Hi, I'm planning to solve Case 15309: https://pharo.fogbugz.com/f/cases/15309/adding-message-for-test-result Personally, I'm not sure what is needed, and I would prefer to do this change at the request of an actual color blind person who needs it and can provide real feedback on the issue. But that's why I'm tackling this case: To determine *whether we should do something about it, and what* *or **to close it*

May 4, 2015

Re: [Pharo-dev] Where to start contributing

by Sergio Fedi

Great, thanks for the explanation Ben. Now I know how to do that. â *bookmarking mail*

May 4, 2015

Roadmaps

by Sergio Fedi

On Mon, May 4, 2015 at 7:56 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > >> *Is there a place where to put all these comments and > >> questions/comments/ramblings?* > >> *If there is, where?* > > > > These are probably best to start on the mail list. Then copy pertinant > > parts to any issues created. > > Also, for really thorny issues, you can build a list of what you learn in a > doc at https://github.com/pharo-project/pharo-workingRoadmaps . I'm doing > this for TxText... > Interesting. So, these roadmaps. I read some of them but I didn't get a clear picture of what are they, so here I am asking: What are roadmaps? Why should we use them? (what problem do they solve) How do we use them? I have a feeling that they are like a "roadmap to the final implementation" That is, an explanation of the different decisions you took as part of solving a problem that led you to where you finally arrived. Feel free to correct me.

May 4, 2015

Re: [Pharo-dev] Improving the About Text of Versionner

by Sergio Fedi

Wow! Look what I stirred up! Ok, I *vaguely* understand the two configuration schemes. I do understand how I touched two projects that are mantained differently and the problems in that. I'm not sure what to learn from all of this (I know I didn't do anything wrong) About the design issues. I cringed when I saw that code, that's why I wanted to model the About information in an object, but that would be a lot more change and without knowing all the classes involved. That's why I asked in another mail what to do after a Case is resolved, about further work. Ok then, now I have no idea if I should be doing anything else about this Case. For now I'm going to keep reading how this issue evolves and if I have to do something, just tell me. PS: I'm not discouraged at all, I know the difficulties of projects of this size. Thanks everyone for the patience and encouragement.

May 4, 2015

Re: [Pharo-dev] Package comments

by Sergio Fedi

I know little about the subject but Packages have been until recently only Strings. Now they were reified as objects, but as far as I saw, these objects didn't have comments as a part of them. â

May 4, 2015

Re: [Pharo-dev] [QUESTION] For Dark Theme users

by Nicolai Hess

2015-05-04 23:43 GMT+02:00 Andrei Chis <chisvasileandrei(a)gmail.com>: > > > On Mon, May 4, 2015 at 11:31 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> @esteban, as you are working on dark theme, can you take a look at this >> issue >> 14923 <https://pharo.fogbugz.com/default.asp?14923> >> TextAdornment: take account of current theme background color >> >> I am not sure what is the right way to solve this for rubric, and even if >> I would know it, >> I can not commit to rubrics repository :) >> > > Rubric repo is now under the Pharo team (Pharo/Rubric) > > Yes, but I tried it already, I can not commit ( https://pharo.fogbugz.com/default.asp?15273#BugEvent.126410) > > Cheers, > Andrei > > > >> >> >> >> 2015-05-02 10:24 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >>> >>> On 02 May 2015, at 04:10, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> >>> wrote: >>> >>> This is maybe a little 'too' dark. >>> Maybe we can do a setting to choose if we want it more or less dark. >>> >>> >>> yes, but we also need a good default, because most people will not tune >>> their system until they are used to it :) >>> So, I think we need to restore the âpreference theme settingsâ options >>> (another brick in the wallâ¦ I mean another todo entry in my list) >>> And in the mean time I will chose something between current and my >>> proposal (because Iâm convinced current one does not offer good contrast). >>> >>> Esteban >>> >>> >>> An other think that would be good with the dark theme is to change the >>> color of the Test Runner because the fluo green attack the eyes when we're >>> on the dark theme x_x. >>> >>> Since we talk about the dark theme, is that normal than the background >>> of the RubScrolledTextMorph stay white ? Or should I use an other Rub text >>> morph ? >>> >>> On 1 May 2015 at 13:52, phil(a)highoctane.be <phil(a)highoctane.be> wrote: >>> >>>> Dawn Theme is lighter actually. >>>> >>>> As long as it is not black ... >>>> >>>> Phil >>>> Le 1 mai 2015 12:34, "Esteban Lorenzano" <estebanlm(a)gmail.com> a >>>> Ã©crit : >>>> >>>>> I suppose "Down Themeâ users (cough, cough, Phil) too. >>>>> >>>>> I want to change the background color for something even darker: >>>>> >>>>> <Screen Shot 2015-05-01 at 12.33.48.png> >>>>> >>>>> >>>>> >>>>> I think it look betterâ¦ what do you think? >>>>> >>>>> (Alsoâ¦ I need to refactor this theme thingyâ¦ is really ugly :P) >>>>> >>>>> Esteban >>>>> >>>> >>> >>> >>> -- >>> Cheers >>> Cyril Ferlicot >>> >>> >>> >> >

May 4, 2015