Re: [Pharo-dev] [Pharo-users] World lastKeystroke and openInWorld: aPasteUpMorph

2015-06-11 10:58 GMT+02:00 Markus Schlager : > issues opened > I added a fix for the broken lastkeystroke,but this will only work for the ActiveWorld/PasteUpMorph, not for any other PasteUpMorph. With the split of PasteUpMorph in PasteUpMorph and WorldMorph, and the change of keystroke handling

Re: [Pharo-dev] About TextStyle and StrikeFonts

Le 15/6/15 10:48, Nicolai Hess a écrit : 2015-05-17 19:01 GMT+02:00 Nicolai Hess >: I am about to fix some issues related to TextMorphs and fonts: 15402 wrong choose list from TextMorph editor halo 15

Re: [Pharo-dev] About TextStyle and StrikeFonts

Hi nicolai this part is a epic mess. Just for the record we (ben and me) extracted from a global dictionary TextConstants :) TextSharedInformation It was strange to have a changing part in a TextConstants. So TextSharedInformation is really something that we can clean/kill/replace. Now I think

Re: [Pharo-dev] Probably Metacello sucks…

Esteban, Yeah, it can take time for the culture to change, but the tools do have to be in place and the early adopters have to beat those tools into shape ... we are in this phase at the moment I think... once the tools are in place, then the projects that are feeling the most pain will have

[Pharo-dev] please test: Make Spec use RubPluggableTextMorph instead of PluggableTextMorph

https://pharo.fogbugz.com/default.asp?15774 Like that we can get rid of the bug https://pharo.fogbugz.com/default.asp?15773 where SHRB is doing wrong semantic analysis and this is one less ref to PluggableTextMorph. We are trying to get rid of it by either using RubPluggableTextMorph or and

[Pharo-dev] Pharo 4.0 crash

Hi, I just got a crash dump. Regards Sabine --- - Mon Jun 15 15:32:56 2015 Exception code: C005 Exception addr: 004239D0 Access violation (read access) at 0016 EAX:0016EBX:005CECX:000E

Re: [Pharo-dev] Inexact draiwing in roassal?

Ok, so everything is okay I understand Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jun 15, 2015, at 10:58 AM, Javier Pimás wrote: > > Thanks for the quick answer, it now w

Re: [Pharo-dev] Forgotten halt ?

> On 15 Jun 2015, at 12:39, Marcus Denker wrote: > > >> On 15 Jun 2015, at 12:36, Max Leske > > wrote: >> >> >>> On 15 Jun 2015, at 11:45, Franck Warlouzet >> > wrote: >>> >>> Hi, >>> >>> I wanted to merge a package filed out, a

[Pharo-dev] SHRBTextStyler is desynched

Hi SHRBTextStyler is using the wrong class when doing semantics analysis. So this is why the coloring does not work. A clear example is looking and the implementor of setText: and selecting one of the three methods. opening the transcript shows an error message that shows that the class used to

[Pharo-dev] [pharo-project/pharo-core] d4e81a: 50114

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: d4e81a2c267b75815db347f8024946c3747dba0f https://github.com/pharo-project/pharo-core/commit/d4e81a2c267b75815db347f8024946c3747dba0f Author: Jenkins Build Server Date: 2015-06-15 (Mon, 15 Jun 2015

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

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

Re: [Pharo-dev] Forgotten halt ?

Yes sorry I forgot ... Pharo 5 latest image From: marcus.den...@inria.fr Date: Mon, 15 Jun 2015 12:39:43 +0200 To: pharo-dev@lists.pharo.org Subject: Re: [Pharo-dev] Forgotten halt ? On 15 Jun 2015, at 12:36, Max Leske wrote: On 15 Jun 2015, at 11:45, Franck Warlouzet wrote:Hi, I wanted to m

Re: [Pharo-dev] Forgotten halt ?

> On 15 Jun 2015, at 12:36, Max Leske wrote: > > >> On 15 Jun 2015, at 11:45, Franck Warlouzet > > wrote: >> >> Hi, >> >> I wanted to merge a package filed out, and I got a self halt in >> FileList>>#readOnlyStream. Is it an expected behavior (like instead

Re: [Pharo-dev] Forgotten halt ?

> On 15 Jun 2015, at 11:45, Franck Warlouzet > wrote: > > Hi, > > I wanted to merge a package filed out, and I got a self halt in > FileList>>#readOnlyStream. Is it an expected behavior (like instead of raise > an exception, put a self halt, I do not know what) or is it just a forgotten > s

[Pharo-dev] Forgotten halt ?

Hi, I wanted to merge a package filed out, and I got a self halt in FileList>>#readOnlyStream. Is it an expected behavior (like instead of raise an exception, put a self halt, I do not know what) or is it just a forgotten self halt ? Cheers, Franck

Re: [Pharo-dev] Debugging and optimizations

2015-06-15 10:07 GMT+02:00 Ben Coman : > whoops. please excuse my previous clicktoofast. > > On Mon, Jun 15, 2015 at 3:51 PM, Clément Bera > wrote: > > Hey all, > > > > Holger Freyther, I didn't know about ##() and once in GNU Smalltalk, but > > that was definitely what I was trying to experiment

Re: [Pharo-dev] About TextStyle and StrikeFonts

2015-05-17 19:01 GMT+02:00 Nicolai Hess : > I am about to fix some issues related to TextMorphs and fonts: > > 15402 > wrong choose list from TextMorph editor halo > > 15552 > chooseStyle halo from TextMorp

Re: [Pharo-dev] Debugging and optimizations

Well, we already have in-image a #once like solution based on memoization. block := [ :key | key factorial ] memoized. "first time" [1000 to: 1500 do: [:index |block value: index]] timeToRun. "0:00:00:01.598" "second time, cached" [1000 to: 1500 do: [:index |block value: index]] timeToRun. "0:

Re: [Pharo-dev] Debugging and optimizations

whoops. please excuse my previous clicktoofast. On Mon, Jun 15, 2015 at 3:51 PM, Clément Bera wrote: > Hey all, > > Holger Freyther, I didn't know about ##() and once in GNU Smalltalk, but > that was definitely what I was trying to experiment with. > > As Thierry mentioned, these elements come fr

Re: [Pharo-dev] Debugging and optimizations

On Mon, Jun 15, 2015 at 3:51 PM, Clément Bera wrote: > Hey all, > > Holger Freyther, I didn't know about ##() and once in GNU Smalltalk, but > that was definitely what I was trying to experiment with. > > As Thierry mentioned, these elements come from C/C++ where you have macros > that are very us

Re: [Pharo-dev] Debugging and optimizations

Hey all, Holger Freyther, I didn't know about ##() and once in GNU Smalltalk, but that was definitely what I was trying to experiment with. As Thierry mentioned, these elements come from C/C++ where you have macros that are very useful when writing high performance code so your code can be both f

Re: [Pharo-dev] Roassal Camp Smalltalk

Hi Peter Definitively. Having stable API is key for us and for everybody. For us (synectique), we stop to change versions around 6 months ago. This is sad that we have to shield us from Roassal but this is what we are doing. We cannot fight to get clients and change all the time our code. As yo