Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

BTW I do not understand why I have changes that I do not do in my image it displays the changes with a dot and the end. And also I do not get why the class comment get changed when I do not do anything. Do you experience the same? BTW I did the pull from pharo and push to my fork by hand to

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

Sure I need because I stage my work. So I need something to be integrated to use it. On Sat, Dec 16, 2017 at 6:53 PM, Esteban Lorenzano wrote: > > >> On 16 Dec 2017, at 17:55, Stephane Ducasse wrote: >> >> Hi Esteban >> >> Now how can I maintain my

Re: [Pharo-dev] Does pharo build not retry anymore?

tx them too. This is great to be surrounded by all you guys! On Sat, Dec 16, 2017 at 8:22 PM, Pavel Krivanek wrote: > The UI Manager problem was fixed by Pablo and Guille > > -- Pavel > > 2017-12-16 13:06 GMT+01:00 Stephane Ducasse : > >> tx

Re: [Pharo-dev] Drag and drop of methods

Thanks cyril. This is strange. May be this is due to the change of denis to improve spec. On Sat, Dec 16, 2017 at 7:37 PM, Cyril Ferlicot D. wrote: > Hi, > > In the latest Pharo 7 I cannot drag and drop methods anymore in Nautilus. > > Pharo version: >

Re: [Pharo-dev] Does pharo build not retry anymore?

The UI Manager problem was fixed by Pablo and Guille -- Pavel 2017-12-16 13:06 GMT+01:00 Stephane Ducasse : > tx pavel > > On Sat, Dec 16, 2017 at 9:25 AM, Pavel Krivanek > wrote: > >> The problems were related UIManager initialization and

[Pharo-dev] Drag and drop of methods

Hi, In the latest Pharo 7 I cannot drag and drop methods anymore in Nautilus. Pharo version: Pharo-7.0+alpha.build.389.sha.e642e96a93951b2765dc808a512b81dc3d52e150 (32 Bit) Stack: TransferMorph(Object)>>doesNotUnderstand: #buildWithSpec

[Pharo-dev] [Pharo 7.0-dev] Build #389: SUCCESS

There is a new Pharo build available! The status of the build #389 was: SUCCESS. Could not extract further issue information from commit message: Tx. Indeed it is better that way Build Url:

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

> On 16 Dec 2017, at 17:24, Stephane Ducasse wrote: > > OK so I restarted everything from scratch: > - deleted my fork > - reforked > - clone pharo again > - here is some feedback > > In the tutorial add /pharo + src in the screenshot > > > Then when I add the local

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

> On 16 Dec 2017, at 17:32, Stephane Ducasse wrote: > > I did a little pass on the wiki to make the flow clearer cool! :) > > > On Sat, Dec 16, 2017 at 5:26 PM, Stephane Ducasse > wrote: >> In the tutorial: >> >> - Put a little heading

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

> On 16 Dec 2017, at 17:39, Stephane Ducasse wrote: > > I committed my code for issue 20861 and I do not understand what I see > > I do not understand why I get local changes with empty packages. :( that’s a bug: there are no changes to commit (which is correct), but

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

> On 16 Dec 2017, at 17:55, Stephane Ducasse wrote: > > Hi Esteban > > Now how can I maintain my fork up to date? there is a “synchronise repositories” option there, at the side of “create branch from fogbugz”. > This is not in the tutorial and to me it was a major

[Pharo-dev] [Pharo 7.0-dev] Build #388: SUCCESS

There is a new Pharo build available! The status of the build #388 was: SUCCESS. Could not extract further issue information from commit message: Look nicer. And tx! Build Url:

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

I clicked on pharo-project remote and I did fetch. thinking stupidly that it will update my local repo. And I get the following and I do not understand whay I get 1965 not published. and I do not Then I siwtched branch and went back to development. and I should be able to now push to my

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

Hi Esteban Now how can I maintain my fork up to date? This is not in the tutorial and to me it was a major problem and a big source of pain. Stef On Sat, Dec 16, 2017 at 5:39 PM, Stephane Ducasse wrote: > I committed my code for issue 20861 and I do not understand what

Re: [Pharo-dev] Implementors of margins in GLMRubScrolledTextBrick

Ok so since I paid attention and rewrote all the margins: invocations I think that my changes will not break On Fri, Dec 15, 2017 at 9:32 PM, Stephane Ducasse wrote: > Argh! I did not thought about it. > So it may means that my changes are breaking the system. > Aliaksei

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

I did a little pass on the wiki to make the flow clearer On Sat, Dec 16, 2017 at 5:26 PM, Stephane Ducasse wrote: > In the tutorial: > > - Put a little heading before > > "You need to add pharo repository as a remote > (g...@github.com:pharo-project/pharo.git)." > > On

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

In the tutorial: - Put a little heading before "You need to add pharo repository as a remote (g...@github.com:pharo-project/pharo.git)." On Sat, Dec 16, 2017 at 5:25 PM, Stephane Ducasse wrote: > I double clicked and it did a massive amount of stuff and finally told >

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

I double clicked and it did a massive amount of stuff and finally told me that it is up to date. On Sat, Dec 16, 2017 at 5:24 PM, Stephane Ducasse wrote: > OK so I restarted everything from scratch: > - deleted my fork > - reforked > - clone pharo again > - here is some

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

OK so I restarted everything from scratch: - deleted my fork - reforked - clone pharo again - here is some feedback In the tutorial add /pharo + src in the screenshot Then when I add the local repository I get uncommited changes and I do not understand why? On Sat, Dec 16, 2017 at 9:57 AM,

Re: [Pharo-dev] [Pharo 7.0-dev] Build #381: 20796-String-should-understand-readStreamDowriteStreamDo-to-be-polymorph-with-FileReference

Hi Stef, On 16 December 2017 at 16:58, Stephane Ducasse wrote: > So I would like to understand (sincerly) what was the problem and what > is the gain? > I learned that we can ask a collection a readStream and writeStream already. > And now we can do anyCollection

Re: [Pharo-dev] [Pharo 7.0-dev] Build #381: 20796-String-should-understand-readStreamDowriteStreamDo-to-be-polymorph-with-FileReference

So I would like to understand (sincerly) what was the problem and what is the gain? I learned that we can ask a collection a readStream and writeStream already. And now we can do anyCollection readStreamDo: and writeStreamDo: Why not? On Sat, Dec 16, 2017 at 4:42 PM, Stephane Ducasse

Re: [Pharo-dev] [Pharo 7.0-dev] Build #381: 20796-String-should-understand-readStreamDowriteStreamDo-to-be-polymorph-with-FileReference

Hi Do we really want this? I do not understand why a string is a fileReference? String has far too many methods and we are even adding more and I do not understand why. Stef On Thu, Dec 14, 2017 at 12:01 PM, wrote: > There is a new Pharo build available! > >

Re: [Pharo-dev] Epicea feedback - save points

El 16 dic. 2017 5:04 AM, "Stephane Ducasse" escribió: I love epicea :) Did you see that now people use my extension to generate docs :) no i didnt! how could i see that? Stef On Sat, Dec 16, 2017 at 9:03 AM, Stephane Ducasse wrote: > Thanks

[Pharo-dev] [Pharo 7.0-dev] Build #387: 20870-Spec-FastTable-badly-support-drag-and-drop

There is a new Pharo build available! The status of the build #387 was: FAILURE. The Pull Request #608 was integrated: "20870-Spec-FastTable-badly-support-drag-and-drop" Pull request url: https://github.com/pharo-project/pharo/pull/608 Issue Url: https://pharo.fogbugz.com/f/cases/20870

[Pharo-dev] [Pharo 7.0-dev] Build #386: 20872-WidgetExamples-classexampleDialogs-is-broken-in-Pharo-7

There is a new Pharo build available! The status of the build #386 was: SUCCESS. The Pull Request #610 was integrated: "20872-WidgetExamples-classexampleDialogs-is-broken-in-Pharo-7" Pull request url: https://github.com/pharo-project/pharo/pull/610 Issue Url:

Re: [Pharo-dev] Does pharo build not retry anymore?

tx pavel On Sat, Dec 16, 2017 at 9:25 AM, Pavel Krivanek wrote: > The problems were related UIManager initialization and consequences of > the opening of the Welcome window. > > -- Pavel > > 2017-12-16 9:12 GMT+01:00 Stephane Ducasse : > >>

Re: [Pharo-dev] Do we have this iterator?

So true :) Stef On Sat, Dec 16, 2017 at 12:12 PM, Ben Coman wrote: > > > On 16 December 2017 at 17:28, Nicolas Cellier > wrote: >> >> Never try to read regexp, it's write only > > > its highly susceptible to Kernighan's Lever to shoot

Re: [Pharo-dev] Do we have this iterator?

On 16 December 2017 at 17:28, Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com> wrote: > Never try to read regexp, it's write only > its highly susceptible to Kernighan's Lever to shoot yourself in the foot... "You separate the bullet from the gun with a hyperoptimized regexp, and then

Re: [Pharo-dev] Do we have this iterator?

Never try to read regexp, it's write only 2017-12-16 9:09 GMT+01:00 Stephane Ducasse : > ouaaahh ;) > My problem was that I had complex lines as elements. and I will not be > able to remember and express anything with regex > > On Tue, Dec 12, 2017 at 4:36 PM, Martin

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

> On 16 Dec 2017, at 09:42, Alistair Grant wrote: > > Hi Esteban, > > On 16 December 2017 at 09:05, Esteban Lorenzano > wrote: >> >> >>> On 15 Dec 2017, at 17:37, Alistair Grant wrote: >>>

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

Hi Esteban, On 16 December 2017 at 09:05, Esteban Lorenzano wrote: > > >> On 15 Dec 2017, at 17:37, Alistair Grant wrote: >> >> Hi Esteban, >> >> I had no problems following the process (Ubuntu 16.04, >> Pharo7.0-32bit-e175bc2.image, fogbugz 20872).

Re: [Pharo-dev] Does pharo build not retry anymore?

The problems were related UIManager initialization and consequences of the opening of the Welcome window. -- Pavel 2017-12-16 9:12 GMT+01:00 Stephane Ducasse : > Pavel what was the problem? > > Stef > > > On Tue, Dec 12, 2017 at 9:34 PM, Pavel Krivanek

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

Yes now I have some pending commits that I do not want to lose so I will fileout them and publish them. Stef On Sat, Dec 16, 2017 at 9:19 AM, Esteban Lorenzano wrote: > > > On 16 Dec 2017, at 09:15, Esteban Lorenzano wrote: > > download latest image

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

> On 16 Dec 2017, at 09:15, Esteban Lorenzano wrote: > > download latest image and follow the steps explained here: > > https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo > side

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

download latest image and follow the steps explained here: https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo Esteban > On 16 Dec 2017, at 09:07, Stephane Ducasse wrote: > >

Re: [Pharo-dev] Does pharo build not retry anymore?

Pavel what was the problem? Stef On Tue, Dec 12, 2017 at 9:34 PM, Pavel Krivanek wrote: > The variable value was reverted to the original value. Thanks. > > -- Pavel > > 2017-12-12 20:13 GMT+01:00 Pavel Krivanek : > >> Yes, with Marcus we

Re: [Pharo-dev] [Pharo6][CI] test runs on submitted slices works again

Thanks you guys! On Wed, Dec 13, 2017 at 1:08 PM, Marcus Denker wrote: > Hi, > > Pavel fixed the test runner (the monkey) for Pharo6. That means, back ports > and fixes now can be checked > as they used to: > > -> submit slice > -> put issue on “fix review needed” >

Re: [Pharo-dev] Do we have this iterator?

ouaaahh ;) My problem was that I had complex lines as elements. and I will not be able to remember and express anything with regex On Tue, Dec 12, 2017 at 4:36 PM, Martin Dias wrote: > If your input was a string instead of a list of lines, you had: > > '[^4]*4|.+'

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

esteban to try the new way. What should I do? Just download a new version or reclone? May be I will refork and reclone to be sure. Stef On Sat, Dec 16, 2017 at 9:05 AM, Esteban Lorenzano wrote: > > >> On 15 Dec 2017, at 17:37, Alistair Grant wrote:

Re: [Pharo-dev] Moving from mc to tonel?

It would be great to be able to sanitize the files. We should get a test about tonel misbehavior. Stef On Thu, Dec 14, 2017 at 3:11 PM, Henrik Sperre Johansen wrote: > Stephan Eggermont-3 wrote >> On 05-12-17 08:59, Peter Uhnák wrote: >>> > In my case, it turned

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

> On 15 Dec 2017, at 17:37, Alistair Grant wrote: > > Hi Esteban, > > I had no problems following the process (Ubuntu 16.04, > Pharo7.0-32bit-e175bc2.image, fogbugz 20872). :-) > > I guess that you have already thought of this, but... Is there any > reason why we

Re: [Pharo-dev] Epicea feedback - save points

I love epicea :) Did you see that now people use my extension to generate docs :) Stef On Sat, Dec 16, 2017 at 9:03 AM, Stephane Ducasse wrote: > Thanks Martin!!! > > On Wed, Dec 13, 2017 at 1:29 PM, Martin Dias wrote: >> Hi >> >> When you "save

Re: [Pharo-dev] Epicea feedback - save points

Thanks Martin!!! On Wed, Dec 13, 2017 at 1:29 PM, Martin Dias wrote: > Hi > > When you "save and close" or "save as..." then next changes will go to a new > log file. Then, they will have a new item of the left of the browser (as > Stef said). > When you just "save", I