The Pharo Linux Vm [WAS] Squeak VM+FT2Plugin, all Pharo 1.0 rc3 tests green

If someone is interested, these are all the packages I needed to install in order not to have problems in my Ubuntu 9.10:

sudo apt-get install linux-libc-dev libecasound2.2-dev libasound2-dev libc6-dev gnulib libc6-dev libpulse-dev libxrender-dev uuid-dev

Should be on Pharo website, given the popularity of Ubuntu.

Ok.....but not only plugins. For exaple, if I don't want UTF-8 ?

errr... maybe it's time to ask to the vm-dev list :)

 

ufff.....what an idiot...thanks!  did you already discovered I am a newbie here ? :)

Me too, but a little less every day :)

Laurent Laffont

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

If someone is interested, these are all the packages I needed to install in order not to have problems in my Ubuntu 9.10:

sudo apt-get install linux-libc-dev libecasound2.2-dev libasound2-dev libc6-dev gnulib libc6-dev libpulse-dev libxrender-dev uuid-dev

Should be on Pharo website, given the popularity of Ubuntu.

I was thinking to add that to the readme.txt. Laurent, can you please download VM:

http://gforge.inria.fr/frs/download.php/24736/pharo-vm-0.15.2f-linux.zip

From my point of view, we need to distribute a Linux VM that:

- Has a easy way to install. I think your VM is cool in these point. I found Exupery a bit more tricky.
- Has FreeType installed
- Has an EXCELLENT README.TXT that explains how to compile from source, how to install it, how to use it, and a FAQ for tipical questions. For example, in Ubuntu, these libraries has to be installed in order to compile. What happend with 64 bits? All that has to be explained in that file

- In the README.TXT we also have to put links for help: squeakvm site, posts like Laurent or Adrain
- Gunification
- It needs to have a name of PharoXXX. Not squeak. This is VERY confusing for newcomers.

- It has to include sources. I know a lot of people that says "I won't put anything in production that I cannot compile by myself first".

- It has to be a Standard VM, not Exupery. Exupery without the exupery package, has no sense at all. It is in Pharo download just because of history reasons. Bryce was very helpful and was the first in put closures in the VM. So, we used that. Now, it has no sense anymore.

- Pass all PharoRC3 tests in green
- The process has to be repeatable. Someone has to be able to came in 1 year, donwload the same VM and repeat the steps without major problems.
- The readme.txt has to include the SVN revision where the C code was taken.
- It would also be good to said which ConfigurationOfVmMaker version was used.

Cheers

Mariano


 

Ok.....but not only plugins. For exaple, if I don't want UTF-8 ?

errr... maybe it's time to ask to the vm-dev list :)

 

ufff.....what an idiot...thanks!  did you already discovered I am a newbie here ? :)

Me too, but a little less every day :)

Laurent Laffont

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

 

- In the README.TXT we also have to put links for help: squeakvm site, posts like Laurent or Adrain
- Gunification
- It needs to have a name of PharoXXX. Not squeak. This is VERY confusing for newcomers.

I agree we need to explain better the distinction between the VM and the image. I'm not sure about renaming squeak-vm -> pharo-vm. It's not a fork. I tend to think it will bring higher confusion.

 

 

- Pass all PharoRC3 tests in green
- The process has to be repeatable. Someone has to be able to came in 1 year, donwload the same VM and repeat the steps without major problems.
- The readme.txt has to include the SVN revision where the C code was taken.
- It would also be good to said which ConfigurationOfVmMaker version was used.

Agree.

Maybe you can open a git repository on INRIA servers so we can keep track of patches + README included in the VM for Pharo. I've used Javier and Levente patches and these are not included in squeak-vm svn. I sent a mail last week on vm-dev but no answers.
This way builders can do:
git clone git://......squeak-vm
cd ..squeak-vm../build
... configure && make && make install.
For packagers it would be cool.
Developpers can have their own branches and submit patches more easily, add more visibility.
With git-svn we can synchronize from official Squeak-VM svn (until they switched to git or another DVCS :)

What do you think ?

Laurent Laffont
 

Cheers

Mariano


 

Ok.....but not only plugins. For exaple, if I don't want UTF-8 ?

errr... maybe it's time to ask to the vm-dev list :)

 

ufff.....what an idiot...thanks!  did you already discovered I am a newbie here ? :)

Me too, but a little less every day :)

Laurent Laffont

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

2010/3/29 Mariano Martinez Peck <[hidden email]>:

>
>>
>>
>>>
>>> - In the README.TXT we also have to put links for help: squeakvm site,
>>> posts like Laurent or Adrain
>>> - Gunification
>>> - It needs to have a name of PharoXXX. Not squeak. This is VERY confusing
>>> for newcomers.
>>
>> I agree we need to explain better the distinction between the VM and the
>> image. I'm not sure about renaming squeak-vm -> pharo-vm. It's not a fork. I
>> tend to think it will bring higher confusion.
>
> I don't agree. Image you are a new comer. For you, Pharo is Pharo. You
> probaly have no idea what Squeak is. So...you go to Pharo website, and
> download the image, and the VM. Imagine when you go to download the VM and
> it says "SqueakVM". I would say "WTF?????"    "WTF is squeak?"
> I am not saying forking the VM. Just to rename it. Actually, the windows VM
> has that name:
> "http://gforge.inria.fr/frs/download.php/26654/PharoVM-Win32-3.11.8.zip"
> And the same with exupery:
> "http://gforge.inria.fr/frs/download.php/24736/pharo-vm-0.15.2f-linux.zip"

Yes and also having a Pharo icon and not a Squeak one.

--
Serge Stinckwich
UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam
Every DSL ends up being Smalltalk
http://doesnotunderstand.org/

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

 

- In the README.TXT we also have to put links for help: squeakvm site, posts like Laurent or Adrain
- Gunification
- It needs to have a name of PharoXXX. Not squeak. This is VERY confusing for newcomers.

I agree we need to explain better the distinction between the VM and the image. I'm not sure about renaming squeak-vm -> pharo-vm. It's not a fork. I tend to think it will bring higher confusion.

I don't agree. Image you are a new comer. For you, Pharo is Pharo. You probaly have no idea what Squeak is. So...you go to Pharo website, and download the image, and the VM. Imagine when you go to download the VM and it says "SqueakVM". I would say "WTF?????"    "WTF is squeak?"
I am not saying forking the VM. Just to rename it. Actually, the windows VM has that name: "http://gforge.inria.fr/frs/download.php/26654/PharoVM-Win32-3.11.8.zip"
And the same with exupery: "http://gforge.inria.fr/frs/download.php/24736/pharo-vm-0.15.2f-linux.zip"

Maybe you can open a git repository on INRIA servers so we can keep track of patches + README included in the VM for Pharo. I've used Javier and Levente patches and these are not included in squeak-vm svn. I sent a mail last week on vm-dev but no answers.
This way builders can do:
git clone git://......squeak-vm
cd ..squeak-vm../build
... configure && make && make install.
For packagers it would be cool.
Developpers can have their own branches and submit patches more easily, add more visibility.
With git-svn we can synchronize from official Squeak-VM svn (until they switched to git or another DVCS :)

What do you think ?

I like the idea....but what about the sync with the public/official SVN repo ? how we will be able to merge ? or the GIT repo will be only for patches ?

Cheers

Mariano

 

Laurent Laffont
 

Cheers

Mariano


 

Ok.....but not only plugins. For exaple, if I don't want UTF-8 ?

errr... maybe it's time to ask to the vm-dev list :)

 

ufff.....what an idiot...thanks!  did you already discovered I am a newbie here ? :)

Me too, but a little less every day :)

Laurent Laffont

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

On Mar 29, 2010, at 9:29 45AM, Mariano Martinez Peck wrote:

>
> Yes! The windows VM has already that. The MacVM, I sent an email few months ago to explain how to do it.
> If you want, I can upload a Squeak 4.2.2beta1U.app   but with the Pharo icons and named Pharo 4.2.2beta1U.app
> Then we link from the website to that VM. What do you think ?
>
> I know there are newer MacOS VMs, but they are still in beta and for the Pharo 1.0 I think the best VM is the 4.2.2.beta1
>
> What do you think ?
>
> Cheers
>
> Mariano

Please use 4.2.3.beta1, as it includes the bitblt fixes which affects StrikeFont rendering.
So if someone switches to Bitmap DejaVu fonts, they don't have to be annoyed their text looks strange when dragging windows :)

Cheers,
Henry

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

On 2010-03-29, at 12:29 AM, Mariano Martinez Peck wrote:

Yes! The windows VM has already that. The MacVM, I sent an email few months ago to explain how to do it.
If you want, I can upload a Squeak 4.2.2beta1U.app   but with the Pharo icons and named Pharo 4.2.2beta1U.app
Then we link from the website to that VM. What do you think ?

I know there are newer MacOS VMs, but they are still in beta and for the Pharo 1.0 I think the best VM is the 4.2.2.beta1

What do you think ?

Cheers

Mariano 

That would be a 4.2.3b1  VM since it contains the bitblt fixes that the Squeak folks wanted. I have no 

idea how that impacts text rendering on Pharo.  

Also this week I will ship a 4.2.4b1 VM which is the result of some Squeak 4.0 base VM merge processing and contains the fix to enable the loading of old image segments used I guess by squeakmap?

Frankly in all of this perhaps we should consider the use of the Version 5. 0 macintosh cocoa VM running in 32bit mode? 

--

===========================================================================

John M. McIntosh <[hidden email]>   Twitter:  squeaker68882

Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com

===========================================================================

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

On Mar 29, 2010, at 21:52 , Mariano Martinez Peck wrote:

> 2010/3/29 John M McIntosh <[hidden email]>
>

>> Also this week I will ship a 4.2.4b1 VM which is the result of some Squeak
>> 4.0 base VM merge processing and contains the fix to enable the loading of
>> old image segments used I guess by squeakmap?
>>
>>
>
> I am not sure.  ImageSegment is a full of c...and maybe it will be even
> removed. It was not working since a lot of time and nobody says anything.

Mariano, I know you know image segments, but I think this is may be confusing for others. So I like to say something ;)

Image segments work very well; both from a reliability and performance point of view. We are using them for hundreds of customers. DabbleDB uses images segments as well AFAIK.

There are two parts, the primitives implemented by the VM in C and the image-side code. The code in the image consists of support code to load and store a segment and on top of this there is code for swapping in/out classes, projects etc. Especially the latter is a mess and we already started cleaning it. As images segments are not used by core code we also consider moving it into a separate, external package (of course, the primitives should stay in the VM).

> We
> even started to remove part of it in Pharo. And SqueakMap was completely
> removed.

Yes, SqueakMap is not relevant anymore for Pharo. Hence, this VM fix is not critical for us.

Cheers,
Adrian

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project