Re: [Pharo-dev] Writeup: how to contribute to Pharo

[Esteban Lorenzano]

Hi,

> On 19 Oct 2017, at 01:36, Hernán Morales Durand  
> wrote:
> 
> Thanks Guille, now it looks fine.
> 
> Another issue for Windows users is that you cannot execute the workaround:
> 
> $ git config core.longpaths true
> 
> until you first cloned the repository. That's why I said one first should let 
> fail the git clone command and then:
> 
> $ cd pharo/
> $ git config core.longpaths true
> $ git checkout -f HEAD
> 
> If anyone can check because submitting a fix should be easy and there 
> shouldn't be guessing in the process.

that’s why we created tonel (we will be moving to it soon). 
libgit2 does not recognise core.longpaths (in iceberg, process is split in two: 
bare clone and checkout so I tried adding that option when repository is 
created before checking out and it does not works either).
also, one other reason to move to tonel is time: clone itself is very fast, but 
the checkout (there is a ridiculous amount of files to recreate there) is very 
slow.

Esteban

> 
> Cheers,
> 
> Hernán
> 
> 
> 2017-10-18 4:37 GMT-03:00 Guillermo Polito  >:
> 
> 
> On Tue, Oct 17, 2017 at 12:42 PM, Hernán Morales Durand 
> mailto:hernan.mora...@gmail.com>> wrote:
> Thank you Esteban, that was the problem! :)
> 
> Maybe guille wants to clarify the correct remote repository in the page: 
> https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to-Pharo
>  
> 
>  after "You can click on the Add remote option and configure a remote with a 
> name and repository url."
> 
> Done that.
> 
> Can you check if that's ok?
>  
> 
> Another thing. I created a PR with a fix for this bug : 
> https://pharo.fogbugz.com/f/cases/17754/CheckBoxModel-RadioButtonModel-ignore-disable
>  
> 
>  following the guide to the Step 3. However I couldn't view any PR in my 
> Github page (see attach).
> 
> Do I miss something?
> 
> 
> 2017-10-17 6:53 GMT-03:00 Esteban Lorenzano  >:
> no is ok.
> with the pharo version I know the iceberg version :)
> 
> anyway your problem is that the remote for pharo is bad.
> 
> you added g...@github.com :pharo/pharo.git and I do 
> not think that exists. 
> Correct one is: 
> 
> g...@github.com :pharo-project/pharo.git
> 
> Esteban
> 
> 
>> On 17 Oct 2017, at 11:51, Hernán Morales Durand > > wrote:
>> 
>> I don't see any easy way to find the Iceberg version.
>> 
>> Should I update Iceberg using this script also in Pharo 7?
>> 
>> "Restore defaults"
>> Iceberg enableMetacelloIntegration: false.
>> MetacelloPharo30Platform select.
>> 
>> "Update metacello" 
>> Metacello new
>>   baseline: 'Metacello';
>>   repository: 'github://metacello/metacello:Pharo6.1/repository <>';
>>   onConflict: [:e | e useIncoming ];
>>   get;
>>   load.
>> 
>> "Update iceberg"
>>  #(
>> 'Iceberg-UI' 
>> 'Iceberg-Plugin-GitHub' 
>> 'Iceberg-Plugin' 
>> 'Iceberg-Metacello-Integration' 
>> 'Iceberg-Libgit-Tonel' 
>> 'Iceberg-Libgit-Filetree' 
>> 'Iceberg-Libgit' 
>> 'Iceberg' 
>> 'LibGit-Core') 
>> do: [ :each | (each asPackageIfAbsent: [ nil ]) ifNotNil: #removeFromSystem 
>> ].
>> Metacello new
>>   baseline: 'Iceberg';
>>   repository: 'github://pharo-vcs/iceberg:v0.6 <>';
>>   load.
>> 
>> 2017-10-17 6:46 GMT-03:00 Hernán Morales Durand > >:
>> Hi Esteban,
>> 
>> This one:
>> 
>> wget -O- get.pharo.org/70+vm  | bash -
>> 
>> 2017-10-17 3:36 GMT-03:00 Esteban Lorenzano > >:
>> which Pharo version (and Iceberg version) do you have?
>> 
>> Esteban
>> 
>>> On 17 Oct 2017, at 04:36, Hernán Morales Durand >> > wrote:
>>> 
>>> Hi Guille,
>>> 
>>> In 
>>> https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to-Pharo
>>>  
>>> 
>>> 
>>> This part is not working for me: "Go back to iceberg, right click on the 
>>> pharo repository and go to the Pharo entry. You'll see the option Create 
>>> new branch from Fogbugz issue."
>>> 
>>> Because there is no such "Pharo" option in the menu. See the attached 
>>> screenshot.
>>> 
>>> Did I miss something?
>>> Any suggestion?
>>> 
>>> 
>>> 2017-08-10 12:17 GMT-03:00 Guillermo Polito >> >:
>>> Hi, 
>>> 
>>> I've made some write up for the pharo part (not metacello or external 
>>> projects)
>>> 
>>> https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to-Pharo
>>>  
>>> 
>>> 
>>> Of course, expect bugs on it :) Not everything is smooth. If you have 
>>> comments, they a

Re: [Pharo-dev] UnifiedFFI Docs

[Ben Coman]

On Thu, Oct 19, 2017 at 1:05 AM, Todd Blanchard  wrote:

> I'm working through Ben's great blog post about playing with libclang and
> I am puzzled by something.
>

Thx Todd. Knowing someone is looking at it encourages me to expand it.
I'm interested in looking at your specific questions, but it might not be
until next week after this stint of long work days.

cheers -ben



>
> invalidateSessionData
>handle atAllPut: 0.
>
> zero;s out the handle.  Cool.  However,
>
> handle isNull
>
> does not return true despite it being used in the getString method as
>
> ^ handle isNull
>  ifTrue: ['external memory invalidated by session restart']
>  ifFalse:[LibClang clang_getCString__cxString: self].
>
> Looks like there should be an isNull on ByteArray that returns true if all
> bytes are zero but it isn't  there.  Was it dropped for some reason?
>
>
>
> On Oct 18, 2017, at 2:58 AM, Dimitris Chloupis 
> wrote:
>
> Sure the documentation could be better, that is definetly important, but
> is already good enough and UFFI is a very technical subject much more
> suited to a mailing list . Its not physical possible to cover the massive
> potential of UFFI.
>
> On Wed, Oct 18, 2017 at 9:32 AM Stephane Ducasse 
> wrote:
>
>> Please do not hesitate to do Pull Requests.
>> Luc told me that he wants to do a pass on it and Esteban promises that to
>> me
>> but he is super busy.
>>
>> Stef
>>
>>
>> On Wed, Oct 18, 2017 at 5:54 AM, Todd Blanchard 
>> wrote:
>> > Wonderful!  Thanks.
>> >
>> >> On Oct 17, 2017, at 3:45 PM, stephan  wrote:
>> >>
>> >> On 17-10-17 23:06, Todd Blanchard wrote:
>> >>> Anyone know what happened to this?
>> >>> https://ci.inria.fr/pharo-contribution/view/Books/job/
>> PharoBookWorkInProgress/lastSuccessfulBuild/artifact/
>> book-result/UnifiedFFI/UnifiedFFI.pdf
>> >>
>> >> https://github.com/SquareBracketAssociates/Booklet-uFFI
>> >>
>> >> has a link to a bintray pdf download
>> >>
>> >> Stephan
>> >>
>> >>
>> >>
>> >
>> >
>>
>>
>

Re: [Pharo-dev] Writeup: how to contribute to Pharo

[Hernán Morales Durand]

Thanks Guille, now it looks fine.

Another issue for Windows users is that you cannot execute the workaround:

$ git config core.longpaths true

until you first cloned the repository. That's why I said one first should
let fail the git clone command and then:

$ cd pharo/
$ git config core.longpaths true
$ git checkout -f HEAD

If anyone can check because submitting a fix should be easy and there
shouldn't be guessing in the process.

Cheers,

Hernán


2017-10-18 4:37 GMT-03:00 Guillermo Polito :

>
>
> On Tue, Oct 17, 2017 at 12:42 PM, Hernán Morales Durand <
> hernan.mora...@gmail.com> wrote:
>
>> Thank you Esteban, that was the problem! :)
>>
>> Maybe guille wants to clarify the correct remote repository in the page:
>> https://github.com/guillep/PharoIntegrationProcess/wiki/Cont
>> ribute-a-fix-to-Pharo after "You can click on the *Add remote* option
>> and configure a remote with a name and repository url."
>>
>
> Done that.
>
> Can you check if that's ok?
>
>
>>
>> Another thing. I created a PR with a fix for this bug :
>> https://pharo.fogbugz.com/f/cases/17754/CheckBoxModel-RadioB
>> uttonModel-ignore-disable following the guide to the Step 3. However I
>> couldn't view any PR in my Github page (see attach).
>>
>> Do I miss something?
>>
>>
>> 2017-10-17 6:53 GMT-03:00 Esteban Lorenzano :
>>
>>> no is ok.
>>> with the pharo version I know the iceberg version :)
>>>
>>> anyway your problem is that the remote for pharo is bad.
>>>
>>> you added g...@github.com:pharo/pharo.git and I do not think that
>>> exists.
>>> Correct one is:
>>>
>>> g...@github.com:pharo-project/pharo.git
>>>
>>> Esteban
>>>
>>>
>>> On 17 Oct 2017, at 11:51, Hernán Morales Durand <
>>> hernan.mora...@gmail.com> wrote:
>>>
>>> I don't see any easy way to find the Iceberg version.
>>>
>>> Should I update Iceberg using this script also in Pharo 7?
>>>
>>> "Restore defaults"
>>> Iceberg enableMetacelloIntegration: false.
>>> MetacelloPharo30Platform select.
>>>
>>> "Update metacello"
>>> Metacello new
>>>   baseline: 'Metacello';
>>>   repository: 'github://metacello/metacello:Pharo6.1/repository';
>>>   onConflict: [:e | e useIncoming ];
>>>   get;
>>>   load.
>>>
>>> "Update iceberg"
>>>  #(
>>> 'Iceberg-UI'
>>> 'Iceberg-Plugin-GitHub'
>>> 'Iceberg-Plugin'
>>> 'Iceberg-Metacello-Integration'
>>> 'Iceberg-Libgit-Tonel'
>>> 'Iceberg-Libgit-Filetree'
>>> 'Iceberg-Libgit'
>>> 'Iceberg'
>>> 'LibGit-Core')
>>> do: [ :each | (each asPackageIfAbsent: [ nil ]) ifNotNil:
>>> #removeFromSystem ].
>>> Metacello new
>>>   baseline: 'Iceberg';
>>>   repository: 'github://pharo-vcs/iceberg:v0.6';
>>>   load.
>>>
>>> 2017-10-17 6:46 GMT-03:00 Hernán Morales Durand <
>>> hernan.mora...@gmail.com>:
>>>
 Hi Esteban,

 This one:

 wget -O- get.pharo.org/70+vm | bash -

 2017-10-17 3:36 GMT-03:00 Esteban Lorenzano :

> which Pharo version (and Iceberg version) do you have?
>
> Esteban
>
> On 17 Oct 2017, at 04:36, Hernán Morales Durand <
> hernan.mora...@gmail.com> wrote:
>
> Hi Guille,
>
> In https://github.com/guillep/PharoIntegrationProcess/wiki/Cont
> ribute-a-fix-to-Pharo
>
> This part is not working for me: "Go back to iceberg, right click on
> the pharo repository and go to the *Pharo* entry. You'll see the
> option *Create new branch from Fogbugz issue*."
>
> Because there is no such "Pharo" option in the menu. See the attached
> screenshot.
>
> Did I miss something?
> Any suggestion?
>
>
> 2017-08-10 12:17 GMT-03:00 Guillermo Polito  >:
>
>> Hi,
>>
>> I've made some write up for the pharo part (not metacello or external
>> projects)
>>
>> https://github.com/guillep/PharoIntegrationProcess/wiki/Cont
>> ribute-a-fix-to-Pharo
>>
>> Of course, expect bugs on it :) Not everything is smooth. If you have
>> comments, they are welcome.
>>
>> Guille
>>
>> --
>>
>> Guille Polito
>>
>> Research Engineer
>> French National Center for Scientific Research - *http://www.cnrs.fr*
>> 
>>
>>
>> *Web:* *http://guillep.github.io* 
>> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>>
>
> 
>
>
>

>>>
>>>
>>
>
>
> --
>
>
>
> Guille Polito
>
> Research Engineer
>
> Centre de Recherche en Informatique, Signal et Automatique de Lille
>
> CRIStAL - UMR 9189
>
> French National Center for Scientific Research - *http://www.cnrs.fr
> *
>
>
> *Web:* *http://guillep.github.io* 
>
> *Phone: *+33 06 52 70 66 13
>

Re: [Pharo-dev] UnifiedFFI Docs

[Todd Blanchard]

> On Oct 18, 2017, at 1:21 PM, Nicolas Cellier 
>  wrote:
> 
> 
> 
> Should isNull be defined as you suggest in ByteArray? If the semantic is 
> #isNullPointer, then I don't think so. If it's a more general message, then 
> maybe...
> 
> What is the class of handle?

It is ByteArray.  I agree that ByteArray responding to isNull is weird.

The struct the memory maps is struct { void* data, int flags } so I can work 
around this with something like 

self data ifNil: [.]

I have just encountered another problem.

Ben creates a type specification as a class variable to model void*[3]

VoidPointer3 := FFITypeArray ofType: 'void*' size: 3.

which produces the following accessor for data

(FFITypeArray ofType: #FFIVoid size: 3) fromHandle: (handle copyFrom: 
OFFSET_DATA to: OFFSET_DATA + 23)

This fails because the native size of void is undefined even though it is a 
void* being mapped.

I will continue to see if I can figure out why it generates this spec - 
definitely a broken assumption somewhere in here.

-Todd Blanchard

Re: [Pharo-dev] UnifiedFFI Docs

[Nicolas Cellier]

2017-10-18 19:05 GMT+02:00 Todd Blanchard :

> I'm working through Ben's great blog post about playing with libclang and
> I am puzzled by something.
>
> invalidateSessionData
>handle atAllPut: 0.
>
> zero;s out the handle.  Cool.  However,
>
> handle isNull
>
> does not return true despite it being used in the getString method as
>
> ^ handle isNull
>  ifTrue: ['external memory invalidated by session restart']
>  ifFalse:[LibClang clang_getCString__cxString: self].
>
> Looks like there should be an isNull on ByteArray that returns true if all
> bytes are zero but it isn't  there.  Was it dropped for some reason?
>
>
>
In original FFI, a ByteArray could not represent a pointer, so it answered:
ByteArray>>isNull
"Answer false since only external addresses can be null"
^false

There was an ExternalAddress subclass for this purpose where isNull was
defined:
ExternalAddress>>isNull
"Answer true if I am a null pointer"
1 to: self size do:[:i| (self at: i) = 0 ifFalse:[^false]].
^true

and there was also a #beNull to nullify the address...


What happens now with UnifiedFFI, is the old FFI API supported (and thus
the example correct), what about Alien, are questions that you must
inquire, but once upon a time, it worked.

Should isNull be defined as you suggest in ByteArray? If the semantic is
#isNullPointer, then I don't think so. If it's a more general message, then
maybe...

What is the class of handle?



> On Oct 18, 2017, at 2:58 AM, Dimitris Chloupis 
> wrote:
>
> Sure the documentation could be better, that is definetly important, but
> is already good enough and UFFI is a very technical subject much more
> suited to a mailing list . Its not physical possible to cover the massive
> potential of UFFI.
>
> On Wed, Oct 18, 2017 at 9:32 AM Stephane Ducasse 
> wrote:
>
>> Please do not hesitate to do Pull Requests.
>> Luc told me that he wants to do a pass on it and Esteban promises that to
>> me
>> but he is super busy.
>>
>> Stef
>>
>>
>> On Wed, Oct 18, 2017 at 5:54 AM, Todd Blanchard 
>> wrote:
>> > Wonderful!  Thanks.
>> >
>> >> On Oct 17, 2017, at 3:45 PM, stephan  wrote:
>> >>
>> >> On 17-10-17 23:06, Todd Blanchard wrote:
>> >>> Anyone know what happened to this?
>> >>> https://ci.inria.fr/pharo-contribution/view/Books/job/
>> PharoBookWorkInProgress/lastSuccessfulBuild/artifact/
>> book-result/UnifiedFFI/UnifiedFFI.pdf
>> >>
>> >> https://github.com/SquareBracketAssociates/Booklet-uFFI
>> >>
>> >> has a link to a bintray pdf download
>> >>
>> >> Stephan
>> >>
>> >>
>> >>
>> >
>> >
>>
>>
>

Re: [Pharo-dev] UnifiedFFI Docs

[Todd Blanchard]

I'm working through Ben's great blog post about playing with libclang and I am 
puzzled by something.

invalidateSessionData
   handle atAllPut: 0. 

zero;s out the handle.  Cool.  However, 

handle isNull 

does not return true despite it being used in the getString method as 

^ handle isNull
 ifTrue: ['external memory invalidated by session restart']
 ifFalse:[LibClang clang_getCString__cxString: self].

Looks like there should be an isNull on ByteArray that returns true if all 
bytes are zero but it isn't  there.  Was it dropped for some reason?



> On Oct 18, 2017, at 2:58 AM, Dimitris Chloupis  wrote:
> 
> Sure the documentation could be better, that is definetly important, but is 
> already good enough and UFFI is a very technical subject much more suited to 
> a mailing list . Its not physical possible to cover the massive potential of 
> UFFI.  
> 
> On Wed, Oct 18, 2017 at 9:32 AM Stephane Ducasse  > wrote:
> Please do not hesitate to do Pull Requests.
> Luc told me that he wants to do a pass on it and Esteban promises that to me
> but he is super busy.
> 
> Stef
> 
> 
> On Wed, Oct 18, 2017 at 5:54 AM, Todd Blanchard  > wrote:
> > Wonderful!  Thanks.
> >
> >> On Oct 17, 2017, at 3:45 PM, stephan  >> > wrote:
> >>
> >> On 17-10-17 23:06, Todd Blanchard wrote:
> >>> Anyone know what happened to this?
> >>> https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgress/lastSuccessfulBuild/artifact/book-result/UnifiedFFI/UnifiedFFI.pdf
> >>>  
> >>> 
> >>
> >> https://github.com/SquareBracketAssociates/Booklet-uFFI 
> >> 
> >>
> >> has a link to a bintray pdf download
> >>
> >> Stephan
> >>
> >>
> >>
> >
> >
> 

Re: [Pharo-dev] open street map

[Pavel Krivanek]

probably coordinates. This works:
http://a.tile.openstreetmap.org/8/129/88.png

-- Pavel

2017-10-18 17:04 GMT+02:00 Stephane Ducasse :

> Hi guys
>
> in the mooc I was used to use this expression
>
> http://a.tile.openstreetmap.org/8/12/8.png
>
> and now I get an empty tile and I wonder why. May openstreet map changed
> their policy.
>
> Did any of you experience the same?
>
> Stef
>
>

[Pharo-dev] open street map

[Stephane Ducasse]

Hi guys

in the mooc I was used to use this expression

http://a.tile.openstreetmap.org/8/12/8.png

and now I get an empty tile and I wonder why. May openstreet map changed
their policy.

Did any of you experience the same?

Stef

Re: [Pharo-dev] Compiler Explorer (for the Compiler guys) #offtopic

[Clément Bera]

On Wed, Oct 18, 2017 at 3:27 PM, Jan Vrany  wrote:

> Hi,
>
> > I was thinking of changing that, adding a primitive which answers a
> > CogMethod as a bytearray, but you still need to use external libs
> > such as gdb/lldb to disassemble your binary
>
> I use udis86 [1] for that purpose. Tiny, clean & dead easy to use.
> x86 only, though.
>
> HTH. Jan
>
> [1]: http://udis86.sourceforge.net/


Tiny that's good.

I normally use the facilities provided by the processor simulators (but
that's not tiny).

Not sure the production environment should have those features anyway


>
>
> > (which is possible but not working out of the box everywhere and it
> > does not make sense to include that as part of the VM), and you still
> > need something extracted from VMMaker to make sense out of the
> > CogMethod header and CogMethod map, which has a lot of dependencies,
> > so likely the whole VMMaker itself. And I'm not talking about all the
> > different CogMethod flavors.
> >
> > With VMMaker loaded you can do it with in-image compilation but you
> > will have the machine code with only unlinked sends. With linked send
> > it's more difficult as you need to really simulate the whole runtime.
> >
> > Overall there's no amazing solution. In the example shown it's easier
> > as in C++ the code is not modified while it runs and you've already
> > have gdb/lldb APIs to show what they show.
> >
> >
> > >
> > >
> > >
> > > >
> > > >
> > > > Cheers,
> > > > Doru
> > > >
> > > >
> > > > > On Oct 17, 2017, at 10:03 PM, Esteban A. Maringolo  > > > > gmail.com> wrote:
> > > > >
> > > > > I'm sure we could do this with ease, because we already can see
> > > > > the bytecodes.
> > > > >
> > > > > https://godbolt.org/
> > > > >
> > > > > Regards!
> > > > >
> > > > > Esteban A. Maringolo
> > > > >
> > > >
> > > > --
> > > > www.tudorgirba.com
> > > > www.feenk.com
> > > >
> > > > "The coherence of a trip is given by the clearness of the goal."
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Mariano
> > > http://marianopeck.wordpress.com
> > >
> >
> >
> >
> > --
> > Clément Béra
> > Pharo consortium engineer
> > https://clementbera.wordpress.com/
> > Bâtiment B 40, avenue Halley 59650 Villeneuve d'Ascq
>
>


-- 
Clément Béra
Pharo consortium engineer
https://clementbera.wordpress.com/
Bâtiment B 40, avenue Halley 59650 Villeneuve d'Ascq

Re: [Pharo-dev] StringMorph removing Text styling

[Peter Uhnák]

> So maybe renaming (subclassing?) StringMorph to LabelMorph to make it more
> clear?
>

Never mind. This apparently exists and I am blind...

Peter

Re: [Pharo-dev] StringMorph removing Text styling

[Peter Uhnák]

There's a cursor issue though... when you have TextMorphs in e.g. list
(FastTable), then the cursor changes to text selection, that's why I wanted
to use StringMorph.

So maybe renaming (subclassing?) StringMorph to LabelMorph to make it more
clear?

Peter

On Wed, Oct 18, 2017 at 1:30 PM, Pavel Krivanek 
wrote:

> Personally I would expect that the second version should be fixed to
> discard formatting. We have the TextMorph for such cases.
>
> -- Pavel
>
> 2017-10-18 11:40 GMT+02:00 Peter Uhnák :
>
>> Hi,
>>
>> I am not sure if this is a bug or a feature, but converting Text to
>> StringMorph clears some of the formating.
>>
>> Compare:
>>
>> |text|
>> text := 'hello' asText makeAllColor: Color red.
>>
>> text asStringMorph openInWindow. "no color"
>> (StringMorph contents: text) openInWindow. "with color"
>>
>> Bug? Feature?
>>
>> Thanks,
>> Peter
>>
>
>

Re: [Pharo-dev] Compiler Explorer (for the Compiler guys) #offtopic

[Jan Vrany]

Hi, 

> I was thinking of changing that, adding a primitive which answers a
> CogMethod as a bytearray, but you still need to use external libs
> such as gdb/lldb to disassemble your binary 

I use udis86 [1] for that purpose. Tiny, clean & dead easy to use. 
x86 only, though. 

HTH. Jan

[1]: http://udis86.sourceforge.net/


> (which is possible but not working out of the box everywhere and it
> does not make sense to include that as part of the VM), and you still
> need something extracted from VMMaker to make sense out of the
> CogMethod header and CogMethod map, which has a lot of dependencies,
> so likely the whole VMMaker itself. And I'm not talking about all the
> different CogMethod flavors.
> 
> With VMMaker loaded you can do it with in-image compilation but you
> will have the machine code with only unlinked sends. With linked send
> it's more difficult as you need to really simulate the whole runtime.
> 
> Overall there's no amazing solution. In the example shown it's easier
> as in C++ the code is not modified while it runs and you've already
> have gdb/lldb APIs to show what they show.
> 
>  
> > 
> > 
> >  
> > > 
> > > 
> > > Cheers,
> > > Doru
> > > 
> > > 
> > > > On Oct 17, 2017, at 10:03 PM, Esteban A. Maringolo  > > > gmail.com> wrote:
> > > > 
> > > > I'm sure we could do this with ease, because we already can see
> > > > the bytecodes.
> > > > 
> > > > https://godbolt.org/
> > > > 
> > > > Regards!
> > > > 
> > > > Esteban A. Maringolo
> > > > 
> > > 
> > > --
> > > www.tudorgirba.com
> > > www.feenk.com
> > > 
> > > "The coherence of a trip is given by the clearness of the goal."
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > 
> > 
> > 
> > -- 
> > Mariano
> > http://marianopeck.wordpress.com
> > 
> 
> 
> 
> -- 
> Clément Béra
> Pharo consortium engineer
> https://clementbera.wordpress.com/
> Bâtiment B 40, avenue Halley 59650 Villeneuve d'Ascq

[Pharo-dev] [Pharo 7.0-dev] Build #209: 17754-CheckBoxModel--RadioButtonModel-ignore-disable

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #209 was: SUCCESS.

The Pull Request #372 was integrated: 
"17754-CheckBoxModel--RadioButtonModel-ignore-disable"
Pull request url: https://github.com/pharo-project/pharo/pull/372

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

Re: [Pharo-dev] Compiler Explorer (for the Compiler guys) #offtopic

[Clément Bera]

On Wed, Oct 18, 2017 at 1:42 PM, Mariano Martinez Peck <
marianop...@gmail.com> wrote:

>
>
> On Wed, Oct 18, 2017 at 3:36 AM, Tudor Girba  wrote:
>
>> Hi,
>>
>> This is already available since some time in the GTInspector. You can
>> just inspect a compiled method. You will get both the bytecode and the AST
>> (with source tracking, too). In fact, this was one of the original reasons
>> why GTInspector exists: I wanted to figure out how the AST is structured so
>> that I can write queries against it :).
>>
>
>
> Sure, we just miss machine code :)
>

Yeah the machine code is what matters.


> But...AFAIR to get the machine code of a method it needs VMMaker to be
> loaded
>

I was thinking of changing that, adding a primitive which answers a
CogMethod as a bytearray, but you still need to use external libs such as
gdb/lldb to disassemble your binary (which is possible but not working out
of the box everywhere and it does not make sense to include that as part of
the VM), and you still need something extracted from VMMaker to make sense
out of the CogMethod header and CogMethod map, which has a lot of
dependencies, so likely the whole VMMaker itself. And I'm not talking about
all the different CogMethod flavors.

With VMMaker loaded you can do it with in-image compilation but you will
have the machine code with only unlinked sends. With linked send it's more
difficult as you need to really simulate the whole runtime.

Overall there's no amazing solution. In the example shown it's easier as in
C++ the code is not modified while it runs and you've already have gdb/lldb
APIs to show what they show.



>
>
>
>
>
>>
>>
>> Cheers,
>> Doru
>>
>>
>> On Oct 17, 2017, at 10:03 PM, Esteban A. Maringolo 
>> wrote:
>>
>> I'm sure we could do this with ease, because we already can see the
>> bytecodes.
>>
>> https://godbolt.org/
>>
>> Regards!
>>
>> Esteban A. Maringolo
>>
>>
>> --
>> www.tudorgirba.com
>> www.feenk.com
>>
>> "The coherence of a trip is given by the clearness of the goal."
>>
>>
>>
>>
>>
>>
>
>
> --
> Mariano
> http://marianopeck.wordpress.com
>



-- 
Clément Béra
Pharo consortium engineer
https://clementbera.wordpress.com/
Bâtiment B 40, avenue Halley 59650 Villeneuve d'Ascq

Re: [Pharo-dev] Compiler Explorer (for the Compiler guys) #offtopic

[Esteban A. Maringolo]

Dolphin's debugger was what came to my mind, it had the "dissasembly" way
of debugging VM bytecode.
It doesn't provide was native code ASM, and as I understand GTInspector
neither.

Regards!

Esteban A. Maringolo

2017-10-18 6:55 GMT-03:00 Dimitris Chloupis :

> Yeap GTInspector was the first thing that came to my mind , great tool :)
>
> On Wed, Oct 18, 2017 at 9:37 AM Tudor Girba  wrote:
>
>> Hi,
>>
>> This is already available since some time in the GTInspector. You can
>> just inspect a compiled method. You will get both the bytecode and the AST
>> (with source tracking, too). In fact, this was one of the original reasons
>> why GTInspector exists: I wanted to figure out how the AST is structured so
>> that I can write queries against it :).
>>
>>
>> Cheers,
>> Doru
>>
>>
>> On Oct 17, 2017, at 10:03 PM, Esteban A. Maringolo 
>> wrote:
>>
>> I'm sure we could do this with ease, because we already can see the
>> bytecodes.
>>
>> https://godbolt.org/
>>
>> Regards!
>>
>> Esteban A. Maringolo
>>
>>
>> --
>> www.tudorgirba.com
>> www.feenk.com
>>
>> "The coherence of a trip is given by the clearness of the goal."
>>
>>
>>
>>
>>
>>

Re: [Pharo-dev] Compiler Explorer (for the Compiler guys) #offtopic

[Mariano Martinez Peck]

On Wed, Oct 18, 2017 at 3:36 AM, Tudor Girba  wrote:

> Hi,
>
> This is already available since some time in the GTInspector. You can just
> inspect a compiled method. You will get both the bytecode and the AST (with
> source tracking, too). In fact, this was one of the original reasons why
> GTInspector exists: I wanted to figure out how the AST is structured so
> that I can write queries against it :).
>


Sure, we just miss machine code :)
But...AFAIR to get the machine code of a method it needs VMMaker to be
loaded





>
>
> Cheers,
> Doru
>
>
> On Oct 17, 2017, at 10:03 PM, Esteban A. Maringolo 
> wrote:
>
> I'm sure we could do this with ease, because we already can see the
> bytecodes.
>
> https://godbolt.org/
>
> Regards!
>
> Esteban A. Maringolo
>
>
> --
> www.tudorgirba.com
> www.feenk.com
>
> "The coherence of a trip is given by the clearness of the goal."
>
>
>
>
>
>


-- 
Mariano
http://marianopeck.wordpress.com

Re: [Pharo-dev] StringMorph removing Text styling

[Pavel Krivanek]

Personally I would expect that the second version should be fixed to
discard formatting. We have the TextMorph for such cases.

-- Pavel

2017-10-18 11:40 GMT+02:00 Peter Uhnák :

> Hi,
>
> I am not sure if this is a bug or a feature, but converting Text to
> StringMorph clears some of the formating.
>
> Compare:
>
> |text|
> text := 'hello' asText makeAllColor: Color red.
>
> text asStringMorph openInWindow. "no color"
> (StringMorph contents: text) openInWindow. "with color"
>
> Bug? Feature?
>
> Thanks,
> Peter
>

[Pharo-dev] [Spec] Improved way of linking presenters to domain model objects

[Pavel Krivanek]

Hi,

this is a simple use-case for the chagnes proposed in the pull request 374
(20551-Improve-way-how-Spec-presenters-are-linked-with-domain-models).

https://github.com/pharo-project/pharo/pull/374

I would like to know your comments on it.

Situation: You have a presenter that shows a form with information about a
person. This form contains a submit button and restore button. Next to it
it shows a table with currently saved results. It is only a demo so the
domain object is stored directly in this presenter.

ComposablePresenterWithModel subclass: #FormPresenter
instanceVariableNames: 'form table'

The instance variable "form" is a presenter of a form subcomponent, the
"table" is a fast table.

The ComposablePresenterWithModel stores the model in an instance variable
named "specCompatibleModel". This can be a Model or a NewValueHolder (as it
is a subclass of Model).

We have our domain model class FormModel which contains information about a
person like name, surname etc. It is a subclass of Object.

Object subclass: #FormModel
instanceVariableNames: 'name surname ...'

At the beginning we create a new instance of this class as a model for our
presenter:

FormPresenter>>initialize
self model: FormModel new.
super initialize.

This will create in the instance variable "specCompatibleModel" a value
holder that will contain our domain object and subscribes yourself to
announcements of this value holder.
We need to have this model ready before we will initialize subpresenters
because we will provide this model to our form.

FormPresenter>>initializeWidgets
form := self instantiate: StandaloneFormPresenter on: self
specCompatibleModel
...

We use here "self specCompatibleModel" and not "self model" because we want
to use our value holder directly. If we would use "self model", the form
would create a new value holder and then we would need to synchronize the
data between the form and parent presenter manually.

When the model of the presenter will change, we will fill the table.

FormPresenter>>imodelChanged
table items: {
self model name.
self model surname. }

The presenter for the form is a subclass of ComposablePresenterWithModel
too. It contains input boxes for name and surname. Then it includes buttons
for submitting and restoring of the form content. It contains an instance
variable "workingModel" to store current state of the form. It is different
from the model because we want to be able to restore original data.

ComposablePresenterWithModel subclass: #StandaloneFormPresenter
instanceVariableNames: 'workingModel nameTextInput surnameTextInput
submitButton restoreButton'

To create the form is straightforward and there is nothing special on it:

StandaloneFormPresenter>>initializeWidgets
nameTextInput := self newTextInput autoAccept: true.
surnameTextInput := self newTextInput autoAccept: true.

StandaloneFormPresenter>>initializePresenter
self submitButton action: [self submit].
self restoreButton action: [self restore].

When we obtain a new model, we will create a new working model as copy of
it and we will fill the form with its data

StandaloneFormPresenter>>modelChanged
workingModel := self model copy.
self fillFormWithWorkingModel.

StandaloneFormPresenter>>fillFormWithWorkingModel
self nameTextInput text: workingModel name.
self surnameTextInput text: workingModel surname.

When we restore the form, we will only do the same as in case of model
change - create a new working copy and update the form

StandaloneFormPresenter>>restore
self modelChanged

When we submit the form we obtain the current data from the inputs, store
them in the working model. Then we will replace the model with it and
announce change of the model to other components.

submit
workingModel name: self nameTextInput text.
workingModel surname: self surnameTextInput text.
self model: workingModel.
self specCompatibleModel valueChanged.
This operation will force update of the parent presenter (that will update
the table). The form itself will be updated too (and a new working copy
will be created).

In this simple case we can make it work without need of a the model working
copy. In the simpler approach we wil create parent presenter model as a
subclass of Model.

Model subclass: #FormModel
instanceVariableNames: 'name surname ...'

The instantiation of StandaloneFormPresenter can be done on the model
directly but it is optional because "self model" and "self
specCompatibleModel" return the same object here.

self instantiate: StandaloneFormPresenter on: self model

When the model will change, we will simply fill the form

StandaloneFormPresenter>>modelChanged
self fillForm

StandaloneFormPresenter>>fillForm
self nameTextInput text: self model name.
self surnameTextInput text: self model surname.

When the form will be submitted, we fill the model with new data and
announce changes.

StandaloneFormPresenter>>su

Re: [Pharo-dev] Techtalk today: AI

[Marcus Denker]

Hi,

The tech talk recording is now in the archive:

http://pharo.org/TechTalk


> On 17 Oct 2017, at 16:43, Marcus Denker  wrote:
> 
> Hello!
> The tech talk starts in 20 minutes (17h europe time).
> 
> Slides (pdf) can be downloaded here 
> .
> 
> Invite for Discord (for Q&A after): 
> 
>  http://discord.gg/Sj2rhxn 
> The talk will be on Youtube, follow this link: 
> 
> https://www.youtube.com/c/AlexandreBergel/live 
> 
> 

Re: [Pharo-dev] UnifiedFFI Docs

[Dimitris Chloupis]

Sure the documentation could be better, that is definetly important, but is
already good enough and UFFI is a very technical subject much more suited
to a mailing list . Its not physical possible to cover the massive
potential of UFFI.

On Wed, Oct 18, 2017 at 9:32 AM Stephane Ducasse 
wrote:

> Please do not hesitate to do Pull Requests.
> Luc told me that he wants to do a pass on it and Esteban promises that to
> me
> but he is super busy.
>
> Stef
>
>
> On Wed, Oct 18, 2017 at 5:54 AM, Todd Blanchard 
> wrote:
> > Wonderful!  Thanks.
> >
> >> On Oct 17, 2017, at 3:45 PM, stephan  wrote:
> >>
> >> On 17-10-17 23:06, Todd Blanchard wrote:
> >>> Anyone know what happened to this?
> >>>
> https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgress/lastSuccessfulBuild/artifact/book-result/UnifiedFFI/UnifiedFFI.pdf
> >>
> >> https://github.com/SquareBracketAssociates/Booklet-uFFI
> >>
> >> has a link to a bintray pdf download
> >>
> >> Stephan
> >>
> >>
> >>
> >
> >
>
>

Re: [Pharo-dev] What is blocking Pharo from supporting long paths on Windows?

[Alistair Grant]

Hi Peter,

On Tue, Oct 17, 2017 at 09:16:49PM +0200, Peter Uhn??k wrote:
> So I wanted to update Iceberg in one of my PharoLauncher managed issues.
> Of course the load failed on some missing file... upon further exploration:
> 
> updating Iceberg updates Metacello, and metacello contains content like
> 
> Metacello-metacello-1af26bf/repository/Metacello-ToolBox.package/
> MetacelloToolBox.class/instance/
> modifySection.sectionIndex.repository.requiredProjects.packages.dependencies.includes.files.repositories.preLoadDoIts.postLoadDoIts.supplyingAnswers.groups.versionSpecsDo..st
> (271 characters - longest file path)
> 
> or
> 
> Metacello-metacello-1af26bf/repository/Metacello-GemStone-TestsMCB.package/
> MetacelloScriptingRegistryDisableUndefinedSymbolsTestCase.extension/instance/
> (152 characters - longest directory path)
> 
> To that you need to add the path to the image (44 chars for me), name of the
> image (35 chars on avg for me), and the local location 
> (github-cache\metacello\
> metacello\Pharo6.1) (41 chars).
> 
> tl;dr: 120 chararacters out of Windows 260 is taken by fixed cost, and I need
> to fit 152+ characters (that's just directory, it includes files of course)
> into 140 chars.
> 
> I have longPathsEnabled in Windows (10) and some applications indeed can go
> beyond the limit --- e.g. I can clone (with git) metacello to the same
> directory (and go over the limit), but Pharo will fail if I try to navigate to
> it. So clearly my system supports it, but not Pharo.
> 
> In conclusion:
> 
> Anyone familiar with WinAPI knows what needs to be done for Pharo to support
> unlimited/long paths?
> 
> Thanks,
> Peter

I'm not familiar with the Win API, but probably what you are looking for
is covered by this comment in sqWin32File.h:

Handles paths longer than 260 characters (including NULL) by prepending
"\\?\" to encode UNC paths as suggested in
http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.85%29.aspx#maxpath

  "The maximum path of 32,767 characters is approximate,
 because the "\\?\" prefix may be expanded to a longer
 string by the system at run time, and this expansion
 applies to the total length."

FilePlugin already does this, so normal directory traversal, i.e. using
FileReference, within Pharo should be working correctly.


Cheers,
Alistair

[Pharo-dev] StringMorph removing Text styling

[Peter Uhnák]

Hi,

I am not sure if this is a bug or a feature, but converting Text to
StringMorph clears some of the formating.

Compare:

|text|
text := 'hello' asText makeAllColor: Color red.

text asStringMorph openInWindow. "no color"
(StringMorph contents: text) openInWindow. "with color"

Bug? Feature?

Thanks,
Peter

Re: [Pharo-dev] OSWindow in Pharo 6.1 stable

[Clément Bera]

Hi again,

I made many more attempts since those mails: I wrote this page
 showing how to deploy
my game in native app at 50fps on Linux, Mac and Windows.

Currently I deploy with:
Ubuntu 64 bits: Pharo61-64 (Pharo61-32 also works with the right lib
installed)
Mac OS X 64 bits: Pharo5Alpha-32 (On Pharo61 the keyboard events do not
work correctly)
Windows 64 bits: Pharo61-32 (There are bugs with the SDL2 window, the top
bar is not displayed, but the game work. Reportedly it would work better
with Pharo61-64 but the default Pharo64 VM on Windows still does not
feature the JIT, once the default VM does, I will update).

My goal is to deploy on all platforms with Pharo61-64 (and later Pharo7-64).

I wrote this mail since maybe you are interested in knowing that with
Pharo5Alpha-32 and the set-up described on the page of my game the keyboard
events work fine on Mac, so it may be possible to write a fix for
Pharo61/Pharo7 based on that.

Best,




On Fri, Sep 29, 2017 at 8:56 PM, Stephane Ducasse 
wrote:

> Tx ronie!
>
>
> On Fri, Sep 29, 2017 at 1:42 PM, Ronie Salgado 
> wrote:
> > Hi Clément,
> >
> > I just checked on my machine and it is also not working. It seems to be
> a VM
> > bug. It will take me some time to debug it. I have some suspicious on
> > ioProcessEvents .
> >
> > Best regards,
> > Ronie
> >
> > 2017-09-29 10:39 GMT+02:00 Clément Bera :
> >>
> >>
> >>
> >> On Fri, Sep 29, 2017 at 10:29 AM, Hilaire  wrote:
> >>>
> >>> Hi,
> >>>
> >>> IMHO, it will make Pharo much more robust if core libraries as sdl,
> >>> cairo, etc will be shipped with each plateform dependent virtual
> machine and
> >>> the image modified accordingly to use these core libraries.
> >>
> >>
> >> That's how it is now but some of it is not working (Here SDL events and
> >> there are 2 SDL2 libs by default).
> >>
> >> I think we should still have a minimal image starting with a minimal UI
> >> without using FFI/SDL/Cairo or whatever lib. Else when we start on a
> >> platform where one of this thing is not properly supported yet (See the
> >> problem on the raspberry pie with some Pharo alpha version) it is too
> hard
> >> to understand what is going on.
> >>
> >>>
> >>>
> >>> The delivery of Pharo application to end users is an issue because of
> >>> these recuring problem.
> >>
> >>
> >> Honestly I was trying to write a doc on how to deploy Pharo client app
> >> with SDL2 and Cairo but I have only a version working in Pharo 4 on Mac
> and
> >> Linux, while in theory I could have it working in Windows/Mac/Linux in
> the
> >> latest Pharo.
> >>
> >>>
> >>> Hilaire
> >>>
> >>>
> >>>
> >>> Le 28/09/2017 à 15:02, Clément Bera a écrit :
> 
>  Btw for some reason in the one-click version of Pharo 32 bits on Mac
>  there is 2 SDL plugins (libSDL2-2.0.0 and libSDL2), which leads to
> conflicts
>  (the VM use randomly one lib or the other). I randomly chose one that
> I use
>  and deleted the other one, do you have advises on which one I should
> prefer
>  ? Maybe the events are working only with the other one ?
> 
> >>>
> >>> --
> >>> Dr. Geo
> >>> http://drgeo.eu
> >>>
> >>>
> >>>
> >>
> >
>
>


-- 
Clément Béra
Pharo consortium engineer
https://clementbera.wordpress.com/
Bâtiment B 40, avenue Halley 59650 Villeneuve d'Ascq

Re: [Pharo-dev] Writeup: how to contribute to Pharo

[Esteban Lorenzano]

hi,

> On 18 Oct 2017, at 08:39, Stephane Ducasse  wrote:
> 
> Esteban it would be good to make the remote handling more robust because many 
> people face
> this problem.

if people enter a wrong url, we can't do anything. 
now, the RSD is another problem, not related with this one.

Esteban

> 
> On Tue, Oct 17, 2017 at 11:53 AM, Esteban Lorenzano  > wrote:
> no is ok.
> with the pharo version I know the iceberg version :)
> 
> anyway your problem is that the remote for pharo is bad.
> 
> you added g...@github.com :pharo/pharo.git and I do 
> not think that exists. 
> Correct one is: 
> 
> g...@github.com :pharo-project/pharo.git
> 
> Esteban
> 
> 
>> On 17 Oct 2017, at 11:51, Hernán Morales Durand > > wrote:
>> 
>> I don't see any easy way to find the Iceberg version.
>> 
>> Should I update Iceberg using this script also in Pharo 7?
>> 
>> "Restore defaults"
>> Iceberg enableMetacelloIntegration: false.
>> MetacelloPharo30Platform select.
>> 
>> "Update metacello" 
>> Metacello new
>>   baseline: 'Metacello';
>>   repository: 'github://metacello/metacello:Pharo6.1/repository <>';
>>   onConflict: [:e | e useIncoming ];
>>   get;
>>   load.
>> 
>> "Update iceberg"
>>  #(
>> 'Iceberg-UI' 
>> 'Iceberg-Plugin-GitHub' 
>> 'Iceberg-Plugin' 
>> 'Iceberg-Metacello-Integration' 
>> 'Iceberg-Libgit-Tonel' 
>> 'Iceberg-Libgit-Filetree' 
>> 'Iceberg-Libgit' 
>> 'Iceberg' 
>> 'LibGit-Core') 
>> do: [ :each | (each asPackageIfAbsent: [ nil ]) ifNotNil: #removeFromSystem 
>> ].
>> Metacello new
>>   baseline: 'Iceberg';
>>   repository: 'github://pharo-vcs/iceberg:v0.6 <>';
>>   load.
>> 
>> 2017-10-17 6:46 GMT-03:00 Hernán Morales Durand > >:
>> Hi Esteban,
>> 
>> This one:
>> 
>> wget -O- get.pharo.org/70+vm  | bash -
>> 
>> 2017-10-17 3:36 GMT-03:00 Esteban Lorenzano > >:
>> which Pharo version (and Iceberg version) do you have?
>> 
>> Esteban
>> 
>>> On 17 Oct 2017, at 04:36, Hernán Morales Durand >> > wrote:
>>> 
>>> Hi Guille,
>>> 
>>> In 
>>> https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to-Pharo
>>>  
>>> 
>>> 
>>> This part is not working for me: "Go back to iceberg, right click on the 
>>> pharo repository and go to the Pharo entry. You'll see the option Create 
>>> new branch from Fogbugz issue."
>>> 
>>> Because there is no such "Pharo" option in the menu. See the attached 
>>> screenshot.
>>> 
>>> Did I miss something?
>>> Any suggestion?
>>> 
>>> 
>>> 2017-08-10 12:17 GMT-03:00 Guillermo Polito >> >:
>>> Hi, 
>>> 
>>> I've made some write up for the pharo part (not metacello or external 
>>> projects)
>>> 
>>> https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to-Pharo
>>>  
>>> 
>>> 
>>> Of course, expect bugs on it :) Not everything is smooth. If you have 
>>> comments, they are welcome.
>>> 
>>> Guille
>>> 
>>> -- 
>>>
>>> Guille Polito
>>> 
>>> Research Engineer
>>> French National Center for Scientific Research - http://www.cnrs.fr 
>>> 
>>> 
>>> 
>>> Web: http://guillep.github.io 
>>> Phone: +33 06 52 70 66 13 
>>> 
>> 
>> 
>> 
> 
> 

Re: [Pharo-dev] Writeup: how to contribute to Pharo

[Guillermo Polito]

On Tue, Oct 17, 2017 at 12:42 PM, Hernán Morales Durand <
hernan.mora...@gmail.com> wrote:

> Thank you Esteban, that was the problem! :)
>
> Maybe guille wants to clarify the correct remote repository in the page:
> https://github.com/guillep/PharoIntegrationProcess/wiki/
> Contribute-a-fix-to-Pharo after "You can click on the *Add remote* option
> and configure a remote with a name and repository url."
>

Done that.

Can you check if that's ok?


>
> Another thing. I created a PR with a fix for this bug :
> https://pharo.fogbugz.com/f/cases/17754/CheckBoxModel-
> RadioButtonModel-ignore-disable following the guide to the Step 3.
> However I couldn't view any PR in my Github page (see attach).
>
> Do I miss something?
>
>
> 2017-10-17 6:53 GMT-03:00 Esteban Lorenzano :
>
>> no is ok.
>> with the pharo version I know the iceberg version :)
>>
>> anyway your problem is that the remote for pharo is bad.
>>
>> you added g...@github.com:pharo/pharo.git and I do not think that exists.
>> Correct one is:
>>
>> g...@github.com:pharo-project/pharo.git
>>
>> Esteban
>>
>>
>> On 17 Oct 2017, at 11:51, Hernán Morales Durand 
>> wrote:
>>
>> I don't see any easy way to find the Iceberg version.
>>
>> Should I update Iceberg using this script also in Pharo 7?
>>
>> "Restore defaults"
>> Iceberg enableMetacelloIntegration: false.
>> MetacelloPharo30Platform select.
>>
>> "Update metacello"
>> Metacello new
>>   baseline: 'Metacello';
>>   repository: 'github://metacello/metacello:Pharo6.1/repository';
>>   onConflict: [:e | e useIncoming ];
>>   get;
>>   load.
>>
>> "Update iceberg"
>>  #(
>> 'Iceberg-UI'
>> 'Iceberg-Plugin-GitHub'
>> 'Iceberg-Plugin'
>> 'Iceberg-Metacello-Integration'
>> 'Iceberg-Libgit-Tonel'
>> 'Iceberg-Libgit-Filetree'
>> 'Iceberg-Libgit'
>> 'Iceberg'
>> 'LibGit-Core')
>> do: [ :each | (each asPackageIfAbsent: [ nil ]) ifNotNil:
>> #removeFromSystem ].
>> Metacello new
>>   baseline: 'Iceberg';
>>   repository: 'github://pharo-vcs/iceberg:v0.6';
>>   load.
>>
>> 2017-10-17 6:46 GMT-03:00 Hernán Morales Durand > >:
>>
>>> Hi Esteban,
>>>
>>> This one:
>>>
>>> wget -O- get.pharo.org/70+vm | bash -
>>>
>>> 2017-10-17 3:36 GMT-03:00 Esteban Lorenzano :
>>>
 which Pharo version (and Iceberg version) do you have?

 Esteban

 On 17 Oct 2017, at 04:36, Hernán Morales Durand <
 hernan.mora...@gmail.com> wrote:

 Hi Guille,

 In https://github.com/guillep/PharoIntegrationProcess/wiki/Cont
 ribute-a-fix-to-Pharo

 This part is not working for me: "Go back to iceberg, right click on
 the pharo repository and go to the *Pharo* entry. You'll see the
 option *Create new branch from Fogbugz issue*."

 Because there is no such "Pharo" option in the menu. See the attached
 screenshot.

 Did I miss something?
 Any suggestion?


 2017-08-10 12:17 GMT-03:00 Guillermo Polito 
 :

> Hi,
>
> I've made some write up for the pharo part (not metacello or external
> projects)
>
> https://github.com/guillep/PharoIntegrationProcess/wiki/Cont
> ribute-a-fix-to-Pharo
>
> Of course, expect bugs on it :) Not everything is smooth. If you have
> comments, they are welcome.
>
> Guille
>
> --
>
> Guille Polito
>
> Research Engineer
> French National Center for Scientific Research - *http://www.cnrs.fr*
> 
>
>
> *Web:* *http://guillep.github.io* 
> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>

 



>>>
>>
>>
>


-- 



Guille Polito

Research Engineer

Centre de Recherche en Informatique, Signal et Automatique de Lille

CRIStAL - UMR 9189

French National Center for Scientific Research - *http://www.cnrs.fr
*


*Web:* *http://guillep.github.io* 

*Phone: *+33 06 52 70 66 13