thanks for the alarm and tx esteban for the fix.
Le 13/9/16 à 08:58, Hersh Krishna via Pharo-users a écrit :
Hi,
I think it is not really realistic to expect this to work *after* loading code
of others.
Why not
-> do image clean
-> *then* load the packages you need?
Marcus
> On 13 Sep 2016, at 03:19, Vitor Medina Cruz wrote:
>
> Ok, I did some extra tests and I think I fig
Hi Holger, I think that both patterns are currently supported (in beta
version), but maybe we do not use exactly the same tools.
First, Iceberg does not use the concept of "stash". The git stash changes
the file in your git working copy (on your file system), while your
(modified) code is not ther
Hi
If you happen to know a double dispatch situation in Pharo, I'm
interested since I'm revisiting my lecture.
Stef
Humm, why not? When I load the configuration it loads several other
packages, wouldn't that need a cleanup too? When I first see that I could
cleanup an image my first thought was to put it in a production state with
my code, then I would cleanup to leave it as lean as possible. Isn't that
correct?
> On 13 Sep 2016, at 13:15, Vitor Medina Cruz wrote:
>
> Humm, why not? When I load the configuration it loads several other packages,
> wouldn't that need a cleanup too? When I first see that I could cleanup an
> image my first thought was to put it in a production state with my code, then
>
Hi Stef!
Plenty of examples:
- Converting money
- Paper, Stone, Scissor
- A canvas containing triangle, circle, box has to be printed, on an html
canvas or PDF. (Very close to the Visitor design pattern, but simpler)
Here are the lectures I use:
https://dl.dropboxusercontent.com/u/31543901/TMP/
> -Message d'origine-
> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de
> Serge Stinckwich
> Envoyé : vendredi 2 septembre 2016 16:44
> À : Pharo Development List
> Cc : scismallt...@googlegroups.com; Any question about pharo is welcome
> Objet : Re: [Pharo-dev] [
I understand. I thought it did more stuff, like remove necessary
development tools or executing processes, I don't know, but considering its
implementation it should affect only the image size, right?
Thanks,
Vitor
On Tue, Sep 13, 2016 at 8:30 AM, Marcus Denker
wrote:
>
> > On 13 Sep 2016, at 1
> On 13 Sep 2016, at 18:54, Vitor Medina Cruz wrote:
>
> I understand. I thought it did more stuff, like remove necessary development
> tools or executing processes,
It does call #cleanUpForRelease, but this we call at *every* update on the CI,
too. This calls the #cleanUp method of all clas
2016-09-13 20:56 GMT+02:00 stepharo :
>
> I was thinking about the code in Pharo.
>
> Plenty of examples:
>
>> - Converting money
>>
>
> can you tell me more about this one?
Probably most known and beautiful case is arithmetic operations. Look at
#adaptToInteger:andSend: and friends.
On Wed, Sep 14, 2016 at 12:25 AM, Blondeau Vincent
wrote:
>
>
>
>> -Message d'origine-
>> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de
>> Serge Stinckwich
>> Envoyé : vendredi 2 septembre 2016 16:44
>> À : Pharo Development List
>> Cc : scismallt...@googlegroups.
Hi,
After renaming, promoting as tag, moving to package and other
non-secuential operations in Nautilus which screwed up the packaging,
now all classes are shown in _UnpackagedPackage but when browsed via
Spotter they show the right package in the class template.
SequenceableCollection subclass:
Very first thought...
1. Close all Nautilus windows.
2. Smalltalk recompileAll.
??
cheers -ben
On Wed, Sep 14, 2016 at 11:58 AM, Esteban A. Maringolo
wrote:
> Hi,
>
> After renaming, promoting as tag, moving to package and other
> non-secuential operations in Nautilus which screwed up the packag
Thought-0.0.2...
What does Monticello > Browse show?
Thought-0.0.3...
Have a look at RPackageOrganizer class >> initialize
cheers -ben
On Wed, Sep 14, 2016 at 1:05 PM, Ben Coman wrote:
> Very first thought...
> 1. Close all Nautilus windows.
> 2. Smalltalk recompileAll.
>
> ??
> cheers -ben
>
>
15 matches
Mail list logo