, giorgio ferraris giorgio.ferra...@gmail.com
wrote:
Hi,
started looking at Pharo after many years.
First of all, you all did an awesome works, thank you!
There is a small problems on System Browser
open image
open system browser
choose one class
select group
The class side
Hi, Guys,
I'm not (yet) working on Pharo (still VW and some VisualSmalltalk in the
few time left free from my main job), but I follow what you do (not just
you but all the community) and I have to admit you (all) work really hard.
Bergel is doing a fantastic job, and your Moose is very nice, etc.
Hi, Guys,
you did and absolutely wonderful work!
giorgio ferraris
On Thu, Apr 16, 2015 at 4:14 PM, Johan Fabry jfa...@dcc.uchile.cl wrote:
On Apr 16, 2015, at 08:38, Sven Van Caekenberghe s...@stfx.eu wrote:
On 16 Apr 2015, at 11:55, Tudor Girba tu...@tudorgirba.com wrote:
Great
hello,
Test seems old, both virtual machines (VW and Pharo) have upgraded in the
meantime.
VW has always been faster that Pharo for what I know, up to recent time.
Recently Pharo changed the vm technology so now it should be much faster,
but I don'r know is faster that VW , so it would be nice to
Hello,
Regarding native widget, on the VW side the usage on them brought
slowness on the OSX platform. Windows platform is speedy, but OSX platform
is slower using native widget than with emulated ones.
So native widget alone are not always a solution.
ciao
giorgio
On Mon, Oct 7, 2019 at 2:08
for what I know it's the way it's integrated with the underlain OS. On
windows things are much, much better.
*VW emulates GUIs well, but I would not expect it to beat native*. I
would restate it as : I would not expect native to be slower that
emulated :) seems the same, but not
seems pretty complete :)
giorgio
On Wed, Jan 29, 2020 at 2:18 PM Richard Kenneth Eng <
horrido.hobb...@gmail.com> wrote:
> Any feedback?
>
> [image: image.png]
>
after long time, I downloaded and opened a Pharo image.
Seems you did a great job on these years!!
giorgio
On Tue, Jan 21, 2020 at 10:00 AM Norbert Hartl wrote:
> Great work and many thanks to all that supported!!
>
> Norbert
>
>
> Am 20.01.2020 um 19:01 schrieb ducasse :
>
> I would like to
Hello,
first of all, have a wonderful 2020..
sorry for jumping in, I'm not a contributor to Pharo, and actually never a
user of it ( when I work in Smalltalk, I use VW mostly, and still need to
find the time to try Pharo seriously), but I do work in Smalltalk (and
Pharo is a dialect of) from
Ciao, Dario,
take care of you. Bergamo is on a very bad situations.
giorgio
On Sat, Mar 14, 2020 at 2:53 PM dario.trussardi65 <
dario.trussard...@gmail.com> wrote:
> Ciao,
> be very careful ... it's very dangerous ...
> here in Bergamo it's a disaster.
> We are losing our grandparents like
Hi, Russ,
I feel better after reading your mail :)
That's the way I modeled and still model things in my (long...) developer
life, so I felt a bit strange after reading that discussion
ciao
giorgio
On Fri, Apr 16, 2021 at 3:45 PM Russ Whaley wrote:
> Wow, I must be missing a whole lot
Hi, Vince,
I don't know exactly Pharo, but when you fork a process, it becomes
an independent thread of work. So in that process you can send your
async call and wait for a response and then do the work. All inside the
forked process.
It's the smallalk's scheduler that will take care of passing
it's interesting to see how the answer changes with only a small change on
the question:
(1 to: 100 by: 4) reject: [:i | i isOdd]
gives:
The code creates a collection of numbers from 1 to 100, incrementing by 4
at each step using the to:by: message. It then applies the reject: message
to this
13 matches
Mail list logo
