[Pharo-dev] Help: Implementing core classes for Redline Smalltalk ...

Hi Pharo People, Redline Smalltalk is a Smalltalk for the Java Virtual Machine. The compiler is 90% complete. Would anyone like to help implement the core runtime classes? No Java involved. If you would like to lend a hand please email object at redline.st - James. -- View this message in

Re: [Pharo-dev] Epicea user experience report

On Mon, Jan 23, 2017 at 8:44 PM, Ben Coman wrote: > On Tue, Jan 24, 2017 at 6:43 AM, Martin Dias wrote: > > > > > > > > On Mon, Jan 23, 2017 at 2:44 PM, Ben Coman wrote: > >> > >> On Wed, Jan 11, 2017 at 3:29 PM, Martin Dias

Re: [Pharo-dev] Epicea user experience report

On Tue, Jan 24, 2017 at 6:43 AM, Martin Dias wrote: > > > > On Mon, Jan 23, 2017 at 2:44 PM, Ben Coman wrote: >> >> On Wed, Jan 11, 2017 at 3:29 PM, Martin Dias wrote: >>> >>> I created an entry in fogbugz and had progress: >>>

Re: [Pharo-dev] Epicea user experience report

On Mon, Jan 23, 2017 at 2:44 PM, Ben Coman wrote: > On Wed, Jan 11, 2017 at 3:29 PM, Martin Dias wrote: > >> I created an entry in fogbugz and had progress: >> >> https://pharo.fogbugz.com/f/cases/19534/Unify-Epicea-UIs >> >> Cheers, >> Martin >> > >

Re: [Pharo-dev] AioPlugin not present

--- Begin Message --- Thanks Esteban, I'm gonna download the vm, try the plugin and feedback you. Thanks Davide EstebanLM wrote >> On 23 Jan 2017, at 00:56, David T. Lewis > lewis@.msen > wrote: >> >> On Sun, Jan 22, 2017 at 05:00:04PM +0100, Thierry Goubier wrote: >>> >>> Le 22/01/2017 ?

Re: [Pharo-dev] Pharo by Example 50 released!

Congrats for the hard work ! On Sun, Jan 22, 2017 at 4:53 PM, stepharong wrote: > https://pharoweekly.wordpress.com/2017/01/22/pharo-by-example-50-released/ > > Super special thanks to Nicolai Hess that pushed me to do the last steps to > release. > Thanks Nicolai your steady

Re: [Pharo-dev] Google summer of code

Thank you Uko to join the team :-) On Mon, Jan 23, 2017 at 5:15 PM, Yuriy Tymchuk wrote: > I can also update my projects and help with the application if needed (I was > a part of the application team for the last two years I think) > > Uko > > On 22 Jan 2017, at 16:33,

Re: [Pharo-dev] Collections and Kernel

On Tue, Jan 24, 2017 at 12:14 AM, Clément Bera wrote: > > > On Mon, Jan 23, 2017 at 3:55 PM, Pavel Krivanek > wrote: > >> I do not think that to have the package "Kernel" as the smallest system >> subset is the good way to go. The minimal system

Re: [Pharo-dev] Epicea user experience report

On Wed, Jan 11, 2017 at 3:29 PM, Martin Dias wrote: > I created an entry in fogbugz and had progress: > > https://pharo.fogbugz.com/f/cases/19534/Unify-Epicea-UIs > > Cheers, > Martin > hi Martin, I like the result - especially when opening a fresh image and directly

Re: [Pharo-dev] AST node replacement API

2017-01-23 17:00 GMT+01:00 Yuriy Tymchuk : > I think that we hacked too much :). I like how ParsetreeRewriter is > working, but I think that it would be nice to have some API to say: ok, I > have this node, now I want to replace it (maybe it should generate a new > changed

Re: [Pharo-dev] AST node replacement API

On 01/23/2017 10:00 AM, Yuriy Tymchuk wrote: I think that we hacked too much :). I like how ParsetreeRewriter is working, but I think that it would be nice to have some API to say: ok, I have this node, now I want to replace it (maybe it should generate a new changed tree), so the pattern

Re: [Pharo-dev] Google summer of code

I can also update my projects and help with the application if needed (I was a part of the application team for the last two years I think) Uko > On 22 Jan 2017, at 16:33, Jigyasa Grover wrote: > > Also, a good application is equally important as the list of clearly

Re: [Pharo-dev] Collections and Kernel

On Mon, Jan 23, 2017 at 3:55 PM, Pavel Krivanek wrote: > I do not think that to have the package "Kernel" as the smallest system > subset is the good way to go. The minimal system should be a set of > well-structured packages so it still makes sense to have packages

[Pharo-dev] [pharo-project/pharo-core] 24542a: 60353

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 24542ad3cedacbf19c06fec46ae34d8df5bbac84 https://github.com/pharo-project/pharo-core/commit/24542ad3cedacbf19c06fec46ae34d8df5bbac84 Author: Jenkins Build Server Date:

Re: [Pharo-dev] AST node replacement API

I think that we hacked too much :). I like how ParsetreeRewriter is working, but I think that it would be nice to have some API to say: ok, I have this node, now I want to replace it (maybe it should generate a new changed tree), so the pattern syntax would be more of a nice interface instead

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60353 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] AST node replacement API

On 01/23/2017 07:48 AM, Yuriy Tymchuk wrote: Hi everyone, does anyone have a better knowledge about replacing nodes in AST? Because what I saw is that there are methods like replaceSourceWith: that can be sent to an AST node with another AST node as a parameter. But this is not enough to

Re: [Pharo-dev] AST node replacement API

2017-01-23 14:48 GMT+01:00 Yuriy Tymchuk : > Hi everyone, > > does anyone have a better knowledge about replacing nodes in AST? Because > what I saw is that there are methods like replaceSourceWith: that can be > sent to an AST node with another AST node as a parameter. But

Re: [Pharo-dev] Collections and Kernel

I do not think that to have the package "Kernel" as the smallest system subset is the good way to go. The minimal system should be a set of well-structured packages so it still makes sense to have packages like Collections-* where some of them are supposed to be mandatory and others optional. So:

[Pharo-dev] Collections and Kernel

Hi everyone, As I am working on an optimising JIT compiler for the Cog VM written in Smalltalk and partly running in the Smalltalk runtime, I am very careful about dependencies. I would like to limit the dependencies of the optimiser to the Kernel. The main problem I have is that there are no

[Pharo-dev] [REMINDER] Pharo TechTalk tomorrow Jan 24 16h UTC

Hello all, This is a reminder for the next TechTalk who will be around Bloc/Brick. Alex, Glenn and/or Doru will be handling this… so specific details will come from them, but I suppose it will be more or less like last time: youtube live for presentations, questions/conversation over discord.

Re: [Pharo-dev] Esteban's ChangeLog week of 16 January 2017

Thanks Esteban. This is interesting to tune in on whats happening in vm and FFI. cheers -ben On Mon, Jan 23, 2017 at 4:00 PM, wrote: > Hello! > > This is my weekly ChangeLog, from 16 January 2017 to 22 January 2017. > You can see it in a better format by going here:

Re: [Pharo-dev] Esteban's ChangeLog week of 16 January 2017

Very good idea Esteban I think I will steal it On Mon, 23 Jan 2017 at 11:38, Guillermo Polito wrote: > I like the "talk to yourself" format :P > > On Mon, Jan 23, 2017 at 10:05 AM, Esteban Lorenzano > wrote: > > > On 23 Jan 2017, at 10:02,

Re: [Pharo-dev] Pharo by Example 50 released!

Thanks for your great effort guys. cheers -ben On Sun, Jan 22, 2017 at 11:53 PM, stepharong wrote: > https://pharoweekly.wordpress.com/2017/01/22/pharo-by-example-50-released/ > > Super special thanks to Nicolai Hess that pushed me to do the last steps > to release. > Thanks

Re: [Pharo-dev] [Pharo6] Issue tracker: Issues tagged Pharo6

I will check with Esteban this week for a plan with real dates… > On 23 Jan 2017, at 12:38, Peter Uhnak wrote: > > When is the release planned? > > Peter > > On Mon, Jan 23, 2017 at 11:58:19AM +0100, Marcus Denker wrote: >> Hi, >> >> To be able to release, we have to check

[Pharo-dev] [pharo-project/pharo-core] 87ff0d: 60352

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 87ff0de86204c116f3c523414a8b704dbae15097 https://github.com/pharo-project/pharo-core/commit/87ff0de86204c116f3c523414a8b704dbae15097 Author: Jenkins Build Server Date:

Re: [Pharo-dev] AioPlugin not present

2017-01-23 12:57 GMT+01:00 Esteban Lorenzano : > > On 23 Jan 2017, at 12:46, Thierry Goubier > wrote: > > > > 2017-01-23 12:40 GMT+01:00 Esteban Lorenzano : > >> >> On 23 Jan 2017, at 12:37, Thierry Goubier

Re: [Pharo-dev] AioPlugin not present

> On 23 Jan 2017, at 12:46, Thierry Goubier wrote: > > > > 2017-01-23 12:40 GMT+01:00 Esteban Lorenzano >: > >> On 23 Jan 2017, at 12:37, Thierry Goubier >

Re: [Pharo-dev] AioPlugin not present

> On 23 Jan 2017, at 12:37, Thierry Goubier wrote: > > > > 2017-01-23 12:26 GMT+01:00 Esteban Lorenzano >: > > > me neither :) > I added AioPlugin (as external) to all linux distributions… they will be >

Re: [Pharo-dev] [Pharo6] Issue tracker: Issues tagged Pharo6

When is the release planned? Peter On Mon, Jan 23, 2017 at 11:58:19AM +0100, Marcus Denker wrote: > Hi, > > To be able to release, we have to check which issues are real show-stoppers. > > As a first step, we will, this Friday, remove the Pharo6 Milestone tag from > *all* > issues that are

Re: [Pharo-dev] AioPlugin not present

2017-01-23 12:26 GMT+01:00 Esteban Lorenzano : > > > me neither :) > I added AioPlugin (as external) to all linux distributions… they will be > available in latest VMs. > > can someone test it? > I'll try. Where is the source for the current pharo vms? On github, pharo-vm?

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60351 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 5df8d2: 60351

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 5df8d27c02961279e12a65edc91131972f558c28 https://github.com/pharo-project/pharo-core/commit/5df8d27c02961279e12a65edc91131972f558c28 Author: Jenkins Build Server Date:

Re: [Pharo-dev] AioPlugin not present

> On 23 Jan 2017, at 00:56, David T. Lewis wrote: > > On Sun, Jan 22, 2017 at 05:00:04PM +0100, Thierry Goubier wrote: >> >> Le 22/01/2017 ? 15:50, Davide Varvello via Pharo-dev a ?crit : >>> Hi Thierry, >>> >>> I need it for the OSProcess. When my code calls OSProcess

[Pharo-dev] [Pharo6] Issue tracker: Issues tagged Pharo6

Hi, To be able to release, we have to check which issues are real show-stoppers. As a first step, we will, this Friday, remove the Pharo6 Milestone tag from *all* issues that are priority “would be nice” or lower.

[Pharo-dev] [pharo-project/pharo-core] 027c7d: 50766

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 027c7dab4499d4372baa890f035b850c1609fe98 https://github.com/pharo-project/pharo-core/commit/027c7dab4499d4372baa890f035b850c1609fe98 Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50766 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] [pharo-project/pharo-core] cfba43: 60350

> > Log Message: > --- > 60350 > 19556 Glamour version 4.31 > https://pharo.fogbugz.com/f/cases/19556 > Changes: - fixes example GLMBasicExamples>>#morphWithCustomInteraction - adds example GLMBasicExamples>>#changingTabsInComposite - case 19505 Setting the selection using

[Pharo-dev] [pharo-project/pharo-core] cfba43: 60350

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: cfba4311979120779437d6c45cac4fae377a4e07 https://github.com/pharo-project/pharo-core/commit/cfba4311979120779437d6c45cac4fae377a4e07 Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60350 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] Pharo by Example 50 released!

Great. This is a great entry point into Pharo. Please publicize it as widely as you can. Here is the announcement tweet that you can retweet: https://twitter.com/stephaneducasse/status/823195882770284545 Cheers, Doru > On Jan 22, 2017, at 4:53 PM, stepharong wrote: > >

Re: [Pharo-dev] [Pharo-users] Pharo by Example 50 released!

Yeh, thanks to all who made an effort :) On Sun, Jan 22, 2017 at 5:10 PM, Sven Van Caekenberghe wrote: > Great work, can't wait for the HTML version (to link to when answering > questions). > > Thank you ! > > > On 22 Jan 2017, at 16:53, stepharong wrote: > >

Re: [Pharo-dev] Esteban's ChangeLog week of 16 January 2017

I like the "talk to yourself" format :P On Mon, Jan 23, 2017 at 10:05 AM, Esteban Lorenzano wrote: > > On 23 Jan 2017, at 10:02, Stephane Ducasse > wrote: > > Tx a lot esteban! > This is so great. > > > thanks :) > > Showing what you are doing is

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60349 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] ada27b: 60349

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: ada27b978600e43ff5942b2a9191ced7ba74a8ff https://github.com/pharo-project/pharo-core/commit/ada27b978600e43ff5942b2a9191ced7ba74a8ff Author: Jenkins Build Server Date:

Re: [Pharo-dev] What happened to Pharo's Window?

2017-01-23 9:51 GMT+01:00 Cyril Ferlicot D. : > On 23/01/2017 08:57, Esteban Lorenzano wrote: > > it works for me (couple of bugs around in the examples) > > > > in macOS sierra > > in latest Pharo 6.0 > > in latest Pharo VM > > > > Esteban > > > > > > I have a white

Re: [Pharo-dev] Esteban's ChangeLog week of 16 January 2017

> On 23 Jan 2017, at 10:02, Stephane Ducasse wrote: > > Tx a lot esteban! > This is so great. thanks :) > Showing what you are doing is important. > Can you send this mail to the consortium mailing-list too? of course, this is a Pharo script after all ;) Esteban

Re: [Pharo-dev] Esteban's ChangeLog week of 16 January 2017

Tx a lot esteban! This is so great. Showing what you are doing is important. Can you send this mail to the consortium mailing-list too? On Mon, Jan 23, 2017 at 9:22 AM, Esteban Lorenzano wrote: > yeah, I’m aware I need to iterate on the text exporter to have some better >

Re: [Pharo-dev] What happened to Pharo's Window?

On 23/01/2017 08:57, Esteban Lorenzano wrote: > it works for me (couple of bugs around in the examples) > > in macOS sierra > in latest Pharo 6.0 > in latest Pharo VM > > Esteban > > I have a white screen until I click macOS ElCaptain Pharo 6.0 latest Pharo VM -- Cyril Ferlicot

Re: [Pharo-dev] What happened to Pharo's Window?

The window display seems to be OK on Fedora and Ubuntu (32-bit) for 60+vmLatest -- Pavel 2017-01-23 8:57 GMT+01:00 Esteban Lorenzano : > it works for me (couple of bugs around in the examples) > > in macOS sierra > in latest Pharo 6.0 > in latest Pharo VM > > Esteban > > On

Re: [Pharo-dev] Esteban's ChangeLog week of 16 January 2017

yeah, I’m aware I need to iterate on the text exporter to have some better output :P Esteban > On 23 Jan 2017, at 09:00, esteba...@gmail.com wrote: > > Hello! > > This is my weekly ChangeLog, from 16 January 2017 to 22 January 2017. > You can see it in a better format by going here:

Re: [Pharo-dev] PharoSpur32Vm

> On 22 Jan 2017, at 13:19, Nicolai Hess wrote: > > > > 2017-01-22 10:21 GMT+01:00 Clément Bera >: > Hi, > > I believe they're built from https://github.com/OpenSmalltalk/vm >

[Pharo-dev] Esteban's ChangeLog week of 16 January 2017

Hello! This is my weekly ChangeLog, from 16 January 2017 to 22 January 2017. You can see it in a better format by going here: http://log.smallworks.eu ChangeLog = 20 January 2017: * I'm still fixing a couple of final failing tests on iceberg, multi-remotes