From b.prior at ieee.org  Sun Dec  4 18:30:20 2011
From: b.prior at ieee.org (Bruce Prior)
Date: Sun, 04 Dec 2011 09:30:20 -0800
Subject: [sbe-discussion] Re: Where is the last version of PBE ?
In-Reply-To: <B89A55BC-720B-4B6F-976A-B2783642E4BB@cs.pdx.edu>
References: <CAOysuxWLQ2bED-hO5CV2xyrpAW90OwAX6kPED2iUaBHqe9JZiA@mail.gmail.com>
	<04F45A9F-15A8-4AB1-BB54-CCE7A8960905@gmail.com>
	<CAOysuxUF7Dr8n8zcnueQxCCCxC87nQ9h4OM=2gBW-ALdUBLW-g@mail.gmail.com>
	<m2hb1xtktl.wl%yoshiki@vpri.org>
	<9CA08508-2E2C-444C-B845-066A7B0B70B1@iam.unibe.ch>
	<FC867993-7C30-4191-B7A9-AB930EC7C42E@cs.pdx.edu>
	<4ECBDECE.7000706@ieee.org>
	<B89A55BC-720B-4B6F-976A-B2783642E4BB@cs.pdx.edu>
Message-ID: <4EDBAE2C.5060500@ieee.org>

Thanks, Andrew.

Stef has signed me on.

Bruce

On 11-11-22 9:48 AM, Andrew P. Black wrote:
> On 22 Nov 2011, at 09:41 , Bruce Prior wrote:
>
>> Hi Andrew,
>>
>> I tried to access the link you provided, but it is closed (needs a password). Perhaps some of us could contribute to the editing of PBE2 if we could see it.
>>
>> Bruce Prior
> There is a page to apply for an account, as there is with github.  It's at https://gforge.inria.fr/.  The name of the project is pharobooks.
>
> One of the questions on the account creation form is:  "Name of the Inria research team you are working with or in".  I'm not sure if one types "Pharobooks" here, or something else.  St?ph?
>
> 	Andrew
>
>
> _______________________________________________
> Sbe-discussion mailing list
> Sbe-discussion at iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/sbe-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/sbe-discussion/attachments/20111204/4dd44fdb/attachment.html>

From sean at clipperadams.com  Tue Dec  6 16:35:53 2011
From: sean at clipperadams.com (Sean P. DeNigris)
Date: Tue, 6 Dec 2011 07:35:53 -0800 (PST)
Subject: [sbe-discussion] Dash character makes it difficult to copy/paste
	code
Message-ID: <1323185753159-4165146.post@n4.nabble.com>

Hi guys, great chapter on Metacello! The toolkit is really cool :) One thing:
the dash character used in the book comes into Pharo as "--" so you have to
change them all to single.

Sean

--
View this message in context: http://forum.world.st/Dash-character-makes-it-difficult-to-copy-paste-code-tp4165146p4165146.html
Sent from the Pharo By Example mailing list archive at Nabble.com.

From sean at clipperadams.com  Wed Dec  7 23:04:10 2011
From: sean at clipperadams.com (Sean P. DeNigris)
Date: Wed, 7 Dec 2011 14:04:10 -0800 (PST)
Subject: [sbe-discussion] Determining what Metacello would load
Message-ID: <1323295450304-4170701.post@n4.nabble.com>

The Metacello chapter is great, especially the workflow part - thank you.

I would mention fetching, which is very useful for testing configs and
before accidentally loading the wrong thing. For example, printing
"ConfigurationOfMyProject project bleedingEdge fetch loadDirective"
gives you a description of what would be loaded in the current image.

Sean

--
View this message in context: http://forum.world.st/Determining-what-Metacello-would-load-tp4170701p4170701.html
Sent from the Pharo By Example mailing list archive at Nabble.com.

From marianopeck at gmail.com  Thu Dec  8 10:20:33 2011
From: marianopeck at gmail.com (Mariano Martinez Peck)
Date: Thu, 8 Dec 2011 10:20:33 +0100
Subject: [sbe-discussion] Re: Determining what Metacello would load
In-Reply-To: <1323295450304-4170701.post@n4.nabble.com>
References: <1323295450304-4170701.post@n4.nabble.com>
Message-ID: <CAA+-=mWWhnxq9sqfnnQGoD=f9UkVvEzVa9ktAupUmUGaA_NbVQ@mail.gmail.com>

On Wed, Dec 7, 2011 at 11:04 PM, Sean P. DeNigris <sean at clipperadams.com>wrote:

> The Metacello chapter is great, especially the workflow part - thank you.
>

Thanks. If you have feedback, as this one, as well as English corrections,
PLEASE give it. You can hace access to the latex files if you want.


> I would mention fetching, which is very useful for testing configs and
> before accidentally loading the wrong thing. For example, printing
> "ConfigurationOfMyProject project bleedingEdge fetch loadDirective"
> gives you a description of what would be loaded in the current image.
>
>
The chapter says:


-----------
\paragraph{Debugging Configuration.}


If you want to simulate the loading of a configuration, without actually
loading it, you should use \ct{record:} instead of \ct{load:}. Then to get
the result of the simulation, you should send it the message
\mthind{loadDirective}{loadDirective} as follows:

\begin{code}{}
  ((ConfigurationOfCoolBrowser project version: '0.2') !\textbf{record:}!
          { 'CoolBrowser-Core' .
        'CoolBrowser-Addons' }) !\textbf{loadDirective}!.
\end{code}

--------


So what is the difference between both?  one uses #fetch and one uses
#record. I don't know exactly the differences but it sounds that #record is
more closed to reality (#load) than #fetch. Dale ?


Thanks!

Sean
>
> --
> View this message in context:
> http://forum.world.st/Determining-what-Metacello-would-load-tp4170701p4170701.html
> Sent from the Pharo By Example mailing list archive at Nabble.com.
> _______________________________________________
> Sbe-discussion mailing list
> Sbe-discussion at iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/sbe-discussion
>



-- 
Mariano
http://marianopeck.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/sbe-discussion/attachments/20111208/0992b4b0/attachment.html>

From stephane.ducasse at free.fr  Thu Dec  8 19:46:26 2011
From: stephane.ducasse at free.fr (stephane ducasse)
Date: Thu, 8 Dec 2011 19:46:26 +0100
Subject: [sbe-discussion] Re: Determining what Metacello would load
In-Reply-To: <1323295450304-4170701.post@n4.nabble.com>
References: <1323295450304-4170701.post@n4.nabble.com>
Message-ID: <8E127A9A-7280-4C51-89DB-72E92868938C@free.fr>


On Dec 7, 2011, at 11:04 PM, Sean P. DeNigris wrote:

> The Metacello chapter is great, especially the workflow part - thank you.
> 
> I would mention fetching, which is very useful for testing configs and
> before accidentally loading the wrong thing. For example, printing
> "ConfigurationOfMyProject project bleedingEdge fetch loadDirective"
> gives you a description of what would be loaded in the current image.


but it is not equivalent to record?

> 
> Sean
> 
> --
> View this message in context: http://forum.world.st/Determining-what-Metacello-would-load-tp4170701p4170701.html
> Sent from the Pharo By Example mailing list archive at Nabble.com.
> _______________________________________________
> Sbe-discussion mailing list
> Sbe-discussion at iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/sbe-discussion
> 



From marianopeck at gmail.com  Thu Dec  8 23:16:35 2011
From: marianopeck at gmail.com (Mariano Martinez Peck)
Date: Thu, 8 Dec 2011 23:16:35 +0100
Subject: [sbe-discussion] Re: [Metacello] Re: Determining what Metacello
	would load
In-Reply-To: <1416189186.623979.1323370966309.JavaMail.root@zimbra-prod-mbox-2.vmware.com>
References: <CAA+-=mWWhnxq9sqfnnQGoD=f9UkVvEzVa9ktAupUmUGaA_NbVQ@mail.gmail.com>
	<1416189186.623979.1323370966309.JavaMail.root@zimbra-prod-mbox-2.vmware.com>
Message-ID: <CAA+-=mXbc-X1ZWKWxQa9xkKzaWKuE0yBee6Nm5Y6SdX=CDrMhA@mail.gmail.com>

Thanks for the explanaiton. It turns I was wrong, I thought #record was
downloadind the mcz files, but it seems this is only done by #fetch, which
makes completly sense!
I will update the chapter. Thanks Sean for asking.



On Thu, Dec 8, 2011 at 8:02 PM, Dale Henrichs <dhenrich at vmware.com> wrote:

> The difference between #fetch: and #record: is that:
>
>  #fetch: accesses and downloads the mcz files from the repository
>
>  #record: simply records which mcz files should be downloaded
>
> So #record: will run a lot faster than #fetch:.
>
> While we're in the neighborhood:
>
>  #load: does a #fetch: followed by a #doLoad on the result of the #fetch:
>
> This means you can do a #fetch:, inspect the result to peruse the list of
> packages that will be loaded and then resume the load with a #doLoad if you
> approve of the load list...
>
> Dale
>
>
> ----- Original Message -----
> | From: "Mariano Martinez Peck" <marianopeck at gmail.com>
> | To: sbe-discussion at iam.unibe.ch
> | Cc: metacello at googlegroups.com
> | Sent: Thursday, December 8, 2011 1:20:33 AM
> | Subject: [Metacello] Re: [sbe-discussion] Determining what Metacello
> would load
> |
> |
> |
> |
> | On Wed, Dec 7, 2011 at 11:04 PM, Sean P. DeNigris <
> | sean at clipperadams.com > wrote:
> |
> |
> | The Metacello chapter is great, especially the workflow part - thank
> | you.
> |
> |
> | Thanks. If you have feedback, as this one, as well as English
> | corrections, PLEASE give it. You can hace access to the latex files
> | if you want.
> |
> |
> |
> |
> | I would mention fetching, which is very useful for testing configs
> | and
> | before accidentally loading the wrong thing. For example, printing
> | "ConfigurationOfMyProject project bleedingEdge fetch loadDirective"
> | gives you a description of what would be loaded in the current image.
> |
> |
> |
> | The chapter says:
> |
> |
> | -----------
> | \paragraph{Debugging Configuration.}
> |
> |
> | If you want to simulate the loading of a configuration, without
> | actually loading it, you should use \ct{record:} instead of
> | \ct{load:}. Then to get the result of the simulation, you should
> | send it the message \mthind{loadDirective}{loadDirective} as
> | follows:
> |
> | \begin{code}{}
> | ((ConfigurationOfCoolBrowser project version: '0.2')
> | !\textbf{record:}!
> | { 'CoolBrowser-Core' .
> | 'CoolBrowser-Addons' }) !\textbf{loadDirective}!.
> | \end{code}
> |
> | --------
> |
> |
> | So what is the difference between both? one uses #fetch and one uses
> | #record. I don't know exactly the differences but it sounds that
> | #record is more closed to reality (#load) than #fetch. Dale ?
> |
> |
> | Thanks!
> |
> |
> |
> | Sean
> |
> | --
> | View this message in context:
> |
> http://forum.world.st/Determining-what-Metacello-would-load-tp4170701p4170701.html
> | Sent from the Pharo By Example mailing list archive at Nabble.com.
> | _______________________________________________
> | Sbe-discussion mailing list
> | Sbe-discussion at iam.unibe.ch
> | https://www.iam.unibe.ch/mailman/listinfo/sbe-discussion
> |
> |
> |
> | --
> | Mariano
> | http://marianopeck.wordpress.com
> |
> |
>



-- 
Mariano
http://marianopeck.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/sbe-discussion/attachments/20111208/7a358f2d/attachment-0001.html>

From sean at clipperadams.com  Thu Dec  8 23:47:42 2011
From: sean at clipperadams.com (Sean P. DeNigris)
Date: Thu, 8 Dec 2011 14:47:42 -0800 (PST)
Subject: [sbe-discussion] Re: [Metacello] Re: Determining what Metacello
	would load
In-Reply-To: <CAA+-=mXbc-X1ZWKWxQa9xkKzaWKuE0yBee6Nm5Y6SdX=CDrMhA@mail.gmail.com>
References: <1323295450304-4170701.post@n4.nabble.com>
	<CAA+-=mWWhnxq9sqfnnQGoD=f9UkVvEzVa9ktAupUmUGaA_NbVQ@mail.gmail.com>
	<CAA+-=mXbc-X1ZWKWxQa9xkKzaWKuE0yBee6Nm5Y6SdX=CDrMhA@mail.gmail.com>
Message-ID: <1323384462326-4174678.post@n4.nabble.com>


Mariano Martinez Peck wrote
> 
> Thanks for the explanaiton. It turns I was wrong, I thought #record was
> downloadind the mcz files, but it seems this is only done by #fetch, which
> makes completly sense!
> 

Thanks for the followup. My pdf must be an older version, which didn't
mention either; but now I understand both :)

--
View this message in context: http://forum.world.st/Determining-what-Metacello-would-load-tp4170701p4174678.html
Sent from the Pharo By Example mailing list archive at Nabble.com.

From stephane.ducasse at free.fr  Fri Dec  9 08:59:20 2011
From: stephane.ducasse at free.fr (stephane ducasse)
Date: Fri, 9 Dec 2011 08:59:20 +0100
Subject: [sbe-discussion] Re: [Metacello] Re: Determining what Metacello
	would load
In-Reply-To: <CAA+-=mXbc-X1ZWKWxQa9xkKzaWKuE0yBee6Nm5Y6SdX=CDrMhA@mail.gmail.com>
References: <CAA+-=mWWhnxq9sqfnnQGoD=f9UkVvEzVa9ktAupUmUGaA_NbVQ@mail.gmail.com>
	<1416189186.623979.1323370966309.JavaMail.root@zimbra-prod-mbox-2.vmware.com>
	<CAA+-=mXbc-X1ZWKWxQa9xkKzaWKuE0yBee6Nm5Y6SdX=CDrMhA@mail.gmail.com>
Message-ID: <E69454C7-802B-4CCE-A4E0-609EC73373A2@free.fr>


On Dec 8, 2011, at 11:16 PM, Mariano Martinez Peck wrote:

> Thanks for the explanaiton. It turns I was wrong, I thought #record was downloadind the mcz files, but it seems this is only done by #fetch, which makes completly sense!
> I will update the chapter.

thanks mariano

you can add that just after the record paragraph

Stef

> Thanks Sean for asking. 
> 
> 
> 
> On Thu, Dec 8, 2011 at 8:02 PM, Dale Henrichs <dhenrich at vmware.com> wrote:
> The difference between #fetch: and #record: is that:
> 
>  #fetch: accesses and downloads the mcz files from the repository
> 
>  #record: simply records which mcz files should be downloaded
> 
> So #record: will run a lot faster than #fetch:.
> 
> While we're in the neighborhood:
> 
>  #load: does a #fetch: followed by a #doLoad on the result of the #fetch:
> 
> This means you can do a #fetch:, inspect the result to peruse the list of packages that will be loaded and then resume the load with a #doLoad if you approve of the load list...
> 
> Dale
> 
> 
> ----- Original Message -----
> | From: "Mariano Martinez Peck" <marianopeck at gmail.com>
> | To: sbe-discussion at iam.unibe.ch
> | Cc: metacello at googlegroups.com
> | Sent: Thursday, December 8, 2011 1:20:33 AM
> | Subject: [Metacello] Re: [sbe-discussion] Determining what Metacello would load
> |
> |
> |
> |
> | On Wed, Dec 7, 2011 at 11:04 PM, Sean P. DeNigris <
> | sean at clipperadams.com > wrote:
> |
> |
> | The Metacello chapter is great, especially the workflow part - thank
> | you.
> |
> |
> | Thanks. If you have feedback, as this one, as well as English
> | corrections, PLEASE give it. You can hace access to the latex files
> | if you want.
> |
> |
> |
> |
> | I would mention fetching, which is very useful for testing configs
> | and
> | before accidentally loading the wrong thing. For example, printing
> | "ConfigurationOfMyProject project bleedingEdge fetch loadDirective"
> | gives you a description of what would be loaded in the current image.
> |
> |
> |
> | The chapter says:
> |
> |
> | -----------
> | \paragraph{Debugging Configuration.}
> |
> |
> | If you want to simulate the loading of a configuration, without
> | actually loading it, you should use \ct{record:} instead of
> | \ct{load:}. Then to get the result of the simulation, you should
> | send it the message \mthind{loadDirective}{loadDirective} as
> | follows:
> |
> | \begin{code}{}
> | ((ConfigurationOfCoolBrowser project version: '0.2')
> | !\textbf{record:}!
> | { 'CoolBrowser-Core' .
> | 'CoolBrowser-Addons' }) !\textbf{loadDirective}!.
> | \end{code}
> |
> | --------
> |
> |
> | So what is the difference between both? one uses #fetch and one uses
> | #record. I don't know exactly the differences but it sounds that
> | #record is more closed to reality (#load) than #fetch. Dale ?
> |
> |
> | Thanks!
> |
> |
> |
> | Sean
> |
> | --
> | View this message in context:
> | http://forum.world.st/Determining-what-Metacello-would-load-tp4170701p4170701.html
> | Sent from the Pharo By Example mailing list archive at Nabble.com.
> | _______________________________________________
> | Sbe-discussion mailing list
> | Sbe-discussion at iam.unibe.ch
> | https://www.iam.unibe.ch/mailman/listinfo/sbe-discussion
> |
> |
> |
> | --
> | Mariano
> | http://marianopeck.wordpress.com
> |
> |
> 
> 
> 
> -- 
> Mariano
> http://marianopeck.wordpress.com
> 
> _______________________________________________
> Sbe-discussion mailing list
> Sbe-discussion at iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/sbe-discussion



From sean at clipperadams.com  Tue Dec 13 02:58:16 2011
From: sean at clipperadams.com (Sean P. DeNigris)
Date: Mon, 12 Dec 2011 17:58:16 -0800 (PST)
Subject: [sbe-discussion] Re: [Metacello] Re: Determining what Metacello
	would load
In-Reply-To: <E69454C7-802B-4CCE-A4E0-609EC73373A2@free.fr>
References: <1323295450304-4170701.post@n4.nabble.com>
	<CAA+-=mWWhnxq9sqfnnQGoD=f9UkVvEzVa9ktAupUmUGaA_NbVQ@mail.gmail.com>
	<CAA+-=mXbc-X1ZWKWxQa9xkKzaWKuE0yBee6Nm5Y6SdX=CDrMhA@mail.gmail.com>
	<E69454C7-802B-4CCE-A4E0-609EC73373A2@free.fr>
Message-ID: <1323741496155-4188420.post@n4.nabble.com>


stephane ducasse wrote
> 
> you can add that just after the record paragraph
> 

Yes, they are both useful. At first, when first testing, I'd like to do a
#fetch because it's more like and end-to-end acceptance test, but the
#record is nice once it's mostly working and I know the packages are
downloadable.

Sean

--
View this message in context: http://forum.world.st/Determining-what-Metacello-would-load-tp4170701p4188420.html
Sent from the Pharo By Example mailing list archive at Nabble.com.

From serge.stinckwich at gmail.com  Thu Dec 15 02:24:29 2011
From: serge.stinckwich at gmail.com (Serge Stinckwich)
Date: Thu, 15 Dec 2011 10:24:29 +0900
Subject: [sbe-discussion] Re: [Pharo-project] 1.3, PBE and lab setups
In-Reply-To: <B4DF8DA2-B2DF-464B-BE08-3FDBBFF540E0@mason-rose.ca>
References: <B4DF8DA2-B2DF-464B-BE08-3FDBBFF540E0@mason-rose.ca>
Message-ID: <CAOysuxVsG0VK0gkKuh=cHs60NNqKYRDAUT0-HFymqLWCsvQnzQ@mail.gmail.com>

2011/12/15 Dave Mason <dmason at mason-rose.ca>:
> I am trying to get our local admins to set up labs so students can use the
> latest Pharo.
>
> Currently we have 1.2 and PBE .image files and by removing the field in the
> INI file that specified the image, if you clicked on Pharo, you'd get a
> dialogue asking which image you wanted. ?All of these are on read-only
> mounts, so if you want to save to the image, you need to copy the image to
> your home directory and then you could navigate to that image file on
> startup. ?Dropping an image on the executable works fine, though.
>
> Additionally, the PBE book doesn't play well with 1.3 (things that the book
> says die when you try them). ?Apparently you can't open the PBE image from
> the 1.3 binary without it crashing, either.
>
> So I have 3 questions:
>
> 1) is 1.3 the system to use, or will 1.4 be stable soon?
>
> 2) is the PBE book getting updated to work with a vanilla 1.3/1.4 image?

There is no plan at the moment to do that, but you could help adapt
the Pharo Book to the new images.
All the contents of the book is here:
https://github.com/SquareBracketAssociates/PharoByExample-english

Maybe we can have branches for each version of Pharo ? pharo1.2,
pharo1.3, etc ...

Regards,
-- 
Serge Stinckwich
UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam
Matsuno Laboratory, Kyoto University, Japan (until 12/2011)
http://www.mechatronics.me.kyoto-u.ac.jp/
Every DSL ends up being Smalltalk
http://doesnotunderstand.org/


From stephane.ducasse at free.fr  Thu Dec 15 08:48:52 2011
From: stephane.ducasse at free.fr (stephane ducasse)
Date: Thu, 15 Dec 2011 08:48:52 +0100
Subject: [sbe-discussion] Re: [Pharo-project] 1.3, PBE and lab setups
In-Reply-To: <CAOysuxVsG0VK0gkKuh=cHs60NNqKYRDAUT0-HFymqLWCsvQnzQ@mail.gmail.com>
References: <B4DF8DA2-B2DF-464B-BE08-3FDBBFF540E0@mason-rose.ca>
	<CAOysuxVsG0VK0gkKuh=cHs60NNqKYRDAUT0-HFymqLWCsvQnzQ@mail.gmail.com>
Message-ID: <063CFD82-6ADC-4A5D-AF39-4FE06BA338A0@free.fr>


On Dec 15, 2011, at 2:24 AM, Serge Stinckwich wrote:

> 2011/12/15 Dave Mason <dmason at mason-rose.ca>:
>> I am trying to get our local admins to set up labs so students can use the
>> latest Pharo.
>> 
>> Currently we have 1.2 and PBE .image files and by removing the field in the
>> INI file that specified the image, if you clicked on Pharo, you'd get a
>> dialogue asking which image you wanted.  All of these are on read-only
>> mounts, so if you want to save to the image, you need to copy the image to
>> your home directory and then you could navigate to that image file on
>> startup.  Dropping an image on the executable works fine, though.
>> 
>> Additionally, the PBE book doesn't play well with 1.3 (things that the book
>> says die when you try them).  Apparently you can't open the PBE image from
>> the 1.3 binary without it crashing, either.
>> 
>> So I have 3 questions:
>> 
>> 1) is 1.3 the system to use, or will 1.4 be stable soon?
>> 
>> 2) is the PBE book getting updated to work with a vanilla 1.3/1.4 image?
> 
> There is no plan at the moment to do that, but you could help adapt
> the Pharo Book to the new images.
> All the contents of the book is here:
> https://github.com/SquareBracketAssociates/PharoByExample-english
> 
> Maybe we can have branches for each version of Pharo ? pharo1.2,
> pharo1.3, etc ?

yes this would be really good to have a branch

Stef

> 
> Regards,
> -- 
> Serge Stinckwich
> UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam
> Matsuno Laboratory, Kyoto University, Japan (until 12/2011)
> http://www.mechatronics.me.kyoto-u.ac.jp/
> Every DSL ends up being Smalltalk
> http://doesnotunderstand.org/
> 
> _______________________________________________
> Sbe-discussion mailing list
> Sbe-discussion at iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/sbe-discussion
> 



From oscar at iam.unibe.ch  Thu Dec 15 11:10:50 2011
From: oscar at iam.unibe.ch (Oscar Nierstrasz)
Date: Thu, 15 Dec 2011 11:10:50 +0100
Subject: [sbe-discussion] Re: [Pharo-project] 1.3, PBE and lab setups
In-Reply-To: <063CFD82-6ADC-4A5D-AF39-4FE06BA338A0@free.fr>
References: <B4DF8DA2-B2DF-464B-BE08-3FDBBFF540E0@mason-rose.ca>
	<CAOysuxVsG0VK0gkKuh=cHs60NNqKYRDAUT0-HFymqLWCsvQnzQ@mail.gmail.com>
	<063CFD82-6ADC-4A5D-AF39-4FE06BA338A0@free.fr>
Message-ID: <6F763E49-5E89-4254-97F6-12BC5FEAD550@iam.unibe.ch>


Sure, that would be great, but please be aware that you must also check that the examples (and tests) work as advertised.

If someone wants to do this please contact me, and I can give some advice and help ...

on

On 15 Dec 2011, at 08:48, stephane ducasse wrote:

> 
> On Dec 15, 2011, at 2:24 AM, Serge Stinckwich wrote:
> 
>> 2011/12/15 Dave Mason <dmason at mason-rose.ca>:
>>> I am trying to get our local admins to set up labs so students can use the
>>> latest Pharo.
>>> 
>>> Currently we have 1.2 and PBE .image files and by removing the field in the
>>> INI file that specified the image, if you clicked on Pharo, you'd get a
>>> dialogue asking which image you wanted.  All of these are on read-only
>>> mounts, so if you want to save to the image, you need to copy the image to
>>> your home directory and then you could navigate to that image file on
>>> startup.  Dropping an image on the executable works fine, though.
>>> 
>>> Additionally, the PBE book doesn't play well with 1.3 (things that the book
>>> says die when you try them).  Apparently you can't open the PBE image from
>>> the 1.3 binary without it crashing, either.
>>> 
>>> So I have 3 questions:
>>> 
>>> 1) is 1.3 the system to use, or will 1.4 be stable soon?
>>> 
>>> 2) is the PBE book getting updated to work with a vanilla 1.3/1.4 image?
>> 
>> There is no plan at the moment to do that, but you could help adapt
>> the Pharo Book to the new images.
>> All the contents of the book is here:
>> https://github.com/SquareBracketAssociates/PharoByExample-english
>> 
>> Maybe we can have branches for each version of Pharo ? pharo1.2,
>> pharo1.3, etc ?
> 
> yes this would be really good to have a branch
> 
> Stef
> 
>> 
>> Regards,
>> -- 
>> Serge Stinckwich
>> UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam
>> Matsuno Laboratory, Kyoto University, Japan (until 12/2011)
>> http://www.mechatronics.me.kyoto-u.ac.jp/
>> Every DSL ends up being Smalltalk
>> http://doesnotunderstand.org/
>> 
>> _______________________________________________
>> Sbe-discussion mailing list
>> Sbe-discussion at iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/sbe-discussion
>> 
> 
> 
> _______________________________________________
> Sbe-discussion mailing list
> Sbe-discussion at iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/sbe-discussion