[Pharo-users] Having to press step into twice, to actually step into with debugger?

Has anyone else noticed that you often have to click 2 times, to step into some things in the debugger? I had some code like this: MyClass verify And had a break point on #verify, which the debugger stops on, but then I have to click into, twice to go through the code? Is there something

Re: [Pharo-users] How to get to the bottom of the spinning beach ball when first entering Pharo

Hi Peter - yes the beach ball is the mac equivalent of the spinning circle , but it seems to appear more often than I expect - just web browsing or reading email and then flipping back incurs that sane delay? This is on a 16gb MacBook Pro. I don’t recall this in Pharo 6 the same, but I’m doing

Re: [Pharo-users] How to get to the bottom of the spinning beach ball when first entering Pharo

Tim I have never seen a spinning beach ball, but I often find, when coming back to Pharo after using some other application, that there is a delay of a few seconds, during which time I see the standard Windows 'hang on a bit' signal, which is a blue ring near the cursor. My assumption is that

Re: [Pharo-users] Pharo and FPGA

For information, you can find a list of old research about smalltalk embedded in hardware: http://www.merlintec.com/swiki/hardware/26.html BR Yves -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] [ANN] CouchDB Client for Pharo

Well... I wasn't aware such client existed. #facepalm Looking at it, it seems to fulfill the pending features I was talking about, including the option to use Pharo as a View server! (running map/reduce operations) and the Mango Queries (it's not a typo of Mongo, it's a different thing [1]). It

Re: [Pharo-users] Hmmm sending at:put: to an undefined object (nil) gives a confusing error message

Byte arrays are not host specific. True. But integers are not byte arrays. They don't even contain byte arrays. Just like (boxed) Floats are not word arrays and don't contain word arrays. For what it's worth, I find that it's quite unusual for a method to change from private to public or vice

[Pharo-users] How to get to the bottom of the spinning beach ball when first entering Pharo

Hi guys - this has come up before in the past - but I’m really noticing it now having worked on a project for a few weeks. Every time I go into my image (by go into - I mean unsuspend my laptop and start using as its the current app, OR flipping to it from say reading email) I get a shining

[Pharo-users] MSWindows Keymapping

Hi All, I'm primarily a Windows user and I am finding the default key mapping very un-windows and it's preventing me from becoming immersed in the environment. Because I'm constantly having to reach for the mouse to switch windows etc. How easy would it be to change the key mapping to

Re: [Pharo-users] Hmmm sending at:put: to an undefined object (nil) gives a confusing error message

On 13/03/19 12:45 PM, Richard O'Keefe wrote: Base 256: that's an implementation detail. Little-endian: that's an implementation detail. Architecture-specific no. Implementation yes. But that should be fine for private methods. My Smalltalk uses base 65536 native-endian and takes some care

Re: [Pharo-users] Hmmm sending at:put: to an undefined object (nil) gives a confusing error message

It's supposed to be on GitHub but I botched it. On Wed, 13 Mar 2019 at 21:08, Sven Van Caekenberghe wrote: > > > > On 13 Mar 2019, at 08:15, Richard O'Keefe wrote: > > > > My Smalltalk > > Where can I have a look at that ? > >

Re: [Pharo-users] [ANN] CouchDB Client for Pharo

Cool! I added an entry [1] for it to awesome-pharos [2]. Cheers, Julien Links: [1]: https://github.com/pharo-open-documentation/awesome-pharo/pull/56 [2]: https://github.com/pharo-open-documentation/awesome-pharo --- Julien Delplanque Doctorant à l’Université de Lille

Re: [Pharo-users] Hmmm sending at:put: to an undefined object (nil) gives a confusing error message

> On 13 Mar 2019, at 08:15, Richard O'Keefe wrote: > > My Smalltalk Where can I have a look at that ?

Re: [Pharo-users] [ANN] CouchDB Client for Pharo

Nice. How does it relate/compare to https://github.com/jmari/SCouchDB ? Gesendet: Mittwoch, 13. März 2019 um 03:18 Uhr Von: "Esteban Maringolo" An: "Pharo users" Betreff: [Pharo-users] [ANN] CouchDB Client for Pharo Hello all,   I finished polishing the repository a CouchDB client for

Re: [Pharo-users] Hmmm sending at:put: to an undefined object (nil) gives a confusing error message

Base 256: that's an implementation detail. Little-endian: that's an implementation detail. My Smalltalk uses base 65536 native-endian and takes some care not to let Smalltalk code find out. (Not least because on 64-bit machines I want to use base 2**32.) For *private* methods, depending on

Re: [Pharo-users] Hmmm sending at:put: to an undefined object (nil) gives a confusing error message

Let's start with portability. I have ST/X, VAST, VW, Squeak, Pharo, GST, Dolphin, and some minor systems. GST and ST/X do not define #at: on any kind of integer at all. Why would they? #basicAt: will do the job, will it not? Dolphin defines #at:[put:] on Integer as self shouldNotImplement and so

Re: [Pharo-users] UI Frameworks

Bob Cowdery writes: > I also found Block and Brick which say they are next generation, Block > being for graphics and  Brick for widgets. These are not yet in Pharo > and again I couldn't find any info although there is a tutorial for > Block but not for Brick. Having forgotten most