I did not know it :) so this is cool.
Today we improved the makefile logic and I'm about to finish a hack to
give the possibility to the makefile to be fully generic.
After I will finally look at Luc makefile generator because we want to
move more logic to Pharo.
Stef
On Tue, Aug 29, 2017 at 2:20
Thanks for your quick reply.
OK, your chapter highligths the polymorpism not the inheritance.
So I will try to change the Number methods in a dedicated image...
Anyway, in the book InsideSmalltalk P. 250, it explains that (I quote)
I suppose the "Number" mecanism is more complex than I can expe
Yes I know this article.
For the book I was trying to get an example that I can just add as an
extension of a previous exercise.
And I like it.
On Tue, Aug 29, 2017 at 9:33 PM, Yves Lenfant wrote:
> I start understanding better, I found this topic in the SmalltalkWithStyle
> book p. 107
> This t
The code of Pharo for + **may** be rewritten using double dispatch but
it is not that clear to me
especially the adaptToInteger logic and we do not change for the sake of it :)
There are plenty of places we should improve and that are really important.
In Pillar, or compiler we have many more node
I start understanding better, I found this topic in the SmalltalkWithStyle
book p. 107
This technic was explained by Dan Ingalls in
[Ingalls 86] Ingalls, D. A Simple Technique for Handling Multiple
Polymorphism.
347-349, Proceedings of OOPSLA '86, Portland, Or., ACM SIGPLAN 21(11).
1986
That you c
except the slides 2 and 3 of the first week :)
But else all the mooc: slides, exercises were made in Pillar
On Tue, Aug 29, 2017 at 3:39 PM, Peter Uhnák wrote:
> All Pharo Mooc slides were made in pillar
>
> e.g.
>
> pillar:
> https://github.com/SquareBracketAssociates/PharoMooc/blob/master/Slide
Le 29/08/2017 à 14:54, H. Hirzel a écrit :
> Hello
>
> On the slide 14 of the Pillar presentation at ESUG 2015 [1] it says
> that the presentation was made with Pillar. Is the Pillar source code
> available somewhere?
>
Hi!
Here are the sources:
https://drive.google.com/drive/folders/0B_KDRvt7h
Point well taken. Unfortunately, I'm not in charge of the infrastructure. I
don't know if my experience is typical or not, but it's difficult for IT to
find a period to disrupt engineering projects, potentially breaking tools,
without drawing fire from engineering :)
On Tue, Aug 29, 2017 at 8:45
Ooops I wasn't int the mailing list, lets try again
Hello Steph,
I have questions about the concept because,probably, I miss something.
I am not sneaky, let me explain.
If we analyse the Kernel Numbers package, and we dissect the relation
between Float, Fraction and Integer (Pharo 5.0) for e
>
> my work environment is using RedHat6/CentOS6 with glibc 2.12
>
That's seven years of unpatched security vulnerabilities! Are you sure you
really want to stay at such great risk?
On Tue, Aug 29, 2017 at 8:30 AM, Andreas Sunardi
wrote:
> That sounds good. Unfortunately for me, my work enviro
That sounds good. Unfortunately for me, my work environment is using
RedHat6/CentOS6 with glibc 2.12. Is there Pharo6 with glibc < 2.15 support.
Or is there a way for me to build that myself?
It's quite a departure to change my DSL into defining multiple methods. But
that's my own problem.
I'm ha
All Pharo Mooc slides were made in pillar
e.g.
pillar:
https://github.com/SquareBracketAssociates/PharoMooc/blob/master/Slides/Week3/C019-W3S03-Basic-Variables.pillar
output:
http://rmod-pharo-mooc.lille.inria.fr/MOOC/Slides/Week3/C019-W3S03-Basic-Variables.html#slide-2
( mooc.pharo.org )
Pete
Hello
On the slide 14 of the Pillar presentation at ESUG 2015 [1] it says
that the presentation was made with Pillar. Is the Pillar source code
available somewhere?
Other source code examples of presentations made with Pillar are fine as well.
Thank you
Hannes Hirzel
[1] http://esug.org/data/
On 8/28/17, Norbert Hartl wrote:
>
>> Am 26.08.2017 um 12:56 schrieb Tudor Girba :
>>
>> In an image having Pillar, inspect a Pillar file. Something like this:
>>
>> ‘path/to/file.pillar' asFileReference
>>
> I downloaded a 6.1 image, loaded pillar from catalog and inspected
>
> 'foo.pillar' asFil
On 28 August 2017 at 06:34, peter yoo wrote:
> 1. failed to compile the SPEC UI Framework. Xetex would have caught the
> error, but I do not know about luatex.
> 2. I am using texlive 2017 with gentoo linux.
Can you send me a copy of the error you are getting ?
The English version should build
> On Aug 29, 2017, at 12:52 PM, Denis Kudriashov wrote:
>
> The code works fine in Pharo 7.0. I just tried the following:
> 1. wget -O- get.pharo.org/alpha+vm | bash
>
> Ah, sorry. I always forgot update.
No problem. I am happy that it works :).
Doru
>
> 2.
> Iceberg enableMetacelloIntegra
>
> The code works fine in Pharo 7.0. I just tried the following:
> 1. wget -O- get.pharo.org/alpha+vm | bash
>
Ah, sorry. I always forgot update.
> 2.
> Iceberg enableMetacelloIntegration: true.
> Metacello new
>baseline: 'GToolkit';
>repository: 'github://feenkcom/gtoolkit/src';
>l
Hi Denis,
Thanks for the feedback!
As I mentioned, this is a pre-alpha :). Our main focus was on exploring that
the design works in breadth. There are indeed, detailed issues that do not work
yet, and there are edge cases for navigation and insertion/deletion that are
still open issues.
In Bl
"I once had a guy who wasn't telling younger team members that he wasn't
able to read their document due to too small fonts. We are talking C level
executives here..."
You mean he was embarrassed to admit he could not read small fonts ? How
small we talking here bellow 12 point size ?
On Tue, Aug
White all over Smalltalks UIs are a reason why I do *not* use them.
Dark Pharo: good.
Properly themeable Pharo with a palette and logical color mappings:
nirvana. I hope to contribute to that. I did some GToolkit dark theming
but it was too late for 6.0 so maybe for 7.
Try to code against a whi
80s was the time of home computer with 1985 the rise of Amiga which was
light years ahead of theme support, it practically established GUIs, GPU,
dedicated hardware components, gaming, computer graphics and of course 3d
graphics, together with many other things. Plus a theme was super easy to
make
Hi,
If your tool works in Pharo 6, you can use the other bytecode set which
supports up to 32k literals. To do so, go to:
World Menu > Settings > Compiler > Encoder
and pick SistaV1 instead of V3PlusClosures
Try to load your code. The default Pharo 6 VM supports both bytecode sets.
Alternatively
Hello,
The new byte code set that we will use in the future does not hat this
limitation.
You can, but only in Pharo6 and later, the new byte code backend (it is called
“SistaV1”).
(this is a global preference to be enabled in the Settings).
Marcus
It is not yet used by default, but yo
23 matches
Mail list logo
