- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] CasInsensitiveOrder map with upper/lower case characters for all latin1 entries

by stepharo

It is cool to have you three on board. I love your discussions because I'm learning by immersion. Le 6/1/16 09:58, Nicolai Hess a Ã©crit : > > see issues 17302/17242/17227 > String>>findString:startindAt:caseSensitive appears to be failing for > extended charsets > String>>compare:caseSensitive seems to be failing for extended charset > comparisons > String>>beginsWithEmpty:caseSensitive: has test failure for some cases > > the problem is, the standard character set used for building the > CaseInsensitiveOrder map > only maps characters from the set of ascii characters but it is used > in the findString/compare/beginsWith-methods for all byte characters. > > Any objections if we fill this map like it is suggested in case 17242 ? > > CaseInsensitiveOrder := AsciiOrder copy. > (0 to: 255) do:[ :v | > | char upper | > char := v asCharacter. > upper := char asUppercase. > upper isOctetCharacter > ifFalse: [ upper := char ]. > CaseInsensitiveOrder at: char asciiValue + 1 put: > (CaseInsensitiveOrder at: upper asciiValue + 1) ]. > > (the check for #isOctectCharacter is needed because for some entries > the correspondending > uppercase character is not within this character set). > > This would solve all three issues. > > > nicolai

Jan. 23, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] fef09a: 50540

by Ben Coman

On Sat, Jan 23, 2016 at 12:23 AM, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > > Le 22 janv. 2016 Ã 17:08, Ben Coman a Ã©crit : > > On Fri, Jan 22, 2016 at 11:26 PM, GitHub <noreply(a)github.com> wrote: > > Branch: refs/heads/5.0 > > Home: https://github.com/pharo-project/pharo-core > > Commit: fef09a7c252f92e255c5053927295a61d16b8395 > > > https://github.com/pharo-project/pharo-core/commit/fef09a7c252f92e255c50539… > > Author: Jenkins Build Server <board(a)pharo-project.org> > > Date: 2016-01-22 (Fri, 22 Jan 2016) > > > Log Message: > > ----------- > > 50540 > > Pharo > > > http://files.pharo.org/image/50/50540.zip > > > What are the issue numbers associated with this integration?? > > > Case 17446: Add registration/unregistration to/from session manager > Thanks. The additional question is why it didn't show up in the original post. cheers -ben

Jan. 23, 2016

Re: [Pharo-dev] Use cases for methods with optional parameters

by Ben Coman

Sounds interesting, but my head hurts trying to think about this more deeply :) so I'm going to keep at a superficial level on this for now. So just thinking out loud... If you have mother1 := foo:(bar:zork:fork) mother2 := foo:bar:(zork:bork:) When you search for senders of #foo:bar: what do you get back and how to display it? Maybe a two level tree list with the option combinations appearing at the top level and each of their senders at the second level, hiding any top level items that don't have children. foo:bar: foo:bar:zork: foo:bar:fork: foor:bar:bork foo:bar:zork:fork: foo:bar:fork:zork: foo:bar:zork:bork: foo:bar:bork:zork: Actually, full any order combination probably becomes unwieldly. Maybe there should be a constraint that optional arguments can be skipped but when used must be used in sequence. cheers -ben btw, how do you mean relationship? Do you mean using a Slots mechanism like the relationship demo in the Flexible Object layouts paper? https://hal.inria.fr/hal-00641716/file/Verw11b-OOSPLA11-FlexibleObjectLayou… On Sat, Jan 23, 2016 at 3:29 AM, stepharo <stepharo(a)free.fr> wrote: > Ben > > We were thinking also about reflection. > > > So may be we should introduce a relationship between the method and its > actual implementation. > > Imagine that > mother := foo:(bar:zork:) > mother children > foo:bar: > foo:bar:zork: > > then > senders (foo:bar:) > => > sender (motherOf(foo:bar:)) > > where motherOf is a back pointer from the expanded method into its mother > But it means that method using foo:bar: should somehow "mention" that they > will > use motherOf (foo:bar:). > > > > Le 22/1/16 01:41, Ben Coman a Ã©crit : > >> I don't have any use cases right now, but I'll keep my eyes open. But >> an example (that is maybe too basic to mess with) is the >> #at:ifAbsent: pattern. For example, the following would be >> "deleted" >> >> Dictionary>>.at: key >> ^ self at: key ifAbsent: [self errorKeyNotFound: key] >> >> and you would only have.... >> >> Dictionary>>at: key ifAbsent: aBlock >> <optional: ifAbsent default: [ self errorKeyNotFound: key]> >> >> The big in-Image example would be... >> >> TClass>> >> subclass: aName >> uses: aTraitCompositionOrArray >> instanceVariableNames: someInstanceVariableNames >> classVariableNames: someClassVariableNames >> poolDictionaries: someSharedPoolNames >> package: aCategory >> <optional: uses default: {}> >> <optional: instanceVariableNames default: ''> >> <optional: classVariableNames default: ''> >> <optional: poolDictionaries default:''> >> <optional: package 'Unclassified'> >> >> Now I wonder about senders & implementers searchability, and if >> "virtual" methods are generated in all combinations of optional >> parameters and show up in the system browser list, but show the "main" >> method as their source. > > >

Jan. 23, 2016

Re: [Pharo-dev] another spotter question

by David Allouche

> On 22 Jan 2016, at 11:08, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > > I was talking about clickable arrow to open preview ;) > Oh wow! I had no idea you click that area to toggle the preview! Even with the shift hints. At the very least, it needs something more in the shift hints than just a change in background color!

Jan. 22, 2016

Re: [Pharo-dev] running Hapao on the String class - error: key not found in MethodDictionary for testClassComment

by sheridan＠sheridan-mahoney.com

Hi Alejandro and Alexandro, Just wanted to let you know Hapao is working fine for me now...thanks for the help. Cheers, Sheridan Hi again! So I looked at the problem, wrote a fix, committed, created a new version and tested it. It should work out of the box :) Also the ConfigurationOfSpy should load Roassal by its own, so to download Hapao just run: ?? Gofer it smalltalkhubUser: 'ObjectProfile' project: 'Spy2'; configurationOf: 'Spy2'; loadStable. ?? Cheers! Alejandro > On Jan 19, 2016, at 4:25 PM, Alejandro Infante > <alejandroinfante91(a)gmail.com> wrote: Hi, So this is not problem of Spy2, but a bug of Hapao. There should be no problem instrumenting String with Spy2 if your profiler is correct, the proof of this is that the image does not explode when you were debugging the execution (I was actually able to open a browser and check the tests of String). This problem happened because we naively assumed, at least in this implementation Hapao, that for every Test Object there is a Test Method associated in the class of the Test Object. This is not correct for inherited tests, where the Test Method is in one of the superclasses. I will submit a fix for that as soon as possible ;) Thanks for the bug report!! Alejandro On Jan 19, 2016, at 8:58 AM, stepharo <stepharo(a)free.fr> wrote: Hi sheridan spy string can be a challenge. Now I was thikning recently that we should have tests for Ring. So if you are interested I would love to review your tests. Sef Le 18/1/16 22:45, sheridan(a)sheridan-mahoney.com a ?crit : Hi there, I am trying to use Hapao to check test coverage in the String class and have run across some trouble. To begin, I loaded Spy2 and Roassal2 using the following code: Gofer new smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; package: 'ConfigurationOfRoassal2'; load. (Smalltalk at: #ConfigurationOfRoassal2) load. Gofer it smalltalkhubUser: 'ObjectProfile' project: 'Spy2'; configurationOf: 'Spy2'; loadStable. Hapao then showed up in the "World" menu, and I selected it. I chose "Hapao @ class ... " and entered "String". Hapao starts running tests, but before long a debugger comes up with the error: KeyNotFound: key #testClassComment not found in MethodDictionary . IF I click "Proceed", other keyNotFound errors come up. This is in a 50524 image. Is there something wrong with the way I am invoking Hapao? Many thanks, Sheridan

Jan. 22, 2016

Re: [Pharo-dev] Use cases for methods with optional parameters

by stepharo

Ben We were thinking also about reflection. So may be we should introduce a relationship between the method and its actual implementation. Imagine that mother := foo:(bar:zork:) mother children foo:bar: foo:bar:zork: then senders (foo:bar:) => sender (motherOf(foo:bar:)) where motherOf is a back pointer from the expanded method into its mother But it means that method using foo:bar: should somehow "mention" that they will use motherOf (foo:bar:). Le 22/1/16 01:41, Ben Coman a Ã©crit : > I don't have any use cases right now, but I'll keep my eyes open. But > an example (that is maybe too basic to mess with) is the > #at:ifAbsent: pattern. For example, the following would be > "deleted" > > Dictionary>>.at: key > ^ self at: key ifAbsent: [self errorKeyNotFound: key] > > and you would only have.... > > Dictionary>>at: key ifAbsent: aBlock > <optional: ifAbsent default: [ self errorKeyNotFound: key]> > > The big in-Image example would be... > > TClass>> > subclass: aName > uses: aTraitCompositionOrArray > instanceVariableNames: someInstanceVariableNames > classVariableNames: someClassVariableNames > poolDictionaries: someSharedPoolNames > package: aCategory > <optional: uses default: {}> > <optional: instanceVariableNames default: ''> > <optional: classVariableNames default: ''> > <optional: poolDictionaries default:''> > <optional: package 'Unclassified'> > > Now I wonder about senders & implementers searchability, and if > "virtual" methods are generated in all combinations of optional > parameters and show up in the system browser list, but show the "main" > method as their source.

Jan. 22, 2016

Re: [Pharo-dev] [Vm-dev] Re: [ANN] Pharo bootstrap

by stepharo

Thanks eliot for this great description.

Jan. 22, 2016

Re: [Pharo-dev] [ANN] OSSubprocess v0.2.0 release

by Mariano Martinez Peck

On Fri, Jan 22, 2016 at 3:33 PM, stepharo <stepharo(a)free.fr> wrote: > ok I will reread it. > > OK, but do it quickly because it was mostly a "re-orgnization" than actually changing the contents. > > Le 20/1/16 21:57, Mariano Martinez Peck a Ã©crit : > > Stef, > > I made quite a re-organization of the readme..basically moved around a > couple of sections. I am working on the dev branch. > If you already started, don't worry, make the PR and I merge it. If you > did NOT yet started, then start from the dev branch :) > > BTW, this is how it looks the new readme in dev: > <https://github.com/marianopeck/OSSubprocess/tree/dev> > https://github.com/marianopeck/OSSubprocess/tree/dev > > On Wed, Jan 20, 2016 at 5:18 PM, Mariano Martinez Peck < > <marianopeck(a)gmail.com>marianopeck(a)gmail.com> wrote: > >> >> >> On Wed, Jan 20, 2016 at 5:11 PM, stepharo < <stepharo(a)free.fr> >> stepharo(a)free.fr> wrote: >> >>> Mariano your doc is gorgeous. >>> >>> I'm reading it and I will do a pull request with some typos! >>> >>> >> Thanks! That will be very much appreciated. Honestly, I could not spend >> much time in improving the "grammar / english" text of the doc. So any >> improvement in that area is appreciated! >> >> >> >> >>> >>> Le 20/1/16 02:06, Mariano Martinez Peck a Ã©crit : >>> >>> Hi guys, >>>> >>>> I am happy to announce OSSubprocess v0.2.0. You can see the changelog >>>> here: <https://github.com/marianopeck/OSSubprocess/releases/tag/v0.2.0> >>>> https://github.com/marianopeck/OSSubprocess/releases/tag/v0.2.0 >>>> Such version becomes the #stable, so the installation instructions >>>> remain the same. >>>> Note that I have improved and added more info in the documentation. >>>> >>>> I took into account most of the feedback I received in the first >>>> release plus some other stuff from the survey. >>>> >>>> If you have more feedback, just let me know! >>>> >>>> Hope you enjoy. >>>> >>>> Best, >>>> >>>> -- >>>> Mariano >>>> http://marianopeck.wordpress.com >>>> >>> >>> >>> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > > > -- > Mariano > http://marianopeck.wordpress.com > > > -- Mariano http://marianopeck.wordpress.com

Jan. 22, 2016

Re: [Pharo-dev] [ANN] OSSubprocess v0.2.0 release

by stepharo

ok I will reread it. Le 20/1/16 21:57, Mariano Martinez Peck a Ã©crit : > Stef, > > I made quite a re-organization of the readme..basically moved around a > couple of sections. I am working on the dev branch. > If you already started, don't worry, make the PR and I merge it. If > you did NOT yet started, then start from the dev branch :) > > BTW, this is how it looks the new readme in dev: > https://github.com/marianopeck/OSSubprocess/tree/dev > > On Wed, Jan 20, 2016 at 5:18 PM, Mariano Martinez Peck > <marianopeck(a)gmail.com <mailto:marianopeck@gmail.com>> wrote: > > > > On Wed, Jan 20, 2016 at 5:11 PM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Mariano your doc is gorgeous. > > I'm reading it and I will do a pull request with some typos! > > > Thanks! That will be very much appreciated. Honestly, I could not > spend much time in improving the "grammar / english" text of the > doc. So any improvement in that area is appreciated! > > > > Le 20/1/16 02:06, Mariano Martinez Peck a Ã©crit : > > Hi guys, > > I am happy to announce OSSubprocess v0.2.0. You can see > the changelog here: > https://github.com/marianopeck/OSSubprocess/releases/tag/v0.2.0 > Such version becomes the #stable, so the installation > instructions remain the same. > Note that I have improved and added more info in the > documentation. > > I took into account most of the feedback I received in the > first release plus some other stuff from the survey. > > If you have more feedback, just let me know! > > Hope you enjoy. > > Best, > > -- > Mariano > http://marianopeck.wordpress.com > > > > > > > -- > Mariano > http://marianopeck.wordpress.com > > > > > -- > Mariano > http://marianopeck.wordpress.com

Jan. 22, 2016

Re: [Pharo-dev] another spotter question

by stepharo

Le 22/1/16 11:08, Aliaksei Syrel a Ã©crit : > > I was talking about clickable arrow to open preview ;) > Ok I thought that you also talked about the other. For this one, I would just put a little triangular icon on top and going the in same orientation because then this is clear that this is a kind of button. > On Jan 22, 2016 10:47 AM, "stepharo" <stepharo(a)free.fr > <mailto:stepharo@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 >>> <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