Re: [Pharo-dev] Deploying using the latest minimal image of Pharo (6.1)

My idea was even to create objects that generate even bash scripts and all the rest but have objects that we can control and probably to be loaded in another image. I just hate all the undebuggable scripts. On Fri, Nov 24, 2017 at 3:16 AM, Ben Coman wrote: > > > On 24

Re: [Pharo-dev] [Pharo-users] I love the launcher!!!!

Yes I do something similar to ben. Stef On Fri, Nov 24, 2017 at 4:43 AM, Ben Coman wrote: > Every time I investigate an issue from the tracker, I start with a new fresh > image. > Often its useful to track down which build introduced a bug, so I need to > bisect the last

Re: [Pharo-dev] Bloc Tutorial Feedback

Thanks Sean I will have a look when I get some time. On Fri, Nov 24, 2017 at 4:41 AM, Sean P. DeNigris wrote: > I did a native English review pass on the first half and submitted a PR on > GH. > > A few other items: > - When clipping is used to initially draw the card

Re: [Pharo-dev] Bloc Tutorial Feedback

Aliaksei told me that he should do another pass to add animations and layout chapters. I imagine that he did some refactorings so this is good that you spotted them. On Fri, Nov 24, 2017 at 8:36 AM, Stephane Ducasse wrote: > Thanks Sean I will have a look when I get

Re: [Pharo-dev] Deploying using the latest minimal image of Pharo (6.1)

On 24 November 2017 at 05:13, despotadesdibujau wrote: > >Hi Gabriel > > >This is cool. > >Thanks for sharing it with us. > >I really want an object responsible for deploying an app. :) > >Your effort is nice in that directory. Keep pushing > > >Stef > Thanks!!! > >

Re: [Pharo-dev] [Pharo-users] I love the launcher!!!!

Every time I investigate an issue from the tracker, I start with a new fresh image. Often its useful to track down which build introduced a bug, so I need to bisect the last 500 builds or so. I select a build version from the "Template" side and create an image named "CaseC-B" where C

[Pharo-dev] Bloc Tutorial Feedback

I did a native English review pass on the first half and submitted a PR on GH. A few other items: - When clipping is used to initially draw the card outline as a rounded rect, instead of using the rect as a path, it's not immediately obvious why this is done. It's only way later when the cross is

Re: [Pharo-dev] [PHARO 7.0A] NEXT ENHANCEMENTS

Yes, very. Phil On Thu, Nov 23, 2017 at 12:26 PM, Alexandre Bergel wrote: > Impressive!! > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Nov 23, 2017,

[Pharo-dev] [PHARO 7.0A] NEXT ENHANCEMENTS

eport period: 5 November 2017 to 23 November 2017 * 20739-Remove-dead-stream-primitives >> https://pharo.fogbugz.com/f/cases/20739/Remove-dead-stream-primitives Issue URL: https://pharo.fogbugz.com/f/cases/20739 PR URL: https://github.com/pharo-project/pharo/pull/524 Diff

Re: [Pharo-dev] [PHARO 7.0A] NEXT ENHANCEMENTS

Impressive!! -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Nov 23, 2017, at 7:12 AM, Stephane Ducasse wrote: > > eport period: 5 November 2017 to 23 November 2017 >

Re: [Pharo-dev] Advent of code

I made an adventofcode channel in Discord. Time for bots... Phil On Nov 22, 2017 21:25, "Stephane Ducasse" wrote: > Ok can you put a link on the advent of code web page? > > On Wed, Nov 22, 2017 at 9:11 PM, Julien > wrote: > >> I’ll write a

[Pharo-dev] I love the launcher!!!!

Hi I love the PharoLauncher. It helps me to manage my parallel development and projects. We should put a link on the Pharo web site because http://files.pharo.org/platform/launcher/ is arcane. Stef

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo TechTalk 21 Nov: Discord Demo

On Wed, Nov 22, 2017 at 6:03 PM Juraj Kubelka wrote: > > On Nov 21, 2017, at 19:54, Dimitris Chloupis > wrote: > > Well done :) > > Now you can make a discord client inside the Pharo image if you want. > > > Exactly :-) I am looking for

[Pharo-dev] [Pharo 7.0-dev] Build #319: 20742 Unused temps in Morph, MalSccNodeDecomposition and MethodNode

There is a new Pharo build available! The status of the build #319 was: SUCCESS. The Pull Request #525 was integrated: "20742 Unused temps in Morph, MalSccNodeDecomposition and MethodNode" Pull request url: https://github.com/pharo-project/pharo/pull/525 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #321: 17641-remove-HasNewFinalization-class-var-from-WeakFinalizationList

There is a new Pharo build available! The status of the build #321 was: SUCCESS. The Pull Request #520 was integrated: "17641-remove-HasNewFinalization-class-var-from-WeakFinalizationList" Pull request url: https://github.com/pharo-project/pharo/pull/520 Issue Url:

Re: [Pharo-dev] nil inspect

> On 23 Nov 2017, at 17:01, Dimitris Chloupis wrote: > > yeah i see it now, I asked earlier on because I did not have access to a > computer (was replying from my tablet). I see now that is an object, though > its weird that nil is an instance of UndefinedObject but

[Pharo-dev] [Pharo 7.0-dev] Build #322: 18217-Settings-What-are-Renkaku-rules

There is a new Pharo build available! The status of the build #322 was: SUCCESS. The Pull Request #527 was integrated: "18217-Settings-What-are-Renkaku-rules" Pull request url: https://github.com/pharo-project/pharo/pull/527 Issue Url: https://pharo.fogbugz.com/f/cases/18217 Build Url:

[Pharo-dev] [Pharo 7.0-dev] Build #320: 20736-update-iceberg-to-063

There is a new Pharo build available! The status of the build #320 was: SUCCESS. The Pull Request #518 was integrated: "20736-update-iceberg-to-063" Pull request url: https://github.com/pharo-project/pharo/pull/518 Issue Url: https://pharo.fogbugz.com/f/cases/20736 Build Url:

Re: [Pharo-dev] [PHARO 7.0A] NEXT ENHANCEMENTS

What is not visible in the list are the many enhancements happening also on Calypso, Bloc,   Grease and many many others. Nonetheless the core image still needs love from more people. Remember even the smallest change can make a difference and shape the future. Also "a contribution per day

Re: [Pharo-dev] OpalCompiler evaluate speed

2017-11-22 0:31 GMT+01:00 Ben Coman : > > > On 22 November 2017 at 05:49, Nicolas Cellier gmail.com> wrote: > >> >> >> 2017-11-21 14:19 GMT+01:00 Nicolas Cellier > l.com>: >> >>> I have an

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo TechTalk 21 Nov: Discord Demo

Hi, the new version is available here: https://www.youtube.com/watch?v=y1EzOnfHUe0 Hopefully it helps :-) Juraj > On Nov 22, 2017, at 15:45, Sean P. DeNigris wrote: > > Juraj Kubelka wrote >> I will upload recording I have

Re: [Pharo-dev] OpalCompiler evaluate speed

Hi Nicolas. Just some comments: Another thing you can try is to remove the allocation of Opal's IR. It seems people use the IR only through the IRBuilder, so the API can be kept but it can generate directly bytecode instead of IR then bytecode. Removing those allocations would speed things up.

Re: [Pharo-dev] [PHARO 7.0A] NEXT ENHANCEMENTS

+ 1 :) On Thu, Nov 23, 2017 at 8:53 PM, Torsten Bergmann wrote: > What is not visible in the list are the many enhancements happening also on > Calypso, Bloc, > Grease and many many others. > > Nonetheless the core image still needs love from more people. Remember even > the

Re: [Pharo-dev] Deploying using the latest minimal image of Pharo (6.1)

Yes your second scenario looks cool to me :). Keep us informed because this is really exciting. Stef On Thu, Nov 23, 2017 at 10:13 PM, despotadesdibujau wrote: >>Hi Gabriel > >>This is cool. >>Thanks for sharing it with us. >>I really want an object responsible for

Re: [Pharo-dev] Deploying using the latest minimal image of Pharo (6.1)

>Hi Gabriel >This is cool. >Thanks for sharing it with us. >I really want an object responsible for deploying an app. :) >Your effort is nice in that directory. Keep pushing >Stef Thanks!!! Maxi Tabacman suggests me to reify the deployment process. I thought of something like to get up a

Re: [Pharo-dev] Bloc Naming Suggestion

In Opal I would keep it because this is about error and warning and you are not all the time manipulating them while for Bloc as soon as you use text you will have to. On Wed, Nov 22, 2017 at 9:37 PM, Nicolas Cellier wrote: > I see same kind of names in Opal

Re: [Pharo-dev] Problem with primitive instVarAt: / instVarAt:put:, what should we do ?

Did you talk with marcus? On Wed, Nov 22, 2017 at 10:12 PM, Clément Bera wrote: > > > On Wed, Nov 22, 2017 at 9:05 PM, Stephane Ducasse > wrote: >> >> Hi clement >> >> you should discuss with marcus. I had the impression that he was >> thinking

Re: [Pharo-dev] Problem with primitive instVarAt: / instVarAt:put:, what should we do ?

On Fri, Nov 24, 2017 at 12:00 AM, Stephane Ducasse wrote: > Did you talk with marcus? > I don't understand the connection between slots and this problem with primitives. > > > On Wed, Nov 22, 2017 at 10:12 PM, Clément Bera > wrote: > > > > > >