Re: [Pharo-dev] memoized vs once

> On 26 Jan 2017, at 00:30, p...@highoctane.be wrote: > > SomeClass>>#initialize >self memoize: #someMethod:andParms:. > > and bingo, automatic method memoization keyed by the objects passed. > I had a prototype called “vigorous caching”. It worked for methods without parameters though

Re: [Pharo-dev] [ANN] Pharo Sprint Friday, Jan 27

> On 26 Jan 2017, at 14:30, Marcus Denker wrote: > > (this is a bit late… next will be announced earlier. I will start to put the > sprints as official > events on the assoc site, too) https://association.pharo.org/event-2447196

[Pharo-dev] [ANN] Pharo Sprint Friday, Jan 27

(this is a bit late… next will be announced earlier. I will start to put the sprints as official events on the assoc site, too) We will organize a Pharo sprint / Moose dojo Friday, 27 Jan, starting at 10:00am. (Local Time Paris). Goals of this sprint: - Clean issue tracker to prepare

Re: [Pharo-dev] Immutability support

Denis' idea is good. There is one problem with the implementation of jump though. MyClass>>iv iv := 1. [ 2 ] value. 1halt. MyClass new beReadOnlyObject ; iv When reaching the halt we see there is an extra nil on stack. I think this is better than the process hack, at least until we add VM

Re: [Pharo-dev] memoized vs once

Denis can we rename this selector? asMethodConst should be at least be renamed to asConstantMethod Hi Eliot. 2017-01-25 19:56 GMT+01:00 Eliot Miranda : Hi Ben, via FaceBook via twitter I hear you've coined BlockClosure>>#memoized. Allow me to beg you to rename

Re: [Pharo-dev] [Ann] PharmIDE: Pharo remote IDE to develop farm of Pharo images remotely

Denis Since I'm basically the head of the team that pays you :) I would really like to have a chance to talk about the name of this environment. Because we will have to market it to a lot of people so I would like to take the time to think about a name that looks like a name. Stef Hi. I

Re: [Pharo-dev] [bloc] addressing the moz2d issue

Hi, Then we will need Cairo + SDL2 (that does not work for us) + Freetype2 (for fonts) + Graphite (glyphs shaping technology in order to use them within vector graphics engine) + cross platform OpenGL / Vulkan context/device provider for hardware acceleration + implement Filters for effects

Re: [Pharo-dev] [Ann] Calypso update: method browser and better UI

Am 20.01.2017 um 14:12 schrieb Denis Kudriashov : > > And this is done. I just upload new stable version: > - source code shortcuts are managed by Calypso. I found simple hook how to > achieve this > - senders/implementors by source code shortcuts in method browser are now

[Pharo-dev] Odd (and wrong) implementation of Float>>sign

Pharo's implementation of Float>>sign is very odd, and rather disturbing. It answers 1 for positive, -1 for negative, and 0 for zero. Except for negative zero, for which it answers -1. This is asymmetric -- positive zero gets 0 but negative 0 gets -1? This does not seem correct. Both the ANSI

Re: [Pharo-dev] [bloc] addressing the moz2d issue

I think that instead of investigating gtk (yet another library to bind and carry around), it would be smarter to have Sparta back-end using an accelerated Cairo + pango. Why? Because - For example Cairo will not disappear in the future (here you will tell me that it does not have all the

Re: [Pharo-dev] memoized vs once

stepharong wrote: >can we rename this selector? >asMethodConst should be at least be renamed to asConstantMethod When you use "as {something}" then "something" depicts the result of the conversion message sent to an object. Like in #asNumber or #asString which shows to what the receiver will be

Re: [Pharo-dev] CALL for GSoC project proposals

We just add project proposals there? On Wed, Jan 25, 2017 at 11:19 AM, Stephane Ducasse wrote: > But I understand the process. > So I did a pass > > On Wed, Jan 25, 2017 at 11:05 AM, Stephane Ducasse < > stepharo.s...@gmail.com> wrote: > >> Hi yuriy >> >> you could have

Re: [Pharo-dev] Immutability support

> Am 26.01.2017 um 08:11 schrieb Clément Bera : > > The "CAN'T REACH" comment is there because execution never reach that part of > the code. If you write code there, it will never be executed. The process > code performs a return without pushing any value on stack. >

Re: [Pharo-dev] Immutability support

*Sorry Clement, maybe I am stupid but it is not clear for me.* *If I put halt after "CAN'T REACH" I got debugger which means that it "can reach".* *Maybe by "CAN'T REACH" you mean that any return value will not be used? But it is not true: if I return something it will be result of original

Re: [Pharo-dev] Immutability support

> Am 26.01.2017 um 10:32 schrieb Clément Bera : > > > > On Thu, Jan 26, 2017 at 9:54 AM, Norbert Hartl > wrote: > >> Am 26.01.2017 um 08:11 schrieb Clément Bera >

Re: [Pharo-dev] Immutability support

Let's rewrite the method this way: attemptToAssign: value withIndex: index | process | "INSERT CODE HERE" process := Processor activeProcess. [ process suspendedContext: process suspendedContext sender ] fork. Processor yield. self error: 'should not be reached'. This way it's

Re: [Pharo-dev] Immutability support

2017-01-26 8:11 GMT+01:00 Clément Bera : > The "CAN'T REACH" comment is there because execution never reach that part > of the code. If you write code there, it will never be executed. The > process code performs a return without pushing any value on stack. > Sorry

Re: [Pharo-dev] Immutability support

On Thu, Jan 26, 2017 at 9:54 AM, Norbert Hartl wrote: > > Am 26.01.2017 um 08:11 schrieb Clément Bera : > > The "CAN'T REACH" comment is there because execution never reach that part > of the code. If you write code there, it will never be executed.

Re: [Pharo-dev] Immutability support

Hi Clement: > On 26 Jan 2017, at 10:59, Clément Bera wrote: > > Let's rewrite the method this way: > > attemptToAssign: value withIndex: index > | process | > "INSERT CODE HERE" > process := Processor activeProcess. > [ process

Re: [Pharo-dev] Immutability support

2017-01-26 10:59 GMT+01:00 Clément Bera : > Let's rewrite the method this way: > > attemptToAssign: value withIndex: index > | process | > "INSERT CODE HERE" > process := Processor activeProcess. > [ process suspendedContext: process suspendedContext sender

Re: [Pharo-dev] Odd (and wrong) implementation of Float>>sign

2017-01-26 21:22 GMT+01:00 Martin McClure : > Pharo's implementation of Float>>sign is very odd, and rather disturbing. > > It answers 1 for positive, -1 for negative, and 0 for zero. Except for > negative zero, for which it answers -1. This is asymmetric -- positive > zero

Re: [Pharo-dev] [bloc] addressing the moz2d issue

Hi Stef, As explained before Brick is where the main focus will be next. I think that once the editor will be working, we should see more visible movement in that department. Cheers, Doru > On Jan 26, 2017, at 8:39 PM, stepharong wrote: > > I think that instead of

Re: [Pharo-dev] [bloc] addressing the moz2d issue

Hi Stef, There was a misunderstanding. Alex was just listing the need of underlying technologies for the features that Bloc already supports. Let’s restart this conversation. He will send an explanatory email. Cheers, Doru > On Jan 26, 2017, at 10:27 PM, stepharong wrote:

Re: [Pharo-dev] Immutability support

Guess the method is wrong given the comment. Shouldn't it be [param anyMask: 1] instead of [param anyMask: 2] ? Phil On Wed, Jan 25, 2017 at 2:14 PM, Clément Bera wrote: > I introduced the method #supportsWriteBarrier in Pharo 6. > > You can backport it if you want: >

Re: [Pharo-dev] memoized vs once

Hi Torsten, On Wed, Jan 25, 2017 at 2:45 PM, Torsten Bergmann wrote: > Hi, > > From my perspective: > > - I agree with Igor that "once" can be interpreted as "evaluate it only > once" as in > "Halt once". > > - I'm not sure but from the (now very distributed) discussion it is

Re: [Pharo-dev] [bloc] addressing the moz2d issue

Hi, Then we will need Cairo + SDL2 (that does not work for us) I do not get why SDL20 would not work for us while it is used by gaming engines. Are we that special? We built interactive applications for Thales with complex event touch and now suddenly "it does not work for us" TM. I

Re: [Pharo-dev] [bloc] addressing the moz2d issue

Hi, The mail from Alex is a bit cryptic. Alex, please send a more elaborate answer :). Cheers, Doru > On Jan 26, 2017, at 9:10 PM, Aliaksei Syrel wrote: > > Hi, > > Then we will need Cairo + SDL2 (that does not work for us) + Freetype2 (for > fonts) + Graphite

Re: [Pharo-dev] [Ann] Calypso update: method browser and better UI

2017-01-26 21:09 GMT+01:00 Bernhard Pieber : > > - no Spec text model anymore. Rubric widgets are used directly. It > improves speed of building text editors > This is really great. I love the Method Browser. I also forgot to show in demo that it is possible to drag window

Re: [Pharo-dev] memoized vs once

On Fri, Jan 27, 2017 at 4:32 AM, Eliot Miranda wrote: > > > Now, descending to the implementations, I understand that Ben's memorize... > btw, I feel a bit of an impostor having it called "my" memorize. It was Torsten's initiative based on gist by John Cromartie.

Re: [Pharo-dev] memoized vs once

Le 27 janv. 2017 05:55, "Ben Coman" a écrit : On Fri, Jan 27, 2017 at 4:32 AM, Eliot Miranda wrote: > > > Now, descending to the implementations, I understand that Ben's memorize... > btw, I feel a bit of an impostor having it called "my"

Re: [Pharo-dev] HandMorph>>#processEvents

Probably a bug. I started to clean this part 4 years ago and my changes got killed by SDL + OS Window and now apparently SDL 20 is not good enough. May be in 3 years from now it will be cleaned, who knows. Stef Why do we have this twice in processEvents? self mouseOverHandler

Re: [Pharo-dev] athens dead code?

On Fri, 27 Jan 2017 00:31:11 +0100, Igor Stasenko wrote: On 27 January 2017 at 00:06, stepharong wrote: accept: aVisitor ^ aVisitor lineSegment: self accept: aVisitor ^ aVisitor closeSegment: self accept: aVisitor ^ aVisitor

Re: [Pharo-dev] [bloc] addressing the moz2d issue

Thanks for this analysis I call it the reality principle Who will pay for it? How many engineers can community afford? Do you know how much other systems invest in graphical frameworks? It is not a science project, isn't it? There is always a tension between what we can achieve and the goal. Now

Re: [Pharo-dev] athens dead code?

On 27 January 2017 at 09:17, stepharong wrote: > On Fri, 27 Jan 2017 00:31:11 +0100, Igor Stasenko > wrote: > > > > On 27 January 2017 at 00:06, stepharong wrote: > >> >> accept: aVisitor >> ^ aVisitor lineSegment: self >>

Re: [Pharo-dev] Immutability support

2017-01-26 10:59 GMT+01:00 Clément Bera : > Let's rewrite the method this way: > > attemptToAssign: value withIndex: index > | process | > "INSERT CODE HERE" > process := Processor activeProcess. > [ process suspendedContext: process suspendedContext sender

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

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

[Pharo-dev] [pharo-project/pharo-core] 029fd5: 60357

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

Re: [Pharo-dev] Odd (and wrong) implementation of Float>>sign

2017-01-27 0:15 GMT+01:00 Martin McClure : > On 01/26/2017 12:47 PM, Nicolas Cellier wrote: > > > > > > 2017-01-26 21:22 GMT+01:00 Martin McClure > >: > > [...] > > > The current implementation of #sign is > > > >

Re: [Pharo-dev] Odd (and wrong) implementation of Float>>sign

On 01/26/2017 05:12 PM, Nicolas Cellier wrote: > -0.0 sign is answering -1 at least since 1998, so we might have get used > to it ;) > I've done the job on Squeak trunk, the answer is we need to revise some > senders Thanks for looking into it. I'm afraid I don't have time to dig into this

Re: [Pharo-dev] memoized vs once

On 27 January 2017 at 02:28, Ben Coman wrote: > On Fri, Jan 27, 2017 at 7:35 AM, Igor Stasenko wrote: > > > > > > On 27 January 2017 at 01:30, Ben Coman wrote: > >> > >> On Fri, Jan 27, 2017 at 6:02 AM, stepharong

Re: [Pharo-dev] memoized vs once

On 27 January 2017 at 03:45, Igor Stasenko wrote: > > > On 27 January 2017 at 02:28, Ben Coman wrote: > >> On Fri, Jan 27, 2017 at 7:35 AM, Igor Stasenko >> wrote: >> > >> > >> > On 27 January 2017 at 01:30, Ben Coman

Re: [Pharo-dev] memoized vs once

On Fri, Jan 27, 2017 at 7:35 AM, Igor Stasenko wrote: > > > On 27 January 2017 at 01:30, Ben Coman wrote: >> >> On Fri, Jan 27, 2017 at 6:02 AM, stepharong wrote: >> > On Thu, 26 Jan 2017 20:38:49 +0100, Torsten Bergmann

Re: [Pharo-dev] [bloc] addressing the moz2d issue

Hi, Vulkan support. Never with cairo. Pure OpenGL too (try to compile cairo-gl > on mac, good luck!) There is a way to compile it with quartz support. As of > version 2.7.9, *XQuartz does not provide support for high-resolution > Retina displays to X11 apps*, which run in pixel-doubled mode on >

Re: [Pharo-dev] [Ann] Calypso update: method browser and better UI

On Fri, Jan 27, 2017 at 5:33 AM, Denis Kudriashov wrote: > > 2017-01-26 21:09 GMT+01:00 Bernhard Pieber : >> >> > - no Spec text model anymore. Rubric widgets are used directly. It >> > improves speed of building text editors >> This is really great. I

[Pharo-dev] athens dead code?

accept: aVisitor ^ aVisitor lineSegment: self accept: aVisitor ^ aVisitor closeSegment: self accept: aVisitor ^ aVisitor moveSegment: self seems to invoke methods that do not exit I check AthensLIneSegment is used so I do not understand why the methods are broken.

Re: [Pharo-dev] [bloc] addressing the moz2d issue

Hi (My previous email was not a joke, I don't try to troll anyone. Let tolls do their job in other places) *Let's forget Moz2D for a moment :) Imagine that it does not exist. *It was done just for fun and is even not in pharo repo. ( https://github.com/syrel/Moz2D). We needed something that works

Re: [Pharo-dev] [bloc] addressing the moz2d issue

Hi *According to conclusion above, we will plan how to migrate to Cairo.* We will need help with Pango. Cheers, Alex On 26 January 2017 at 23:45, Aliaksei Syrel wrote: > Hi > > (My previous email was not a joke, I don't try to troll anyone. Let tolls > do their job in

Re: [Pharo-dev] memoized vs once

On 27 January 2017 at 00:28, Chris Cunningham wrote: > On Thu, Jan 26, 2017 at 2:02 PM, stepharong wrote: > >> On Thu, 26 Jan 2017 20:38:49 +0100, Torsten Bergmann >> wrote: >> >> ... >> >> >>> Instead it is sent to an object that

Re: [Pharo-dev] athens dead code?

On 27 January 2017 at 00:06, stepharong wrote: > > accept: aVisitor > ^ aVisitor lineSegment: self > accept: aVisitor > ^ aVisitor closeSegment: self > accept: aVisitor > ^ aVisitor moveSegment: self > > seems to invoke methods that do not exit > I

Re: [Pharo-dev] memoized vs once

On Fri, Jan 27, 2017 at 6:02 AM, stepharong wrote: > On Thu, 26 Jan 2017 20:38:49 +0100, Torsten Bergmann wrote: > >> stepharong wrote: >>> >>> can we rename this selector? >>> asMethodConst should be at least be renamed to asConstantMethod >> >> >> When you

Re: [Pharo-dev] memoized vs once

On 27 January 2017 at 01:30, Ben Coman wrote: > On Fri, Jan 27, 2017 at 6:02 AM, stepharong wrote: > > On Thu, 26 Jan 2017 20:38:49 +0100, Torsten Bergmann > wrote: > > > >> stepharong wrote: > >>> > >>> can we rename this selector? >

Re: [Pharo-dev] [bloc] addressing the moz2d issue

On 01/26/2017 02:45 PM, Aliaksei Syrel wrote: > There are some real questions: > > 1. Do we need Bloc or Morphic2 or %name your favourite framework%? > 2. How advanced and modern do you want it to be? > 3. What technology stack do we want to use for our new graphical framework? > 4. What

Re: [Pharo-dev] [bloc] addressing the moz2d issue

Moz2D looks pretty great and the stateless argument makes sense. Furthermore there is an isolation layer. Interesting reads: https://blog.mozilla.org/joe/2011/04/26/introducing-the-azure-project/ http://robert.ocallahan.org/2011/09/graphics-api-design.html

Re: [Pharo-dev] [bloc] addressing the moz2d issue

On Thu, 26 Jan 2017 22:36:47 +0100, Tudor Girba wrote: Hi Stef, There was a misunderstanding. Alex was just listing the need of underlying technologies for the features that Bloc already supports. Let’s restart this conversation. He will send an explanatory email.

Re: [Pharo-dev] Odd (and wrong) implementation of Float>>sign

Hi, i wonder what is the reasoning that "Float nan sign" returns anything else than Float nan? werner On 01/26/2017 09:47 PM, Nicolas Cellier wrote: 2017-01-26 21:22 GMT+01:00 Martin McClure >: Pharo's implementation of Float>>sign

Re: [Pharo-dev] memoized vs once

On Thu, 26 Jan 2017 20:38:49 +0100, Torsten Bergmann wrote: stepharong wrote: can we rename this selector? asMethodConst should be at least be renamed to asConstantMethod When you use "as {something}" then "something" depicts the result of the conversion message sent to an

[Pharo-dev] HandMorph>>#processEvents

Why do we have this twice in processEvents? self mouseOverHandler processMouseOver: lastMouseEvent ? Well, maybe that is not there that things happen but if you spy on mouseEnter and mouseLeave events, you will notice that they are both sent **twice** all the time. I think that this happens so

Re: [Pharo-dev] Odd (and wrong) implementation of Float>>sign

On 01/26/2017 12:47 PM, Nicolas Cellier wrote: > > > 2017-01-26 21:22 GMT+01:00 Martin McClure >: [...] > The current implementation of #sign is > > self > 0 ifTrue: [^ 1]. > (self < 0 or: [((self at: 1) bitShift: -31) = 1])

Re: [Pharo-dev] [bloc] addressing the moz2d issue

My last mail on that topic Esteban told me that we should recompile the cairo lib with acceleration enabled. Now probably Mozz2d is the coolest techno right now. We read about Azure when Igor started to build athens. Athens was designed to make sure that when Cairo dies we do not have to

Re: [Pharo-dev] memoized vs once

On Thu, Jan 26, 2017 at 2:02 PM, stepharong wrote: > On Thu, 26 Jan 2017 20:38:49 +0100, Torsten Bergmann > wrote: > > ... > > >> Instead it is sent to an object that afterwards is a constant within a >> method >> (so it will not be evaluated later at runtime