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

[Pharo-project] Fwd: [Metacello] Re: symbolic version proof of concept...
by Dale Henrichs Nov. 25, 2010

Nov. 25, 2010

-------- Original Message -------- Subject: [Metacello] Re: symbolic version proof of concept... Date: Thu, 25 Nov 2010 08:02:41 -0800 From: Dale <dhenrich(a)vmware.com> Reply-To: metacello(a)googlegroups.com <metacello(a)googlegroups.com> To: Metacello <metacello(a)googlegroups.com> Doru, If you want to try out the load you need to do a couple of things: Gofer new gemsource: 'metacello'; package: 'ConfigurationOfMetacello'; load. Then: (ConfigurationOfMetacello project version: '1.0-beta.28') load. Followed by: Gofer new url: 'http://a-bibliocello.gemstone.com/bibliocello/projects/Pharo/ repository/Experiment1/MetacelloRepository'; package: 'ConfigurationOfGofer'; package: 'ConfigurationOfRefactoringBrowser'; package: 'ConfigurationOfShout'; package: 'ConfigurationOfOCompletion'; package: 'ConfigurationOfOmniBrowser'; load. That way you've got all of the new configurations preloaded in your image. And then: (ConfigurationOfOmniBrowser project version: #stable) load. Sorry about not including these instructions in the original message:( Dale On Nov 25, 5:10 am, Tudor Girba <tudor.gi...(a)gmail.com> wrote: > Hi, > > I tried: > Gofer new > url: 'http://a-bibliocello.gemstone.com/bibliocello/projects/Pharo/reposito... > package: 'ConfigurationOfOmniBrowser'; > load. > ((Smalltalk at: #ConfigurationOfOmniBrowser) project version: #stable) load: 'Tests'. > > But the (ConfigurationOfOmniBrowser project version: #stable) is nil. > > Cheers, > Doru > > On 25 Nov 2010, at 12:21, Alexandre Bergel wrote: > > > > > Is there a short description of symbolic versions somewhere? > > > Alexandre > > > On 24 Nov 2010, at 21:46, Dale wrote: > > >> 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/reposito... > > >> 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 > > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > --www.tudorgirba.com > > "In a world where everything is moving ever faster, > one might have better chances to win by moving slower."

1 1

[Pharo-project] Issue 3324 in pharo: Closing find dialog does not reinstate top window
by pharo＠googlecode.com Nov. 25, 2010

Nov. 25, 2010

Status: Fixed Owner: gazzaguru2 CC: aplantec, marcus.denker Labels: Milestone-1.2 New issue 3324 by gazzaguru2: Closing find dialog does not reinstate top window http://code.google.com/p/pharo/issues/detail?id=3324 Closing "find & replace" doe not return focus to a system window. Fix attached. Attachments: TopWindowFix.1.cs 427 bytes

1 2

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

Nov. 25, 2010

lukas could you publish CompletionRequest somewhere in a place like a bug entry so that we integrate it :) Stef > Le 25/11/2010 12:03, Lukas Renggli a Ã©crit : >>> So, its a basic widget which, afaik is missing and that could be used with >>> ob-tools. >> I don't follow what you and Francisco are saying. >> >> IMHO there is a much better widget already in OB. > sorry but why much better? > OBCompletionRequest is a dialog. > What I propose is to enrich PluggableTextFieldMorph > with the possibility to use a completion list. > So we have two differents things here. > And indeed, OBCompletionRequest should be named CompletionRequest > and integrated in the core. > Showing it in the browser find class was not a good idea... > Cheers > Alain > >> I suggest to make >> that a standard widget so that other tools outside of OB can take >> advantage too. >> >> It is simple subclass of DialogWindow morph from Polymorph and can be >> fully configured and opened for example like this: >> >> OBCompletionRequest new >> prompt: 'Find Class'; >> searchBlock: [ :string | self findClassIn: target environment >> pattern: string ]; >> labelBlock: [ :class | class name ]; >> iconBlock: [ :class | class browserIcon ]; >> signal >> >> Lukas >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> >> >> > >

2 1

Re: [Pharo-project] Issue 3181 in pharo: PharoCorePackageDependenciesTests failure and error
by pharo＠googlecode.com Nov. 25, 2010

Nov. 25, 2010

Updates: Status: Fixed Comment #3 on issue 3181 by marcus.denker: PharoCorePackageDependenciesTests failure and error http://code.google.com/p/pharo/issues/detail?id=3181 (No comment was entered for this change.)

1 2

[Pharo-project] Issue 3293 in pharo: UITheme examples broken
by pharo＠googlecode.com Nov. 25, 2010

Nov. 25, 2010

Status: Fixed Owner: gazzaguru2 CC: nicolas.cellier.aka.nice, marcus.denker Labels: Milestone-1.2 New issue 3293 by gazzaguru2: UITheme examples broken http://code.google.com/p/pharo/issues/detail?id=3293 Due to Color>>wheel: refactoring. Fix CS attached. Attachments: ThemeExampleFixes.1.cs 8.8 KB

1 1

[Pharo-project] [update 1.2] #12255
by Marcus Denker Nov. 25, 2010

Nov. 25, 2010

12255 ----- Issue 3324: Closing find dialog does not reinstate top window Issue 3318: DropList positioning to fit display Issue 3292: SourceReference>>parseTimestampFrom: chokes on tk 2/18/97 Issue 3293: UITheme examples broken Issue 3181: PharoCorePackageDependenciesTests failure and error -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3318 in pharo: DropList positioning to fit display
by pharo＠googlecode.com Nov. 25, 2010

Nov. 25, 2010

Status: Fixed Owner: gazzaguru2 CC: aplantec, marcus.denker Labels: Milestone-1.2 New issue 3318 by gazzaguru2: DropList positioning to fit display http://code.google.com/p/pharo/issues/detail?id=3318 Attached - when a drop list has insufficient room to show the full list below it, show above instead. Fixed corner rounding when list shown/hidden. Just trying to keep on top of the small details ;-) Regards, Gary. Attachments: DropListPositioning.1.cs 1.9 KB

1 1

[Pharo-project] Issue 3325 in pharo: SourcedMethodReference bug due to parseTimestampFrom:
by pharo＠googlecode.com Nov. 25, 2010

Nov. 25, 2010

Status: Accepted Owner: Benjamin.VanRyseghem.Pharo New issue 3325 by Benjamin.VanRyseghem.Pharo: SourcedMethodReference bug due to parseTimestampFrom: http://code.google.com/p/pharo/issues/detail?id=3325 aString = 'tk 1/8/97' parseTimestampFrom: aString "Parse a date-time from a timestamp-string that is extracted from a source file. If there is no timestamp, we return a very old time" ^ aString isEmpty ifTrue:[DateAndTime new] ifFalse:[(((aString subStrings: ' ') last: 2) joinUsing: Character space) asDateAndTime] It crashes

1 3

[Pharo-project] RBScanner>>#initializeClassificationTable
by Benjamin Nov. 25, 2010

Nov. 25, 2010

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

3 6

Nov. 25, 2010

Oscar There are only a few really really newbies questions. Then we like newbies and their questions because we learned all a lot from them. So this is not because we may talk about stuff that looks complex that - they are (often this is just that we do not have enough time to understand) - we know everything - we do not like to reply to simple questions - we do not like to learn from answer to simple questions. So keep asking questions and having fun with us. I hate those mailing-lists where people are asked to do their homework. :) Stef

1 0