- Pharo-dev - lists.pharo.org

[Pharo-project] pharo-2.0-tests Â» win - Build # 427 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Oct. 20, 2012

[Pharo-project] [update 2.0] #20355

by Marcus Denker

20355 ----- Issue 6849: SystemDictionary should not use nil as a sortBlock http://code.google.com/p/pharo/issues/detail?id=6849 Issue 6838: Undeclareds in Jenkins test runner http://code.google.com/p/pharo/issues/detail?id=6838 Issue 6837: Failing test: Undeclared in MetacelloPlatform>>createRepository: http://code.google.com/p/pharo/issues/detail?id=6837 Issue 6833: Failing test: ConfigurationCommandLineHandlerTest http://code.google.com/p/pharo/issues/detail?id=6833 Diff information: http://ss3.gemstone.com/ss/Pharo20/System-Support-MarcusDenker.725.diff http://ss3.gemstone.com/ss/Pharo20/SUnit-UI-MarcusDenker.45.diff http://ss3.gemstone.com/ss/Pharo20/SUnit-Core-MarcusDenker.62.diff http://ss3.gemstone.com/ss/Pharo20/HudsonBuildTools20-MarcusDenker.8.diff -- Marcus Denker -- http://marcusdenker.de

Oct. 20, 2012

Re: [Pharo-project] Group metacello question

by Dale Henrichs

Stef, Yes... the specifications from each section are merged in order to produce the final set of specifications: for: #common do: [ spec: 'package' with: [ spec repository: 'http://example.com/repo' ]]. for: #pharo do: [ spec: 'package' with: [ spec file: 'package.pharo-dkh.1' ]]. for: #squeak do: [ spec: 'package' with: [ spec file: 'package.squeak-dkh.1' ]]. with the attributes #(common pharo) it resolves to: spec: 'package' with: [ spec file: 'package.pharo-dkh.1'; repository: 'http://example.com/repo' ]. with the attributes #(common pharo) it resolves to: spec: 'package' with: [ spec file: 'package.squeak-dkh.1'; repository: 'http://example.com/repo' ]. with the attributes #(common gemstone) it resolves to: spec: 'package' with: [ spec repository: 'http://example.com/repo' ]. and so on... Dale ----- Original Message ----- | From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> | To: Pharo-project(a)lists.gforge.inria.fr | Sent: Saturday, October 20, 2012 2:10:03 PM | Subject: Re: [Pharo-project] Group metacello question | | Hi dale | | it is correct that | | common | squeakcommon | pharo | then pharoxxx | sections are loaded all together? | | Stef | > I'm updating the chapter | > | > | > \paragraph{Loading order.} | > \sd{dale is it correct?} Notice that if you | > in a system where the platform attributes are (\ct{#common} | > \ct{#squeakCommon} \ct{#pharo} \ct{#'pharo2.x'} | > \ct{#'pharo2.0.x'}) (you can obtain this information doing | > \ct{ConfigurationOf project attributes}) and you have specified | > three sections such as \ct{#common}, \ct{#pharo} and | > \ct{#pharo2.0.x}, these sections will loaded one after the other. | > | > \begin{code}{} | > ConfigurationOfCoolBrowser>>baseline09: spec | > <version: '0.9-baseline'> | > | > !\textbf{spec for: \#common do: [}! | > spec blessing: #baseline. | > spec repository: 'http://www.example.com/CoolBrowser'. | > | > spec | > package: 'CoolBrowser-Core'; | > package: 'CoolBrowser-Tests' with: [ spec | > requires: 'CoolBrowser-Core' ]; | > package: 'CoolBrowser-Addons' with: [ spec | > requires: 'CoolBrowser-Core' ]; | > package: 'CoolBrowser-AddonsTests' with: [ | > spec requires: #('CoolBrowser-Addons' | > 'CoolBrowser-Tests' ) ]. | > spec | > group: 'default' with: #('CoolBrowser-Core' | > 'CoolBrowser-Addons' ); | > group: 'Core' with: #('CoolBrowser-Core' | > 'CoolBrowser-Platform' ); | > group: 'Extras' with: #('CoolBrowser-Addon'); | > group: 'Tests' with: #('CoolBrowser-Tests' | > 'CoolBrowser-AddonsTests' ); | > group: 'CompleteWithoutTests' with: #('Core', | > 'Extras' ); | > group: 'CompleteWithTests' with: | > #('CompleteWithoutTests', 'Tests' )]. | > | > !\textbf{spec for: \#gemstone do: [}! | > spec package: 'CoolBrowser-Platform' with: | > 'CoolBrowser-PlatformGemstone']. | > !\textbf{spec for: \#pharo do: [}! | > spec package: 'CoolBrowser-Platform' with: | > 'CoolBrowser-PlatformPharo']. | > !\textbf{spec for: \#pharo2.0.x do: [}! | > spec package: 'CoolBrowser-Addons' with: | > 'CoolBrowser-Core20']. | > | > \end{code} | > | > | | |

Oct. 20, 2012

Re: [Pharo-project] Group metacello question

by StÃ©phane Ducasse

Hi dale it is correct that common squeakcommon pharo then pharoxxx sections are loaded all together? Stef > I'm updating the chapter > > > \paragraph{Loading order.} > \sd{dale is it correct?} Notice that if you > in a system where the platform attributes are (\ct{#common} \ct{#squeakCommon} \ct{#pharo} \ct{#'pharo2.x'} \ct{#'pharo2.0.x'}) (you can obtain this information doing \ct{ConfigurationOf project attributes}) and you have specified three sections such as \ct{#common}, \ct{#pharo} and \ct{#pharo2.0.x}, these sections will loaded one after the other. > > \begin{code}{} > ConfigurationOfCoolBrowser>>baseline09: spec > <version: '0.9-baseline'> > > !\textbf{spec for: \#common do: [}! > spec blessing: #baseline. > spec repository: 'http://www.example.com/CoolBrowser'. > > spec > package: 'CoolBrowser-Core'; > package: 'CoolBrowser-Tests' with: [ spec requires: 'CoolBrowser-Core' ]; > package: 'CoolBrowser-Addons' with: [ spec requires: 'CoolBrowser-Core' ]; > package: 'CoolBrowser-AddonsTests' with: [ > spec requires: #('CoolBrowser-Addons' 'CoolBrowser-Tests' ) ]. > spec > group: 'default' with: #('CoolBrowser-Core' 'CoolBrowser-Addons' ); > group: 'Core' with: #('CoolBrowser-Core' 'CoolBrowser-Platform' ); > group: 'Extras' with: #('CoolBrowser-Addon'); > group: 'Tests' with: #('CoolBrowser-Tests' 'CoolBrowser-AddonsTests' ); > group: 'CompleteWithoutTests' with: #('Core', 'Extras' ); > group: 'CompleteWithTests' with: #('CompleteWithoutTests', 'Tests' )]. > > !\textbf{spec for: \#gemstone do: [}! > spec package: 'CoolBrowser-Platform' with: 'CoolBrowser-PlatformGemstone']. > !\textbf{spec for: \#pharo do: [}! > spec package: 'CoolBrowser-Platform' with: 'CoolBrowser-PlatformPharo']. > !\textbf{spec for: \#pharo2.0.x do: [}! > spec package: 'CoolBrowser-Addons' with: 'CoolBrowser-Core20']. > > \end{code} > >

Oct. 20, 2012

Re: [Pharo-project] Ring Methods and Traits...

by StÃ©phane Ducasse

This is strange that we missed it. Now veronica will be on vacation in November so we will see. Can you create an issue so that I do not forget. > What's the plan there? > > We definitely need something like RGMethodDefinition>>#origin and certainly > a proper implementation of RGMethodDefinition>>#isFromTrait. The current > version will never work with remote methods as it relies 100% on > CompiledMethod>>#isFromTrait > > best > cami >

Oct. 20, 2012

Re: [Pharo-project] [Issue Tracker] The last 6 open 3-digit Issues!

by StÃ©phane Ducasse

On Oct 20, 2012, at 6:41 PM, Marcus Denker wrote: > The 6 last issues with an issue tracker number less than 1000... > > Issue 329: strange behaviour when Proceeding or Stepping in a newly opened Debugger > http://code.google.com/p/pharo/issues/detail?id=329 this is on the todo of igor :) As soon as athens is out :) > > Issue 439: Change autocompletion shortcut from cmd-q to ...? > http://code.google.com/p/pharo/issues/detail?id=439 > > Issue 709: Debugger highlight bug > http://code.google.com/p/pharo/issues/detail?id=709 > > Issue 825: Some changes are not save to the changes file > http://code.google.com/p/pharo/issues/detail?id=825 I will check this one especially since now we do not have systemChangenotifier. > Issue 895: class not well unloaded with monticello > http://code.google.com/p/pharo/issues/detail?id=895 We should recheck that one because now that we changed and fixed the unload of packages. > > Issue 958: Adding Iterable to Pharo > http://code.google.com/p/pharo/issues/detail?id=958 > > > -- > Marcus Denker -- http://marcusdenker.de > >

Oct. 20, 2012

Re: [Pharo-project] Still Alive

by StÃ©phane Ducasse

On Oct 20, 2012, at 4:24 PM, Sean P. DeNigris wrote: > Hey guys, > > A few of you reached out since I have been absent from commits and the > mailing lists. I am very much still around, just furiously hacking on a > Pharo project (and a little burnt out from ESUG, but in a good way). We imagined that you were running around to extinct fire not to get burnt out :). We are working :) even if we got some hiccups with team evaluation and a lot of other administrative varia and normal duties of a research lab. > Thanks for the love :) :) > > Sean > > > > -- > View this message in context: http://forum.world.st/Still-Alive-tp4652126.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Oct. 20, 2012

Re: [Pharo-project] Progress bar in 2.0

by StÃ©phane Ducasse

On Oct 20, 2012, at 3:53 PM, Sean P. DeNigris wrote: > EstebanLM wrote >> it is supposed to be... > > Step by step we evolve... under the covers, the new progress system bears > little resemblance to the previous mess. It is much more powerful, allowing > us to create, manage, and receive updates about units of work. And, we will > continuously improve itâ¦ I love this message yes we do that all the time. The most funny aspect is that I do not thin that many people realize how much the system improved. It is like an iceberg :) > > Sean > > > > -- > View this message in context: http://forum.world.st/Progress-bar-in-2-0-tp4651694p4652122.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Oct. 20, 2012

[Pharo-project] [update 2.0] #20354

by Marcus Denker

20354 ----- Issue 4651: Introduce AuthorNameRequest http://code.google.com/p/pharo/issues/detail?id=4651 Issue 3347: simplified and unified Strings line-ending changing methods http://code.google.com/p/pharo/issues/detail?id=3347 ssue 2345: Should we keep sorted: nil ? http://code.google.com/p/pharo/issues/detail?id=2345 Diff information: http://ss3.gemstone.com/ss/Pharo20/System-Support-MarcusDenker.723.diff http://ss3.gemstone.com/ss/Pharo20/Collections-Traits-MarcusDenker.11.diff http://ss3.gemstone.com/ss/Pharo20/Collections-Strings-MarcusDenker.233.diff http://ss3.gemstone.com/ss/Pharo20/Collections-Sequenceable-MarcusDenker.12… http://ss3.gemstone.com/ss/Pharo20/Collections-Abstract-MarcusDenker.190.di… -- Marcus Denker -- http://marcusdenker.de

Oct. 20, 2012

Re: [Pharo-project] Yet another Notation format: Object literals

by Igor Stasenko

On 20 October 2012 16:29, Dale Henrichs <dhenrich(a)vmware.com> wrote: > > > ----- Original Message ----- > | From: "Igor Stasenko" <siguctua(a)gmail.com> > | To: Pharo-project(a)lists.gforge.inria.fr > | Sent: Friday, October 19, 2012 8:13:12 PM > | Subject: Re: [Pharo-project] Yet another Notation format: Object literals > | > | On 20 October 2012 03:48, Dale Henrichs <dhenrich(a)vmware.com> wrote: > | > > | > > | > ----- Original Message ----- > | > | From: "Igor Stasenko" <siguctua(a)gmail.com> > | > | To: Pharo-project(a)lists.gforge.inria.fr > | > | Sent: Friday, October 19, 2012 4:46:47 PM > | > | Subject: Re: [Pharo-project] Yet another Notation format: Object > | > | literals > | > | > | > | On 20 October 2012 00:54, Dale Henrichs <dhenrich(a)vmware.com> > | > | wrote: > | > | > Igor, > | > | > > | > | > It's not clear that I need to be part of this discussion. > | > | > > | > | > If you want to invent a new serialization format, then go for > | > | > it. > | > | > > | > | > I did chime in with my opinion that your suggested format was > | > | > not > | > | > very readable. You happen to disagree with me. > | > | > > | > | > | > | Yes, i disagree. Tell me what is not readable in this: > | > | > | > | #( Dictionary > | > | > | > | yellow (Color 1 1 0) > | > | blue (Color 0 0 1) > | > | red (Color 1 0 0) > | > | > | > | ) fromObjectLiteral. > | > > | > Please read my earlier description of why I think JSON is more > | > readable as you haven't addressed the main points with this > | > format... > | > | yes, because i do not regarding them as significant. > > Then I don't think I should be the one that you get feedback from ... or perhaps you should re-evaluate your thoughts that they are not significant ... > > At this point in time I don't see the point in discussing anything more ... > > You seem to be trying to convince me that I should be able to read a format that I consider unreadable ... you don't seem to want to hear that I consider the format unreadable ... > > We are done... > yes, we are :) > Dale > -- Best regards, Igor Stasenko.

Oct. 20, 2012