Re: [Pharo-dev] About method comments

Hi, Stef I have an idea for this problem, 1. method should have it's comment like class comment 2. method comment has two versions, one for developer another for reader 3. developder's comment will be saved in source or changes file 4. reader's comment will be saved in its own file 5. system

Re: [Pharo-dev] Iceberg experience report - synchronising README change made on github

On 11 February 2018 at 02:28, Stephane Ducasse wrote: > > > > P.P.S. I think more thought needs to be given to whether mixing > > updates from both the remote and disk working directory in the one > > pane is beneficial? > > As an alternative, perhaps some

[Pharo-dev] [Pharo 7.0-dev] Build #520: 21280 Remove double dots in #cleanUpChangeSetForClassNames:

There is a new Pharo build available! The status of the build #520 was: SUCCESS. The Pull Request #834 was integrated: "21280 Remove double dots in #cleanUpChangeSetForClassNames:" Pull request url: https://github.com/pharo-project/pharo/pull/834 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #519: 21277 Improve comment for byteToUnicodeSpec and typo fix

There is a new Pharo build available! The status of the build #519 was: SUCCESS. The Pull Request #831 was integrated: "21277 Improve comment for byteToUnicodeSpec and typo fix" Pull request url: https://github.com/pharo-project/pharo/pull/831 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #518: 21268 Cleanup AST-Tests-Core package

There is a new Pharo build available! The status of the build #518 was: SUCCESS. The Pull Request #822 was integrated: "21268 Cleanup AST-Tests-Core package" Pull request url: https://github.com/pharo-project/pharo/pull/822 Issue Url: https://pharo.fogbugz.com/f/cases/21268 Build Url:

[Pharo-dev] [Pharo 7.0-dev] Build #517: 21266 Cleanup testAddMCPackageForCategoryAlreadyExistingDoesNotCreateAPackage

There is a new Pharo build available! The status of the build #517 was: SUCCESS. The Pull Request #820 was integrated: "21266 Cleanup testAddMCPackageForCategoryAlreadyExistingDoesNotCreateAPackage" Pull request url: https://github.com/pharo-project/pharo/pull/820 Issue Url:

Re: [Pharo-dev] interactive method definition (was Re: Calypso wishlist)

In fact I'm stupid because I already coded it by extending the parser and I lost the code. I should look around or redo it. On Sat, Feb 10, 2018 at 7:10 PM, Stephane Ducasse wrote: >> Is this your ideal, or mainly to align with Tonel? Because it seems Tonel >> was

Re: [Pharo-dev] Iceberg experience report - synchronising README change made on github

> > P.P.S. I think more thought needs to be given to whether mixing > updates from both the remote and disk working directory in the one > pane is beneficial? > As an alternative, perhaps some side-scrolling GTInspector-like panes >Image <--> Working Directory <--> Remote <--> Server(github)

Re: [Pharo-dev] interactive method definition (was Re: Calypso wishlist)

> Is this your ideal, or mainly to align with Tonel? Because it seems Tonel > was developed > without much consideration of interactive method definition -- which is fine > in as much as > Tonel was designed to quickly overcome a specific problem with Windows+Git, > but it > Tonel shouldn't be

[Pharo-dev] Thanks for the fix of line selection in playground...

Now no need to select the line to execute it a pain and time saver Tx!

[Pharo-dev] Ring2

Hello Pavel and all, I wonder what's the best way to try Ring2 and maybe do some experiment on top of it. Is it ok if I load master branch of https://github.com/pavel-krivanek/Ring2 in Pharo 6.1? or should I load it in Pharo 7? I also see there are several branches in the repo. I'd like to load