[Pharo-dev] [Pharo 7.0-dev] Build #626: 21333-update-iceberg-to-068

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #626 was: SUCCESS.

The Pull Request #876 was integrated: "21333-update-iceberg-to-068"
Pull request url: https://github.com/pharo-project/pharo/pull/876

Issue Url: https://pharo.fogbugz.com/f/cases/21333
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/626/

[Pharo-dev] [Pharo 7.0-dev] Build #625: 21424-Comment-explaining-StringexpandMacros--co

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #625 was: FAILURE.

The Pull Request #971 was integrated: 
"21424-Comment-explaining-StringexpandMacros--co"
Pull request url: https://github.com/pharo-project/pharo/pull/971

Issue Url: https://pharo.fogbugz.com/f/cases/21424
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/625/

Re: [Pharo-dev] Pharo 7.0 does not includes "Metacello support for GitFileTree metadata-less mode"

[Cyril Ferlicot D.]

Le 25/02/2018 à 23:07, Cyril Ferlicot D. a écrit :
> Hi!
> 
> This support is in this PR:
> 
> https://github.com/pharo-project/pharo/pull/950
> 
> It was not added in Pharo 7 during the last sync but was in Pharo 6.1.
> 
> I hope in the future we will depend on Metacello as a project during the
> bootstrap instead of having the sources directly in the Pharo
> repository. It will help but it needs work.
> 


Hi!

It is integrated. Can you check in the latest Pharo please?

-- 
Cyril Ferlicot
https://ferlicot.fr



signature.asc
Description: OpenPGP digital signature

[Pharo-dev] [Pharo 7.0-dev] Build #624: 21436 Clean the professor

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #624 was: SUCCESS.

The Pull Request #981 was integrated: "21436 Clean the professor"
Pull request url: https://github.com/pharo-project/pharo/pull/981

Issue Url: https://pharo.fogbugz.com/f/cases/21436
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/624/

Re: [Pharo-dev] Esteban's ChangeLog week of 19 February 2018

[Francisco Ortiz Peñaloza]

Esteban,

is there any available information of this new UI. Sketches, proposed ideas?

Thanks,
Francisco

On Mon, Feb 26, 2018 at 8:03 AM, Esteban Lorenzano 
wrote:

> btw… reason why inform is being so small is because I’m investing a lot of
> time on a new UI for iceberg.
> and that’s a “meta-task”. I will try to split tasks on smaller ones :)
>
> Esteban
>
> > On 26 Feb 2018, at 11:47, Sean P. DeNigris 
> wrote:
> >
> > EstebanLM wrote
> >>
> >>Now it should be there ;)
> >
> > Yes, it works. Thanks!!
> >
> >
> >
> > -
> > Cheers,
> > Sean
> > --
> > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.
> html
> >
>
>
>

[Pharo-dev] [Pharo 7.0-dev] Build #623: 21434 Improve WebBrowser code (lint, naming, comments, ...)

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #623 was: SUCCESS.

The Pull Request #979 was integrated: "21434 Improve WebBrowser code (lint, 
naming, comments, ...)"
Pull request url: https://github.com/pharo-project/pharo/pull/979

Issue Url: https://pharo.fogbugz.com/f/cases/21434
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/623/

[Pharo-dev] [Pharo 7.0-dev] Build #622: 21414 Cleanup OSWindow-Tests package

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #622 was: SUCCESS.

The Pull Request #963 was integrated: "21414 Cleanup OSWindow-Tests package"
Pull request url: https://github.com/pharo-project/pharo/pull/963

Issue Url: https://pharo.fogbugz.com/f/cases/21414
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/622/

[Pharo-dev] [Pharo 7.0-dev] Build #621: 21427 Fix piping and make it work on Windows too

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #621 was: SUCCESS.

The Pull Request #972 was integrated: "21427 Fix piping and make it work on 
Windows too"
Pull request url: https://github.com/pharo-project/pharo/pull/972

Issue Url: https://pharo.fogbugz.com/f/cases/21427
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/621/

Re: [Pharo-dev] Monticello file out bug during bootstrap

[Alistair Grant]

Hi All,

I've submitted:

https://pharo.fogbugz.com/f/cases/21431/
https://github.com/pharo-project/pharo/pull/976

The issue has additional analysis of the problem, namely that
#classSide is a convenience method for retrieving the class from
either an instance or the class, so isn't appropriate for chunk file
out.

Cheers,
Alistair

On 26 February 2018 at 17:43, Alistair Grant  wrote:
> Hi Everyone,
>
> The following demonstrates the problem (and will allow me to provide an
> automated test when I submit a patch):
>
>
> | stream definition writer diskStore nonExistent |
>
> definition := MCMethodDefinition
> className: #DiskStore
> classIsMeta: true
> selector: #activeClass
> category: 'current'
> timeStamp: nil
> source: 'activeClass
> self allSubclassesDo: [:ea |
> ea isActiveClass ifTrue: [^ ea]].
> ^ self'.
> stream := String new writeStream.
> writer := MCStWriter new
> stream: stream;
> yourself.
>
> writer writeMethodPreamble: definition.
> diskStore := stream contents.
>
> definition := MCMethodDefinition
> className: #NotALoadedClass
> classIsMeta: true
> selector: #reset
> category: 'imagine'
> timeStamp: nil
> source: 'reset
>
> ^self doReset'.
> stream := String new writeStream.
> writer := MCStWriter new
> stream: stream;
> yourself.
>
> writer writeMethodPreamble: definition.
> nonExistent := stream contents.
>
> { diskStore. nonExistent. }
>
> " #('
> !DiskStore class methodsFor: ''current'' stamp: ''nil''!
> ' '
> !NotALoadedClass classSide methodsFor: ''imagine'' stamp: ''nil''!
> ')"
>
>
> As can be seen, the DiskStore preamble is as expected, while the
> NotALoadedClass preamble uses "classSide" instead of "class".
>
>
> Modifying one method:
>
>
> MCStWriter>>
> writeMethodPreamble: definition
> self chunkContents: [:str |
>stream bang.
>str nextPutAll: definition className asString.
>definition classIsMeta ifTrue:
>   [ str nextPutAll: ' class' ].
>str
>   nextPutAll: ' methodsFor: ';
>   nextPutAll: definition category asString printString;
>   nextPutAll: ' stamp: ';
>   nextPutAll: definition timeStamp asString printString
>]
>
>
> produces the correct result, i.e. running the test code above produces:
>
>
> " #('
> !DiskStore class methodsFor: ''current'' stamp: ''nil''!
> ' '
> !NotALoadedClass class methodsFor: ''imagine'' stamp: ''nil''!
> ')"
>
>
> The NotALoadedClass has the "class" keyword as expected.
>
>
> Cheers,
> Alistair
>
> On 26 February 2018 at 11:14, Alistair Grant  wrote:
>> Hi Guille and Stef,
>>
>> Stef, thanks also for your reply.  All the information I was going to
>> put there I've included below, so please treat is a combined reply.
>>
>>
>> On 26 February 2018 at 09:51, Guillermo Polito
>>  wrote:
>>> Hi Alistair,
>>>
>>> Can you provide some more context on what are you trying to do and how?
>>
>> I'm working on integrating the changes I've made to FileSystem to
>> properly support symbolic links and all the other attributes returned
>> by libc stat().
>>
>> There's a slightly dated but more detailed description of the changes
>> in 
>> http://forum.world.st/FileSystem-file-attributes-and-isSymlink-patch-tt4956517.html
>>
>> The patch introduces a number of new classes to the FileSystem package:
>>
>> - FileAttributesPluginPrims with Unx and Windows subclasses
>> - Subclasses of FileSystemDirectoryEntry for symbolic links
>> - FileAttributeNotSupported
>>
>>
>>> Generally you should not change anything in the bootstrap, just modify the
>>> classes you want to modify and commit them into the repository. The
>>> bootstrap will take care of it.
>>
>> That's true, but as mentioned this introduces new classes, which also
>> should be handled automatically, but there is a bug in the Monticello
>> file out code that is causing it to fail.
>>
>> I haven't gone through the bootstrap process in great detail, but my
>> understanding is that it reads in the Pharo 7 code from the repository
>> and writes out key classes to .st files to file in as part of the
>> build, i.e.:
>>
>> ${VM70} "${COMPILER_IMAGE_NAME}.image" st ${ST_CACHE}/Multilingual.st
>> ${ST_CACHE}/DeprecatedFileStream.st ${ST_CACHE}/FileSystem.st
>> --no-source --quit --save
>>
>> The bug is only triggered because the new classes, e.g.
>> FileAttributesPluginPrim, are not part of the running image.  You can
>> see the code here:
>>
>>
>> MCMethodDefinition>>fullClassName
>> "Using #class selector for classes for backwards compatibility"
>>
>> ^ self classIsMeta
>> ifFalse: [self className]
>> ifTrue: [
>> (self actualClass isNil or: [ self actualClass isTrait ])
>> ifFalse: [self className, ' class']
>> ifTrue: [self className, ' classSide']]
>>
>>
>> Because FileAttributesPluginPrims isn't in the 

Re: [Pharo-dev] [Pharo 7.0-dev] Build #618: 21430-some-small-cleanup-of-for-reflectivity-tests

[Marcus Denker]

This contains in addition

21419-Integrate-Calypso #966
https://github.com/pharo-project/pharo/pull/966

> On 27 Feb 2018, at 17:22, ci-pharo-ci-jenki...@inria.fr wrote:
> 
> There is a new Pharo build available!
>   
> The status of the build #618 was: SUCCESS.
> 
> The Pull Request #973 was integrated: 
> "21430-some-small-cleanup-of-for-reflectivity-tests"
> Pull request url: https://github.com/pharo-project/pharo/pull/973
> 
> Issue Url: https://pharo.fogbugz.com/f/cases/21430
> Build Url: 
> https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/618/

[Pharo-dev] [Pharo 7.0-dev] Build #619: 21419-Integrate-Calypso

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #619 was: SUCCESS.

The Pull Request #966 was integrated: "21419-Integrate-Calypso"
Pull request url: https://github.com/pharo-project/pharo/pull/966

Issue Url: https://pharo.fogbugz.com/f/cases/21419
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/619/

[Pharo-dev] [Pharo 7.0-dev] Build #618: 21430-some-small-cleanup-of-for-reflectivity-tests

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #618 was: SUCCESS.

The Pull Request #973 was integrated: 
"21430-some-small-cleanup-of-for-reflectivity-tests"
Pull request url: https://github.com/pharo-project/pharo/pull/973

Issue Url: https://pharo.fogbugz.com/f/cases/21430
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/618/

[Pharo-dev] [Pharo 7.0-dev] Build #617: 21425-remove-some-dead-code-referencing-SmalltalkEditor

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #617 was: SUCCESS.

The Pull Request #969 was integrated: 
"21425-remove-some-dead-code-referencing-SmalltalkEditor"
Pull request url: https://github.com/pharo-project/pharo/pull/969

Issue Url: https://pharo.fogbugz.com/f/cases/21425
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/617/

[Pharo-dev] [Pharo 7.0-dev] Build #616: 21269 Provide tags in package Announcements-Core for better structure

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #616 was: SUCCESS.

The Pull Request #823 was integrated: "21269 Provide tags in package 
Announcements-Core for better structure"
Pull request url: https://github.com/pharo-project/pharo/pull/823

Issue Url: https://pharo.fogbugz.com/f/cases/21269
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/616/

[Pharo-dev] [Pharo 7.0-dev] Build #615: 21423-Improve-even-more-the-Test-reports

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #615 was: SUCCESS.

The Pull Request #968 was integrated: "21423-Improve-even-more-the-Test-reports"
Pull request url: https://github.com/pharo-project/pharo/pull/968

Issue Url: https://pharo.fogbugz.com/f/cases/21423
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/615/

Re: [Pharo-dev] Simplified AST "Suggestions" menu definitions

[Torsten Bergmann]

Added to: http://wiki.astares.com/pharo/607


> Gesendet: Montag, 26. Februar 2018 um 08:17 Uhr
> Von: "Marcus Denker" 
> An: "Pharo Development List" 
> Betreff: Re: [Pharo-dev] Simplified AST "Suggestions" menu definitions
>
> 
> 
> > On 25 Feb 2018, at 21:30, Stephane Ducasse  wrote:
> > 
> > Marcus I thought that the context was about to represent what the
> > tools selected like the class currently selected.
> > You have this information in the AST?
> > 
> The AST as coming from the Parser: no. The AST after name Analysis: yes.
> Which means you actually need the class to do name analysis (“Semantic 
> Analysis”, 
> implemented by OCASTSemanticAnalyzer).
> 
> I think it will be easy:
> 
> -> there is RubSmalltalkCodeMode / RubSmalltalkScriptingMode which models if 
> the editor.
> is editing Doits or Methods (important for parsing!).
> -> RubSmalltalkCodeMode does have an ivar classOrMetaclass already. It is not 
> set by most tools yet, though.
> -> we can easily add there (or in RubSmalltalkEditor) an “ast “ ivar and 
> re-parse at every keystroke.
> 
> So as soon as we make sure that all users of RubSmalltalkCodeMode correctly 
> set the class, this will be all
> very simple.
> 
>   Marcus
>