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

Re: [Pharo-project] RBScanner>>#initializeClassificationTable

by Henrik Johansen

On Nov 25, 2010, at 11:12 59AM, Henrik Johansen wrote: > > On Nov 25, 2010, at 10:58 44AM, Benjamin wrote: > >> Hello guys, >> >> Is there a reason this method use : >> >> (Scanner isLiteralSymbol: '_') >> ifTrue: [ self initializeChars: '_' to: #alphabetic ] >> ifFalse: [ self initializeChars: '_' to: #special ]. >> >> and not >> >> (Scanner allowUnderscoreAsAssignment) >> ifTrue: [ self initializeChars: '_' to: #special ] >> ifFalse:[ self initializeChars: '_' to: #alphabetic ] >> >> ? >> >> >> Cheers, >> >> Ben > > Compatibility I would guess. > In Squeak, allowUnderscoreAsAssignment is still a Preferences method. > > Cheers, > Henry > P.S. At the very least it could be changed to Scanner isLiteralSymbol: #_ :)

Nov. 25, 2010

Re: [Pharo-project] RBScanner>>#initializeClassificationTable

by Henrik Johansen

On Nov 25, 2010, at 10:58 44AM, Benjamin wrote: > Hello guys, > > Is there a reason this method use : > > (Scanner isLiteralSymbol: '_') > ifTrue: [ self initializeChars: '_' to: #alphabetic ] > ifFalse: [ self initializeChars: '_' to: #special ]. > > and not > > (Scanner allowUnderscoreAsAssignment) > ifTrue: [ self initializeChars: '_' to: #special ] > ifFalse:[ self initializeChars: '_' to: #alphabetic ] > > ? > > > Cheers, > > Ben Compatibility I would guess. In Squeak, allowUnderscoreAsAssignment is still a Preferences method. Cheers, Henry

Nov. 25, 2010

Re: [Pharo-project] Issue 3290 in pharo: TextEditor>>disregardNextMouseUp (oldInterval is Undeclared)

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3290 by marcus.denker: TextEditor>>disregardNextMouseUp (oldInterval is Undeclared) http://code.google.com/p/pharo/issues/detail?id=3290 12254

Nov. 25, 2010

[Pharo-project] RBScanner>>#initializeClassificationTable

by Benjamin

Hello guys, Is there a reason this method use : (Scanner isLiteralSymbol: '_') ifTrue: [ self initializeChars: '_' to: #alphabetic ] ifFalse: [ self initializeChars: '_' to: #special ]. and not (Scanner allowUnderscoreAsAssignment) ifTrue: [ self initializeChars: '_' to: #special ] ifFalse:[ self initializeChars: '_' to: #alphabetic ] ? Cheers, Ben

Nov. 25, 2010

[Pharo-project] [update 1.2] #12254

by Marcus Denker

12254 ----- Issue 3287: Class builder depends on Scanner Issue 3289: FinderUI>>initialize (searchedTextListMaxSize is Undeclared Issue 3290: TextEditor>>disregardNextMouseUp (oldInterval is Undeclared) -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Nov. 25, 2010

Re: [Pharo-project] Issue 3289 in pharo: FinderUI>>initialize (searchedTextListMaxSize is Undeclared

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3289 by marcus.denker: FinderUI>>initialize (searchedTextListMaxSize is Undeclared http://code.google.com/p/pharo/issues/detail?id=3289 12254

Nov. 25, 2010

Re: [Pharo-project] Issue 3287 in pharo: Class builder depends on Scanner

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3287 by marcus.denker: Class builder depends on Scanner http://code.google.com/p/pharo/issues/detail?id=3287 12254

Nov. 25, 2010

Re: [Pharo-project] [DEBIAN] latest standard vm package

by Alexander LazareviÄ

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

Nov. 25, 2010

[Pharo-project] Fwd: [Metacello] symbolic version proof of concept...

by StÃ©phane Ducasse

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

Nov. 25, 2010

Re: [Pharo-project] Issue 3291 in pharo: Missing text field with completion

by StÃ©phane Ducasse

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 >>> >> >> > >

Nov. 25, 2010