[ANN] PharoDev-1.3-13173

Thanks, Mariano!

We will move the latest Moose development build to this Pharo version next week.

Cheers,
Doru

On 27 Apr 2011, at 10:21, Mariano Martinez Peck wrote:

> Hi. IMPORTANT: This is not the final 1.3 release, it just one simple snapshot and one point. We all want a rock-solid Pharo 1.3 release, but that doesn't happens automagically. We all need to start using and testing the image before they are release. It is for the better of all of us. The more we test the more stable will be the release. So...we need your help. What you can do?
>
> 1) test test test test test. Use it. Take this image and use it for your regular work.
> 2) report bugs: http://www.pharo-project.org/community/issue-tracking
> 3) propose fixes: http://code.google.com/p/pharo/wiki/HowToContribute
> 4) Fix errors/failures tests
> 5) Load your OWN packages and projects now. Don't wait until Pharo1.3 is released and then ask "uuhh what happened to XXX? you removed? ohhh but I use it".
> 6) Do you maintain Metacello configurations?  ok, if you test your project and works correctly in Pharo 1.3, please update (or create if you don't yet have it) the #stable,
> 7) Do you maintain packages included in Pharo?  please check we are using the correct versions
> 8) I would like to see people testing AidaWeb, Magma, Fuel, Moose, DBXTalk, Seaside and all its friends, Zinc, FileSystem, etc, etc, etc.
>
> Pharo-1.3-13173  should work with Interpreter VM and with Cog. For Cog I recommend to download the last one from Eliot's page: http://www.mirandabanda.org/files/Cog/VM/
>
> Two little warnings:
> - The Transcript is read only....and it will probably be roll backed to the previous one
> - if text editing looks weird....it is Lukas's fault ;)  http://www.youtube.com/watch?v=fTMX1f8Lu5w
>
> Ok, the image is here:   https://gforge.inria.fr/frs/download.php/28517/Pharo-1.3-13173.zip
>
> And it was build by Hudson: https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.3/111/
>
> Best regards,
>
> --
> Mariano
> http://marianopeck.wordpress.com
>

--
www.tudorgirba.com

"Sometimes the best solution is not the best solution."

Good morning Mariano

This is something I wrote to Adrian Lienhard,
when an image did not run, straight out of the box
so to speak, because of VM differences
Some thoughts about reliability, and, very important
IMHO, upward compatibility.

Thanks & Regards
Ted

>>>
?
I did expect that, nota bene working with
the Seaside supplied one-click image and
the virtual machine supplied with it,
provided on the Seaside.st site itself,
that everything is (and remains)
100% upward compatible,
no matter what VM is or will be used in the future.

So, that application builders are assured that
the things they create will run unchanged
for even years to come. In an industrial
environment, this is vital.

For example: on IBM mainframes. many
Cobol or PL/1 programs/modules made more than
30 years ago run unchanged and without recompilation/linking.
This is actually an industrial requirement, without it e.g.
the complete IT environment of banks etc. would collapse.
Even your bank account very probably relies on modules
programmed way back in the seventies..
( i won't mention the chaos with years of legacy code here,
but this could also occur years later with Smalltalk apps)

but back to image compatibility
As a workaround, wouldn't it be a good idea:
 - if some shell script on the Seaside hosting site somehow scans/checks
 the image and start it with an appropriate VM either COG or another?
or:
 provide a standard unchanged clean Seaside image in the file directory
 as default, so the only thing  one has to do is to load Monticello
package(s) into it?

This is written from the somewhat traditional, industrial
and pragmatic perspective of a typical application developer,
who is not really involved in the more underlying system "details" :o)

It would be almost a night mare in a large production environment
if e.g. classes are removed where applications rely on.
It would mean and unnecessary rewriting of a lot of code.

Please observe: No pun or harsh negative criticism intended here,
I do really appreciate what is currently
going on with Smalltalk!

I''ll copy this to Pharo-users,
currently seen that Mariano is touching a bit similar things.

On Wed, Apr 27, 2011 at 10:36 AM, Tudor Girba <[hidden email]> wrote:
> Thanks, Mariano!
>
> We will move the latest Moose development build to this Pharo version next week.
>
> Cheers,
> Doru
>
>
> On 27 Apr 2011, at 10:21, Mariano Martinez Peck wrote:
>
>> Hi. IMPORTANT: This is not the final 1.3 release, it just one simple snapshot and one point. We all want a rock-solid Pharo 1.3 release, but that doesn't happens automagically. We all need to start using and testing the image before they are release. It is for the better of all of us. The more we test the more stable will be the release. So...we need your help. What you can do?
>>
>> 1) test test test test test. Use it. Take this image and use it for your regular work.
>> 2) report bugs: http://www.pharo-project.org/community/issue-tracking
>> 3) propose fixes: http://code.google.com/p/pharo/wiki/HowToContribute
>> 4) Fix errors/failures tests
>> 5) Load your OWN packages and projects now. Don't wait until Pharo1.3 is released and then ask "uuhh what happened to XXX? you removed? ohhh but I use it".
>> 6) Do you maintain Metacello configurations?  ok, if you test your project and works correctly in Pharo 1.3, please update (or create if you don't yet have it) the #stable,
>> 7) Do you maintain packages included in Pharo?  please check we are using the correct versions
>> 8) I would like to see people testing AidaWeb, Magma, Fuel, Moose, DBXTalk, Seaside and all its friends, Zinc, FileSystem, etc, etc, etc.
>>
>> Pharo-1.3-13173  should work with Interpreter VM and with Cog. For Cog I recommend to download the last one from Eliot's page: http://www.mirandabanda.org/files/Cog/VM/
>>
>> Two little warnings:
>> - The Transcript is read only....and it will probably be roll backed to the previous one
>> - if text editing looks weird....it is Lukas's fault ;)  http://www.youtube.com/watch?v=fTMX1f8Lu5w
>>
>> Ok, the image is here:   https://gforge.inria.fr/frs/download.php/28517/Pharo-1.3-13173.zip
>>
>> And it was build by Hudson: https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.3/111/
>>
>> Best regards,
>>
>> --
>> Mariano
>> http://marianopeck.wordpress.com
>>
>
> --
> www.tudorgirba.com
>
> "Sometimes the best solution is not the best solution."
>
>
>

Thanks for the initiative Mariano!

Some things I have seen in the few minutes I have used it:

- The zip includes the __MACOSX folder on the same level that the
uncompressed Pharo-1.3-13173

- The browser is way to small I think. Most names aren't shown complete.
The user has to resize it almost every time to be useful.

- The System -> Update is activated. Is this correct for Pharo (not
PharoCore) images?

Currently testing the ConfigurationOfMagma in it. If something shows up
I will report it also.

Cheers

El mié, 27-04-2011 a las 10:21 +0200, Mariano Martinez Peck escribió:

> Hi. IMPORTANT: This is not the final 1.3 release, it just one simple
> snapshot and one point. We all want a rock-solid Pharo 1.3 release,
> but that doesn't happens automagically. We all need to start using and
> testing the image before they are release. It is for the better of all
> of us. The more we test the more stable will be the release. So...we
> need your help. What you can do?
>
> 1) test test test test test. Use it. Take this image and use it for
> your regular work.
> 2) report bugs: http://www.pharo-project.org/community/issue-tracking
> 3) propose fixes: http://code.google.com/p/pharo/wiki/HowToContribute
> 4) Fix errors/failures tests
> 5) Load your OWN packages and projects now. Don't wait until Pharo1.3
> is released and then ask "uuhh what happened to XXX? you removed? ohhh
> but I use it".
> 6) Do you maintain Metacello configurations?  ok, if you test your
> project and works correctly in Pharo 1.3, please update (or create if
> you don't yet have it) the #stable,
> 7) Do you maintain packages included in Pharo?  please check we are
> using the correct versions
> 8) I would like to see people testing AidaWeb, Magma, Fuel, Moose,
> DBXTalk, Seaside and all its friends, Zinc, FileSystem, etc, etc, etc.
>
> Pharo-1.3-13173  should work with Interpreter VM and with Cog. For Cog
> I recommend to download the last one from Eliot's page:
> http://www.mirandabanda.org/files/Cog/VM/
>
> Two little warnings:
> - The Transcript is read only....and it will probably be roll backed
> to the previous one
> - if text editing looks weird....it is Lukas's fault ;)
> http://www.youtube.com/watch?v=fTMX1f8Lu5w
>
> Ok, the image is here:
> https://gforge.inria.fr/frs/download.php/28517/Pharo-1.3-13173.zip
>
> And it was build by Hudson:
> https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.3/111/
>
> Best regards,
>
> --
> Mariano
> http://marianopeck.wordpress.com
>

--
Miguel Cobá
http://twitter.com/MiguelCobaMtz
http://miguel.leugim.com.mx

On 27 Apr 2011, at 18:27, Philippe Marschall wrote:

> - ZnServer class >> #initialize references AutoStart

Zn is not a standard part of this image, so it must have come with Seaside ?
If so, that would be cool, that is something that I want !

Anyway,

ZnServer class>>initialize
       Smalltalk addToStartUpList: self after: AutoStart.

       Smalltalk addToShutDownList: self

Indeed AutoStart seems to be gone.
I just picked that code up somewhere, what should it have to be then ?

Apart from that loading error, all Zn tests are green.

Thx,

Sven