Hi Davide,
First I'll explain why you see a difference in behaviour, then I'll give you a
solution.
Network connections are expensive resources, most servers try to close them as
soon as possible when they are not used.
Zinc HTTP Components does not normally close connections by itself, althou
We will organize a Pharo sprint / Moose dojo Feb 28, starting at
10:00am. (Local Time Paris).
Goals of this sprint:
- Pharo 8: Fix issues from tracker
https://github.com/pharo-project/pharo/issues
Remote Sprint: Remotely, you can join us on Discord. During the sprint, we
sync
Your critique is perfectly valid; I have no problem with it. Ben nicely
expanded on my point. Like I said, if I wanted to serve your purpose, then
yes, I'd make your video. Your critique would be very helpful.
This video didn't need a soundtrack either, but adding it made the video
immeasurably be
--- Begin Message ---
Hi Sven,
Thanks for your reply.
I supposed that the ping/pong feature would have helped (I'm not an expert,
but I found something about it on the net).
Tomorrow I'm gonna try your updated runWith: and I'll feedback you.
Thanks
Davide
Sven Van Caekenberghe-2 wrote
> Hi David
I am testing the new image of Pharo 8 (Pharo Contribution Jenkins) with
pre-installed seaside. When trying to load the Torsten Bootstrap:
Gofer new
url: 'http://smalltalkhub.com/mc/TorstenBergmann/Bootstrap/main';
package: 'ConfigurationOfBootstrap';
load
(Smalltalk at: #Configurat
Ben,
I checked, [Form] is inherited from class [DisplayMedium]. So in
smalltalk, the inheritence pattern is:
Object -> DisplayObject -> DisplayMedium -> Form
The inheritence pattern of ImageMorph is:
Object -> Morph -> ImageMorph
One does not inherit the other and is not a wrapper, at least in P
This is interesting. How many people usually go to these code sprint
things?
I am learning pharo and roassal and I perused Moose and it looks very
interesting!
On Mon, Feb 24, 2020 at 4:52 AM Marcus Denker
wrote:
> We will organize a Pharo sprint / Moose dojo Feb 28, starting at
>
> 10:
Normally, there should not be an inheritance relationship between
wrapper and wrappee, but I agree that describing Morphs as wrappers
around Forms seems to miss the point. The notion of wrapper usually
implies that there is little modification to the protocol of the
wrappee, a wrapper should no
