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

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

by Dale Henrichs

Oh, one other thing ... Metacello1.0-beta.28 has not been released yet, it's a development version so I recommend that for now you only use 1.0-beta.28 for experimenting with symbolicVersions ... Dale On 11/25/2010 10:30 AM, Dale Henrichs wrote: > > > -------- 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." >

Nov. 25, 2010

Re: [Pharo-project] Issue 1970 in pharo: ProtoObject does not define #instVarNamed:, causes problem when using Inspector & SFuture

by pharo＠googlecode.com

Updates: Status: Closed Comment #11 on issue 1970 by marcus.denker: ProtoObject does not define #instVarNamed:, causes problem when using Inspector & SFuture http://code.google.com/p/pharo/issues/detail?id=1970 (No comment was entered for this change.)

Nov. 25, 2010

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

by Dale Henrichs

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

Nov. 25, 2010

Re: [Pharo-project] Issue 2734 in pharo: Conflict between Shout and PluggableTextMorph in Pharo 1.2

by pharo＠googlecode.com

Updates: Status: Closed Comment #6 on issue 2734 by marcus.denker: Conflict between Shout and PluggableTextMorph in Pharo 1.2 http://code.google.com/p/pharo/issues/detail?id=2734 I think this has been fixed

Nov. 25, 2010

Re: [Pharo-project] Issue 3324 in pharo: Closing find dialog does not reinstate top window

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3324 by marcus.denker: Closing find dialog does not reinstate top window http://code.google.com/p/pharo/issues/detail?id=3324 12255

Nov. 25, 2010

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

by Francisco Ortiz PeÃ±aloza

Hi, as ppl use to say a picture is *worth a thousand words (or two thousands in bad written english)* Imho it should look like this, without the static list and with recently used on top :) Francisco ** [image: findClassCompletion.png] ** ---------- Forwarded message ---------- From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> Date: Thu, Nov 25, 2010 at 2:23 PM Subject: Re: [Pharo-project] Issue 3291 in pharo: Missing text field with completion To: Pharo-project(a)lists.gforge.inria.fr, alain.plantec(a)free.fr 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 >> >> >> > >

Nov. 25, 2010

Re: [Pharo-project] Issue 3324 in pharo: Closing find dialog does not reinstate top window

by pharo＠googlecode.com

Comment #2 on issue 3324 by marcus.denker: Closing find dialog does not reinstate top window http://code.google.com/p/pharo/issues/detail?id=3324 12255

Nov. 25, 2010

Re: [Pharo-project] Issue 3181 in pharo: PharoCorePackageDependenciesTests failure and error

by pharo＠googlecode.com

Comment #5 on issue 3181 by marcus.denker: PharoCorePackageDependenciesTests failure and error http://code.google.com/p/pharo/issues/detail?id=3181 I removed the Announcements tests, as there is not one package Announcements but multiple ones.

Nov. 25, 2010

Re: [Pharo-project] Issue 3181 in pharo: PharoCorePackageDependenciesTests failure and error

by pharo＠googlecode.com

Updates: Status: Closed Comment #4 on issue 3181 by marcus.denker: PharoCorePackageDependenciesTests failure and error http://code.google.com/p/pharo/issues/detail?id=3181 I removed the Announcements tests, as there is not one package Announcements but multiple ones.

Nov. 25, 2010

Re: [Pharo-project] Issue 3293 in pharo: UITheme examples broken

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3293 by marcus.denker: UITheme examples broken http://code.google.com/p/pharo/issues/detail?id=3293 12255

Nov. 25, 2010