- Pharo-dev - lists.pharo.org

[Pharo-project] Issue 3289 in pharo: FinderUI>>initialize (searchedTextListMaxSize is Undeclared
by pharo＠googlecode.com Nov. 25, 2010

Nov. 25, 2010

Status: Fixed Owner: marcus.denker Labels: Milestone-1.2 New issue 3289 by marcus.denker: FinderUI>>initialize (searchedTextListMaxSize is Undeclared http://code.google.com/p/pharo/issues/detail?id=3289 fix attached (not used anywhere) Attachments: Finder.1.cs 200 bytes

1 2

[Pharo-project] Issue 3287 in pharo: Class builder depends on Scanner
by pharo＠googlecode.com Nov. 25, 2010

Nov. 25, 2010

Status: Accepted Owner: Benjamin.VanRyseghem.Pharo New issue 3287 by Benjamin.VanRyseghem.Pharo: Class builder depends on Scanner http://code.google.com/p/pharo/issues/detail?id=3287 ClassBuilder depends on Scanner because a new Scanner is used each time the code needs to parse a string and to create an array with each words ... I've change this by string subStrings: ' ' Attached : cs file Attachments: ClassScannerReferences.1.cs 8.6 KB

1 2

Re: [Pharo-project] [DEBIAN] latest standard vm package
by Alexander LazareviÄ Nov. 25, 2010

Nov. 25, 2010

Again FWIW I've built a new vm available at http://www.lazarevic.de/download/squeak/squeak-vm_4.3.18.2330-1_i386.deb It's basically the same as the one before only updated to VMMaker 4.3.18 and that it now includes the Cryptography plugins DESPlugin MD5Plugin SHA256Plugin and an updated DSAPlugin All the Cryptography-Tests did run fine with this vm. Cheers, Alex PS: Once I know how to properly use the debian tools I will also provide the source package. Currently I don't know why it does not built a orig and a diff file ... PPS: Again provided as is, no guaranties, no nothing, nada

1 0

[Pharo-project] Fwd: [Metacello] symbolic version proof of concept...
by StÃ©phane Ducasse Nov. 25, 2010

Nov. 25, 2010

Over the last few days I've been working on converting ConfigurationOfOmniBrowser and the configurations it depends upon (ConfigurationOfRefactoringBrowser, ConfigurationOfShout, and ConfigurationOfOCompletion) to use symbolic versions. The results are stashed away in a repository on the Bibliocello site: http://a-bibliocello.gemstone.com/bibliocello/projects/Pharo/repository/Exp… With Metacello 1.0-beta.28 loaded you can execute the following expression in a PharoCore1.0, PharoCore1.1, or PharoCore1.2 image and the appropriate versions of OmniBrowser and the supporting proejcts will be loaded: (ConfigurationOfOmniBrowser project version: #stable) load: 'Tests'. So far I have been using only the 'Tests' group because ... well I want to verify that the code not only loads, but passes all of the tests (for the loaded projects) in each image and the results are: PharoCore1.0: 1221 run, 1218 passes, 3 expected failures, 0 failures, 0 errors, 0 unexpected passes PharoCore1.1: 1325 run, 1324 passes, 1 expected failures, 0 failures, 0 errors, 0 unexpected passes PharoCore1.2: 814 run, 813 expected passes, 0 expected failures, 0 failures, 1 errors, 0 unexpected passes, and deprecation warnings For Pharo1.2, OB-Refactory is not loaded, because it doesn't appear to have been ported to Pharo1.2 yet ... If you want to look at what I've done you can compare the latest version of the config with the earliest version of the config in the repository ... I'll be glad to explain any changes that don't make sense to you. All four configs also run clean against the Metacello validator .... I've developed a set of scripts (in MetacelloToolBox) that I have been using to automate the process of determining which versions in a particular configuration load cleanly into an image and if the tests pass as well (including checking for deprecation warnings). The following expression when executed in a PharoCore1.0.x image will load each version in the configuration and run the tests (loading the 'Tests' group if it is defined): (MetacelloToolBox validatePlatformLoad: #'pharo1.0.x' for: 'OmniBrowser') explore. Right now, that script will automatically update the development and stable symbolic version definitions as well as mark versions as #release if the 'Tests' group loads without errors or deprecation warnings and passes all of the tests (without deprecation warnings). It also produces an 'issues list' that describes the individual errors, critical warnings and warnings for each version ... much like the validator with added information about tests. I expect to continue working my way through the various configurations with the goal to automate as much of the validation and analysis as possible... Dale

1 0

Re: [Pharo-project] Issue 3291 in pharo: Missing text field with completion
by StÃ©phane Ducasse Nov. 25, 2010

Nov. 25, 2010

tx alain this is important to improve basic widgets because they will have a big impact. Stef On Nov 25, 2010, at 8:14 AM, Alain Plantec wrote: > Hi Lukas, > ok, I've plugged the textfield with completion (surely a bad name) in the find class for testing only. > I don't like the two lists also. > The purpose is to have a normal text field which popup a list of possible answers only > when you typin something in the field. > So, its a basic widget which, afaik is missing and that could be used with ob-tools. > btw: even with ob find class, add category, etc, I would prefer to see only one simple text field. > Cheers > Alain > > Le 25/11/2010 00:33, Lukas Renggli a Ã©crit : >> Why two lists when one list is enough? >> >> http://www.lukas-renggli.ch/blog/ob-completion-dialog >> >> Lukas >> >> On 24 November 2010 19:08, Alain Plantec<alain.plantec(a)free.fr> wrote: >>> Dear list, >>> I'm not should it's enough clear so >>> a screenshot is attached. >>> Cheers >>> Alain >>> >> >> > >

1 0

Re: [Pharo-project] Issue 3266 in pharo: Clean TextEditor
by StÃ©phane Ducasse Nov. 25, 2010

Nov. 25, 2010

Now I will see who will port/rewrite what we have on top of a cleaned SimpleMorphic. > StÃ©phane Ducasse wrote: >> Indeed. I mean >> I can't help, but feel free to go ahead >> >> Stef >> >> > Great! Thanks for the clarification. > > Cheers, > Juan Vuletich >

1 0

Re: [Pharo-project] Issue 3266 in pharo: Clean TextEditor
by StÃ©phane Ducasse Nov. 25, 2010

Nov. 25, 2010

this is just for state. You have traits for methods. For me the way to go is first clean the classbuilder, have first class instance variables, what you want is just hashSubclass: instead of variableSubclass: Stef > > IMO SimpleMorphic, minus 'color' ivar in Morph class is a way to go. >>> (i mean get rid that 'color' thing in base class) :) >>> >>> >> >> Yep. I fully agree. >> > I think, for things like Morphic, where there are dozens of various > properties expected > to be in basic morph class, we should use dictionaries, backed up by > clever VM semantics. > I cannot stop thinking about extending object format to allow a > dynamic number of slots per object, > like in self or javascript. > > >> Cheers, >> Juan Vuletich >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. >

1 0

Nov. 25, 2010

let's start writing a lot of scripts with coral and fixing the infrastructure and see. > Very nice! I installed it according to the instructions (http://www.auverlot.fr/pharo/coralinstall/) and it works. > > I guess the next step is to have a class for the scripts? So that one can define methods and have pre-defined > methods to ease script-writing... why? For now we want coral syntax to be potentially a replacement to the chunk format. and learn. In GNU you do not need to have a script class to write code. > Small edit for the readme: > > -> "3) make them executable: chmod +x coral.sh coraldb.sh" > ==> is now called coralDebug.sh > > > On Nov 24, 2010, at 2:53 PM, Olivier Auverlot wrote: > >> New methods for displaying in a UNIX console : >> >> * Console>>displayAttributes: >> * Console>>eraseScreen >> * Console>>esc: >> * Console>>locate: >> * Console>>plot: >> * Console>>resetAllAttributes >> >> Two examples: >> >> * scriptCarpet.cst >> * scriptHappyFace.cst >> >> Best regards >> Olivier >> >> www.auverlot.fr >> > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-coral mailing list > Pharo-coral(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-coral

1 0

Re: [Pharo-project] Fwd: [Pharo-users] TestMock: a full featured mock testing framework now available in SqueakSource
by StÃ©phane Ducasse Nov. 25, 2010

Nov. 25, 2010

So dennis squared it would be good that you write this chapter. I can help editing and reviewing it. Start examples first It would be a good addition for the community. At the end we should all produce more documentation. Stef On Nov 24, 2010, at 7:33 PM, Dennis Schetinin wrote: > > By the way dennis did you start to write a chapter on Mocks? > > Stef > > > Well, actually I'm another Dennis :) I think you talked about the Mocks chapter with Dennis Kudryashov, author of Mocketry. > > On the other hand, he was my student, we still stay in touch with him and decided to work together on the topic. We didn't make much progress so far unfortunately, but we have a plan for the chapter and about 50% of text in Russian. > > -- > Dennis Schetinin

1 0

Re: [Pharo-project] Update for Coral
by Marcus Denker Nov. 24, 2010

Nov. 24, 2010

Hello Olivier, Very nice! I installed it according to the instructions (http://www.auverlot.fr/pharo/coralinstall/) and it works. I guess the next step is to have a class for the scripts? So that one can define methods and have pre-defined methods to ease script-writing... Small edit for the readme: -> "3) make them executable: chmod +x coral.sh coraldb.sh" ==> is now called coralDebug.sh On Nov 24, 2010, at 2:53 PM, Olivier Auverlot wrote: > New methods for displaying in a UNIX console : > > * Console>>displayAttributes: > * Console>>eraseScreen > * Console>>esc: > * Console>>locate: > * Console>>plot: > * Console>>resetAllAttributes > > Two examples: > > * scriptCarpet.cst > * scriptHappyFace.cst > > Best regards > Olivier > > www.auverlot.fr > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1