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

Re: [Pharo-project] Spell check test cases

by Stan Shepherd

Lukas Renggli wrote: > >> Glad you like the tests. >> >> In my version of RBSpellChecker>>normalize, I also commented out the >> line: >> Â Â Â Â "or: [ input peek = $' ]" "this causes false positives eg 'OK' in >> class >> comments" > > That change breaks word like > > don't > Smalltalk's > etc. > > I see that there are a few other cases where you don't want any $'. > So I removed it for now. > >> OK returns an error on k, RB b etc. >> >> So that's what causes the two cases on a Linux box (fairly sure). I'm >> guessing you have letters k i b and t in the Mac dictionary, or it >> specifically doesn't check one letter words? > > RBSpellChecker>>#normalize: removes one letter words, so I don't think > this can be the error. If you show the individual words that are > checked against the dictionary on the transcript, you will see that > they all look pretty ok. > >> BTW, it looks like RBPoolVariableNameSpellingRule should be >> RBPoolDictionaryNameSpellingRule, as that's what it looks at? > > Ok, I renamed that. Probably this rule isn't really needed anyway ... > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > Hi Lukas, I think you didn't pick up the other fix in RBBugFixes RBLiteralValuesSpellingRule>>initialize super initialize. matcher := RBParseTreeSearcher new. matcher matches: '`#literal' do: [ :node :answer | | nodeValue | nodeValue := node value. (nodeValue isString or: [ nodeValue isSymbol or: [ nodeValue isCollection ] ]) ifTrue: [ answer add: nodeValue ]. answer ] Currently it checks the node, not the node value. When I load this method, all tests run green. > RBSpellChecker>>#normalize: removes one letter words, so I don't think > this can be the error. > The tests are on 'RB' 'OK' etc, in the quotes in class comments. Leading capitals are stripped off. If $' is passed through, the check gets made on K', and as it is 2 characters doesn't get disallowed. That's why the tests need the pass through of ' taken out at the moment. If instead, where you store the result: result add: output contents if you strip out trailing $' before storing, this would let you verify don't and smalltalk's as well, I think. Then you'd need a different test from the position in the stream for size = 1. I only hit this edge case because I had a class comment about namespace related prefixes- 'WA' 'RB' etc. So now 'OK' is not checked, under the 'strip out leading capitals' scenario. At some point it might be nice to check these as well - eg WARenderCanvas rather than WBRenderCanvas. YAGNI, NASA, other abbreviations. Code Critics browser still doesn't show Method Protocols in bold. Cheers, ...Stan -- View this message in context: http://n2.nabble.com/Spell-check-test-cases-tp4288633p4290734.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 12, 2010

[Pharo-project] Issue 1782 - Save Dialog too small: fixed and ready

by Torsten Bergmann

It was annoying with the current image names, so I fixed it: http://code.google.com/p/pharo/issues/detail?id=1782 Bye T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

Jan. 12, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Serge Stinckwich

Thank you for your good work Mariano. I use your image for my development right now. The inspector is crashing in unexpected ways. Just try : #(1 2 3 4 5 6 7 9 10) inspect. and in the panel below on the right, just evaluate for example : 3+7 with CTRL-D several times. After a while, the following screen appears. 2010/1/10 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Hi Folks/Beta-Testers! > > I have prepare a new PharoDev image. This image, has same differences with > the previous ones that you should know: > > 1) This is the first Dev image I ever prepare. I adapt to Mac OS Damien's > bash scripts to build them and I also cleanup all the Squeak stuff from > those bash scripts. So, maybe there are some problems. Forgive me if this is > the case. I would like you to check, not only the Image in itself but also > the zip. The package.txt, changelog, the fonts, etc. > > 2) This image puts TrueType fonts again. We won't put StrikeFonts or DejaVu > package until there is big bug with them. We know those fonts are faster, > but still a bit buggy. If you fix those issues, cool! > > 3) This image DOES NOT include O2. I know there are a lot of people who use > it (mostly in Moose), but unfortunately, this was a decision taken. O2 > depends and overrides OB making this more unstable sometimes. The same as > the TrueType, we will put O2 again when this can be perfectly load in a > PharoCore image without anything about OB. > Sorry, but we rather affect only O2 users and not all. If you want packages > support, then help in O2 development. > > 4) In previous Dev images only tests from PharoCore were included. Now, it > also includes the tests from the external packages loaded. > > 5) This image was build using Metacello configurations. If you want, compare > the installScript.st from this image to the previous one. > > 6) There is no Web image this time. If you want to install Seaside 2.8.4 > evaluate: > > Gofer new > Â Â Â squeaksource: 'MetacelloRepository'; > Â Â Â package: 'ConfigurationOfSeaside28'; > Â Â Â load. > > (Smalltalk at: #ConfigurationOfSeaside28) load > > And if you want Seaside 3.0 evaluate: > > Gofer new > Â Â Â squeaksource: 'MetacelloRepository'; > Â Â Â package: 'ConfigurationOfSeaside30'; > Â Â Â load. > > (Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion > > However, I am not sure if this is perfectly working in Pharo. > > > > Ok .... Here is the link: > https://gforge.inria.fr/frs/download.php/25156/pharo1.0-10505-rc1dev10.01.1… > > I will wait a couple of days now and I will also start to use this image for > my development. If there are issues, report them. If we have big issues, > this image is not release. On the other hand, if it works well, we release > it. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/

Jan. 12, 2010

Re: [Pharo-project] Etymology of #perform:?

by Nicolas Cellier

2010/1/12 Adrian Kuhn <akuhn(a)iam.unibe.ch>: > Smalltalk is based on message sending, but sending a method is called #perform: > Â rather than #send:? When I read aloud the code is it "perform a message" or > Â "perform a method", both seem to be wrong. The first since, well, methods are > Â sent not performed. And the second since, well, the argument is a message and a > Â not a method. What is the etymology or rational for this? Maybe if one of the > Â old Smalltalkers (or Marcus with his awesome knowledge of Smalltalk history) > Â can elaborate on this? > > --AA > If you analyze messages pattern, you see there is no sender but only a receiver... Thus, it's obviously not #send:, you don't tell the receiver to send, only to receive... The receiver receives and then perform a method indeed. Another point of view would have been thisContext send: aMessage to: receiver. But it's not how we write things. Nicolas > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 12, 2010

Re: [Pharo-project] [ANN] WorkingSet

by Mariano Martinez Peck

On Tue, Jan 12, 2010 at 10:44 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > > Maybe there is stuff that it is not just related to OB but to other > stuff. > > For example > > > > DEVToolSet >> openWorkspace refers to Shout Workspace. > > Yeah, it depends on all kinds of unrelated things. > > > But maybe it is a good idea to build a OBToolsSet. I have no idea. > > Then the problem is that you cannot combine different tools. > DEVToolSet just works for the dev images because it has tons of checks > if certain classes are present in the system. > > Yes, I know. It doesn't work if you don't have loaded all that stuff :( I don't know how to fix it. > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 12, 2010

Re: [Pharo-project] [ANN] WorkingSet

by Damien Cassou

On Tue, Jan 12, 2010 at 10:24 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > I see, you do that in DEVToolSet. I wonder why this class is not part of OB? Take what you want from DEVToolSet and put it in an OBToolSet. Then, when someone builds an image, he can combine different things from different tool sets if he wants to. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Jan. 12, 2010

Re: [Pharo-project] Object Buffer (implementation tryout)

by Lukas Renggli

> VW had this and I miss it all the times in Pharo. Dragging an object from an > Â inspector to a workspace is just so convenient, priceless! OBTools has that since the beginning. Somebody would need to spend some time on these tools though to make them really useful. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 12, 2010

Re: [Pharo-project] [ANN] WorkingSet

by Lukas Renggli

> Maybe there is stuff that it is not just related to OB but to other stuff. > For example > > DEVToolSet >> openWorkspaceÂ Â refers to Shout Workspace. Yeah, it depends on all kinds of unrelated things. > But maybe it is a good idea to build a OBToolsSet. I have no idea. Then the problem is that you cannot combine different tools. DEVToolSet just works for the dev images because it has tons of checks if certain classes are present in the system. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 12, 2010

Re: [Pharo-project] [ANN] WorkingSet

by Mariano Martinez Peck

On Tue, Jan 12, 2010 at 10:24 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > >>>> That's strange, since I use Toolset for these queries. Should I use > something else? > >>> > >>> I am using OB, but I get the old system browser in some cases: for > >>> senders, implementors and sets of classes. > >> > >> What ToolSet do you use? In the Pharo images, the ToolSet I install > >> takes care of launching OB in all cases. > > > > OBSystemBrowserAdaptor > > I see, you do that in DEVToolSet. I wonder why this class is not part of > OB? > Maybe there is stuff that it is not just related to OB but to other stuff. For example DEVToolSet >> openWorkspace refers to Shout Workspace. But maybe it is a good idea to build a OBToolsSet. I have no idea. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 12, 2010

Re: [Pharo-project] Object Buffer (implementation tryout)

by Adrian Kuhn

Damien Pollet <damien.pollet@...> writes: > drag-n-drop variables between workspaces etc +1 drag and drop would be nice indeed. VW had this and I miss it all the times in Pharo. Dragging an object from an inspector to a workspace is just so convenient, priceless! --AA

Jan. 12, 2010