January 2016 - Pharo-dev - lists.pharo.org

16814 Critics Browser seriously broken /validation errors (marked as validation succeeded)

by Nicolai Hess

Who can help with this ? 16814 <https://pharo.fogbugz.com/f/cases/16814/Critics-Browser-seriously-broken> Critics Browser seriously broken

Jan. 22, 2016

Re: [Pharo-dev] [ANN] GitHub API Bindings: new version

by Sven Van Caekenberghe

> On 22 Jan 2016, at 12:02, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > Hi Skip, > > Trying your tool in Windows 8.1 and Pharo 5. I wrote my username and password and this is what I get: > > MessageNotUnderstood: NeoJSONObjectMapping>>allowNil > (there is no implementor of #allowNil) That is a pretty recent addition to NeoJSON (Neo-JSON-Core-SvenVanCaekenberghe.31), maybe that is not yet in #stable. > Cheers, > > HernÃ¡n > > > 2016-01-21 7:30 GMT-03:00 Skip Lentz <skip.lentz(a)inria.fr>: > Hi everyone, > > I am announcing a new version for the API bindings to GitHub in Pharo. > For documentation and information on how to load it, see the new project homepage: > > https://balletie.github.io/GitHub/ (generated with Pillar. Plug for Damien and Cyril) > > For a list of changes in this release, follow this link: https://github.com/Balletie/GitHub/releases/tag/v0.5 > > To load absolutely everything, including the tests and the tool, evaluate: > > Metacello new > baseline: 'GitHub'; > repository: 'github://Balletie/GitHub:master'; > load: #(tests tool) > > If you have loaded the tool, it can be opened via the world menu, under âToolsâ. > > Feedback welcome :) >

Jan. 22, 2016

Re: [Pharo-dev] [ANN] GitHub API Bindings: new version

by HernÃ¡n Morales Durand

Hi Skip, Trying your tool in Windows 8.1 and Pharo 5. I wrote my username and password and this is what I get: MessageNotUnderstood: NeoJSONObjectMapping>>allowNil (there is no implementor of #allowNil) Cheers, HernÃ¡n 2016-01-21 7:30 GMT-03:00 Skip Lentz <skip.lentz(a)inria.fr>: > Hi everyone, > > I am announcing a new version for the API bindings to GitHub in Pharo. > For documentation and information on how to load it, see the new project > homepage: > > https://balletie.github.io/GitHub/ (generated with Pillar. Plug for > Damien and Cyril) > > For a list of changes in this release, follow this link: > https://github.com/Balletie/GitHub/releases/tag/v0.5 > > To load absolutely everything, including the tests and the tool, evaluate: > > Metacello new > baseline: 'GitHub'; > repository: 'github://Balletie/GitHub:master'; > load: #(tests tool) > > If you have loaded the tool, it can be opened via the world > menu, under âToolsâ. > > Feedback welcome :) >

Jan. 22, 2016

Re: [Pharo-dev] [Pharo-users] Ready to play guinea pig for UI improvements

by Tudor Girba

Hi, Yes. That is the type of input that we need. It would be great if others would do the same. Cheers, Doru > On Jan 22, 2016, at 11:42 AM, stepharo <stepharo(a)free.fr> wrote: > > Hi guys > > Many of you may bthink that I'm mad or whatever about new UI elements. Sometimes this is true :) > but most of the time not. I'm just going straight and (harsh) comments. > So what I propose to the GT team is the following: > I'm ready to be a guinea pig > Each time they want I will record a screenflow of my interaction or perception about new/different tools. > I will follow a UI debugging process an expert proposed: talking aloud about my hypotheses while interacting and > discovering the tools. I play that in the past with other people and it works well. > > I encourage other people to do the same to give feeback to GT team. > > Stef > -- www.tudorgirba.com www.feenk.com "Speaking louder won't make the point worthier."

Jan. 22, 2016

Ready to play guinea pig for UI improvements

by stepharo

Hi guys Many of you may bthink that I'm mad or whatever about new UI elements. Sometimes this is true :) but most of the time not. I'm just going straight and (harsh) comments. So what I propose to the GT team is the following: I'm ready to be a guinea pig Each time they want I will record a screenflow of my interaction or perception about new/different tools. I will follow a UI debugging process an expert proposed: talking aloud about my hypotheses while interacting and discovering the tools. I play that in the past with other people and it works well. I encourage other people to do the same to give feeback to GT team. Stef

Jan. 22, 2016

Re: [Pharo-dev] another spotter question

by Aliaksei Syrel

I was talking about clickable arrow to open preview ;) On Jan 22, 2016 10:47 AM, "stepharo" <stepharo(a)free.fr> wrote: > Hi aliaksei > > Hi Stef > > I saw an early version of Spotter with arrows near each item and it was > IMHO awful. But still, pencils taste differently for each of us ;) > > > I do not know. May be the arrow should not be on every element but just on > the group/category > may be the colors should be deemed. > > I can agree with you that people "do not get how to use spotter". However > it depends on how we define "use spotter". From my prospective almost all > do understand how to use main feature: searching. > I think the whole discussion is about more advanced features. > > No it is about frustration. > I get a list in front of my nose and I have no clue how to access it. I > click on it and it does not work. > I have to read blog to see something and I have no clue how to obtain the > same result. > This kind of thing. > > Let's talk about how to open preview(pane to the right) in context of > learnability which consists of multiple design principles. During our > analysis we will try to determinate violated ones and see how they can be > fixed. > > a) Familiarity. It consists of guessability which is surely violated - I > can not imagine anyone who could guess that in order to open preview she > should click on arrow to the right of the item (I talk about intentional > click, not random one to see what will happen). > > ok > > Second part describes how prior knowledge applies to new system. If we > would take Pharo as new system, then principle is finally busted because I > never saw such behaviour anywhere else - it was invented in spotter. If new > system would be spotter in context of Pharo, then still violated as > clicking on arrow is not used anywhere else in Pharo. > > If you put a little triangular icons on top of the arrow then people will > certainly undertsand that they can click on it. > > My point is ask yourself why many people do not know how to open the pane. > I could not find it. Once I got it I asked around and really few people > know it. > > Possible way to fix familiarity principle is to spread usage of arrow to > the whole Pharo (or world) or to modify its design to improve guessability > by adding preview icon/label/whatever on the arrow. > > b) Generalizability. Meaning that user can extend specific interaction > knowledge to new situations. Clicking on arrow is only used in one place in > spotter - so there is no chance for user to extend not existing knowledge. > Violated. > > Fix is similar to familiarity - clicking on arrow to expand/open new pane > should be used in more places. > > I do not think. > > c) Predictability. Consists of determinism and operation visibility. > Determinism is not violated because effect of clicking on arrow can be > immediately observed by user. However, operation visibility is violated - > arrow does not change depending whether preview is available or not. > > To fix operation visibility we need to change arrow color/icon depending > on availability of preview. > > > You do not reply to the point that to see that I can interact with a group > of element I have to select the first one. > Currently it only work because some people use arrows. I never because > there are at the bottom of my keyboard. > > d) Synthesisability. Not violated - user can easily observe effect of past > operations. Preview has only two states: on and off. > > e) Consistency. We can not say anything, because there are no similar > situations in the system. > > To conclude, an action to open preview should be improved. The most > easiest fix would be to add something on top of arrow to make it obvious > (improve guessability) what clicking does. > > yes to improve the fact that we may click on something. > > More preferred one IMHO is to expose arrow usecases and teach users so > that generalizability would start playing a role. > > I do not get it. > You should understand that Pharo can be used with a mouse. > > Sorry for long email > Alex > > > Le 20/1/16 14:30, Aliaksei Syrel a Ã©crit : > > On Wed, Jan 20, 2016 at 12:59 PM, Ben Coman <btc(a)openinworld.com> wrote: > >> +1. Its annoying that it takes two clicks to dive into categories like >> "Implementors" (one to click an item under the category to make the arrow >> appear, and then another to click on it) when it would only take one if >> that arrow for each category was always visible. > > > Doru is right, always visible arrows would pollute UI. > > I do not see why. > A user interface is not something that we should click randomly at to > learn how to use it. > > A compromise solution would be to show them on mouse hover - one click + > not overcrowded interface. > > > may be > but you can ask yourselves why so many people do not get how to use > Spotter. > I asked again today to people how to show the pane on the right and nobody > knew obviously. > > > Cheers, > Alex > > > >

Jan. 22, 2016

Re: [Pharo-dev] another spotter question

by stepharo

Hi aliaksei > Hi Stef > > I saw an early version of Spotter with arrows near each item and it > was IMHO awful. But still, pencils taste differently for each of us ;) > I do not know. May be the arrow should not be on every element but just on the group/category may be the colors should be deemed. > I can agree with you that people "do not get how to use spotter". > However it depends on how we define "use spotter". From my prospective > almost all do understand how to use main feature: searching. > I think the whole discussion is about more advanced features. > No it is about frustration. I get a list in front of my nose and I have no clue how to access it. I click on it and it does not work. I have to read blog to see something and I have no clue how to obtain the same result. This kind of thing. > Let's talk about how to open preview(pane to the right) in context of > learnability which consists of multiple design principles. During our > analysis we will try to determinate violated ones and see how they can > be fixed. > > a) Familiarity. It consists of guessability which is surely violated - > I can not imagine anyone who could guess that in order to open preview > she should click on arrow to the right of the item (I talk about > intentional click, not random one to see what will happen). > ok > Second part describes how prior knowledge applies to new system. If we > would take Pharo as new system, then principle is finally busted > because I never saw such behaviour anywhere else - it was invented in > spotter. If new system would be spotter in context of Pharo, then > still violated as clicking on arrow is not used anywhere else in Pharo. > If you put a little triangular icons on top of the arrow then people will certainly undertsand that they can click on it. My point is ask yourself why many people do not know how to open the pane. I could not find it. Once I got it I asked around and really few people know it. > > Possible way to fix familiarity principle is to spread usage of arrow > to the whole Pharo (or world) or to modify its design to improve > guessability by adding preview icon/label/whatever on the arrow. > > b) Generalizability. Meaning that user can extend specific interaction > knowledge to new situations. Clicking on arrow is only used in one > place in spotter - so there is no chance for user to extend not > existing knowledge. Violated. > > Fix is similar to familiarity - clicking on arrow to expand/open new > pane should be used in more places. > I do not think. > c) Predictability. Consists of determinism and operation visibility. > Determinism is not violated because effect of clicking on arrow can be > immediately observed by user. However, operation visibility is > violated - arrow does not change depending whether preview is > available or not. > > To fix operation visibility we need to change arrow color/icon > depending on availability of preview. > You do not reply to the point that to see that I can interact with a group of element I have to select the first one. Currently it only work because some people use arrows. I never because there are at the bottom of my keyboard. > d) Synthesisability. Not violated - user can easily observe effect of > past operations. Preview has only two states: on and off. > > e) Consistency. We can not say anything, because there are no similar > situations in the system. > > To conclude, an action to open preview should be improved. The most > easiest fix would be to add something on top of arrow to make it > obvious (improve guessability) what clicking does. > yes to improve the fact that we may click on something. > > More preferred one IMHO is to expose arrow usecases and teach users so > that generalizability would start playing a role. > I do not get it. You should understand that Pharo can be used with a mouse. > > Sorry for long email > Alex > > > > Le 20/1/16 14:30, Aliaksei Syrel a Ã©crit : >> On Wed, Jan 20, 2016 at 12:59 PM, Ben Coman <btc(a)openinworld.com >> <mailto:btc@openinworld.com>> wrote: >> >> +1. Its annoying that it takes two clicks to dive into categories >> like "Implementors" (one to click an item under the category to >> make the arrow appear, and then another to click on it) when it >> would only take one if that arrow for each category was always >> visible. >> >> >> Doru is right, always visible arrows would pollute UI. > I do not see why. > A user interface is not something that we should click randomly at to > learn how to use it. > >> A compromise solution would be to show them on mouse hover - one >> click + not overcrowded interface. > > may be > but you can ask yourselves why so many people do not get how to use > Spotter. > I asked again today to people how to show the pane on the right and > nobody knew obviously. >> >> Cheers, >> Alex >

Jan. 22, 2016

Re: [Pharo-dev] another spotter question

by David Allouche

> On 22 Jan 2016, at 10:23, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > Sorry for long email > I found it rather short and synthetic ;-) At least compared to my recent messages.

Jan. 22, 2016

Re: [Pharo-dev] another spotter question

by Aliaksei Syrel

Hi Stef I saw an early version of Spotter with arrows near each item and it was IMHO awful. But still, pencils taste differently for each of us ;) I can agree with you that people "do not get how to use spotter". However it depends on how we define "use spotter". From my prospective almost all do understand how to use main feature: searching. I think the whole discussion is about more advanced features. Let's talk about how to open preview(pane to the right) in context of learnability which consists of multiple design principles. During our analysis we will try to determinate violated ones and see how they can be fixed. a) Familiarity. It consists of guessability which is surely violated - I can not imagine anyone who could guess that in order to open preview she should click on arrow to the right of the item (I talk about intentional click, not random one to see what will happen). Second part describes how prior knowledge applies to new system. If we would take Pharo as new system, then principle is finally busted because I never saw such behaviour anywhere else - it was invented in spotter. If new system would be spotter in context of Pharo, then still violated as clicking on arrow is not used anywhere else in Pharo. Possible way to fix familiarity principle is to spread usage of arrow to the whole Pharo (or world) or to modify its design to improve guessability by adding preview icon/label/whatever on the arrow. b) Generalizability. Meaning that user can extend specific interaction knowledge to new situations. Clicking on arrow is only used in one place in spotter - so there is no chance for user to extend not existing knowledge. Violated. Fix is similar to familiarity - clicking on arrow to expand/open new pane should be used in more places. c) Predictability. Consists of determinism and operation visibility. Determinism is not violated because effect of clicking on arrow can be immediately observed by user. However, operation visibility is violated - arrow does not change depending whether preview is available or not. To fix operation visibility we need to change arrow color/icon depending on availability of preview. d) Synthesisability. Not violated - user can easily observe effect of past operations. Preview has only two states: on and off. e) Consistency. We can not say anything, because there are no similar situations in the system. To conclude, an action to open preview should be improved. The most easiest fix would be to add something on top of arrow to make it obvious (improve guessability) what clicking does. More preferred one IMHO is to expose arrow usecases and teach users so that generalizability would start playing a role. Sorry for long email Alex Le 20/1/16 14:30, Aliaksei Syrel a Ã©crit : On Wed, Jan 20, 2016 at 12:59 PM, Ben Coman <btc(a)openinworld.com> wrote: > +1. Its annoying that it takes two clicks to dive into categories like > "Implementors" (one to click an item under the category to make the arrow > appear, and then another to click on it) when it would only take one if > that arrow for each category was always visible. Doru is right, always visible arrows would pollute UI. I do not see why. A user interface is not something that we should click randomly at to learn how to use it. A compromise solution would be to show them on mouse hover - one click + not overcrowded interface. may be but you can ask yourselves why so many people do not get how to use Spotter. I asked again today to people how to show the pane on the right and nobody knew obviously. Cheers, Alex

Jan. 22, 2016

Re: [Pharo-dev] Spotter suggestions

by David Allouche

> On 21 Jan 2016, at 22:36, stepharo <stepharo(a)free.fr> wrote: > > Le 20/1/16 10:39, David Allouche a Ã©crit : >> Since you asked to keep challengingâ¦ >> >> Preamble: Sorry, I did one of those long messages again. I hope I am not annoying people with that. > > Not at all thanks for sharing that. > I appreciate that you take the time to write it because I'm a lot more intuitive and have not the time > fully develop my gut feeling. So I sound harsh and at the end I do not use the features. > And people get sad when I say it. Thanks for the kind words. :-) I hope that will motivate Tudor to read my messageâ¦

Jan. 22, 2016