On Mon, Mar 21, 2011 at 4:50 PM, Dale Henrichs <dhenrich@vmware.com> wrote:
Alexandre,

I agree that symbolic versions should be used in load expressions (when defined), but that should be #'stable', with some missing parens:

�((Smalltalk at: #ConfigurationOfOCompletion) project version: #'stable') load.

Another problem I found is that symbolic versions where integrated AFTER Pharo 1.0 and 1.1 were released.
So, if you document that people should use #stable instead....then they will raise an error in Pharo 1.0 or 1.1.
A possible solution is to change your conf so that it makes sure to update Metacello. BUt this is complicated because you cannot be sure that metacello will always work there.
IF metacello 28 (where symbolics are) works perfect in 1.0 and 1.1, AND IF there is a magic way to tell metacello to update only to .28�� then we can add such code in #stable� or some place in the conf..� but I am not sure.� I prefer to document clearly.

cheers

mariano


�

Dale


On Mar 21, 2011, at 4:00 AM, Alexandre Bergel wrote:


Shouldn't it be:
(Smalltalk at: #ConfigurationOfOCompletion) project version: 'stable' load.

Instead?

Alexandre

Le 21 mars 2011 � 03:13, laurent laffont <laurent.laffont@gmail.com<mailto:laurent.laffont@gmail.com>> a �crit :

Mariano,

I've added Autotest.

I've seen a lot of Configuration example which won't work because of missing parenthesis:

(Smalltalk at: #ConfigurationOfOCompletion) project version: '1.1.2' load.

should be

((Smalltalk at: #ConfigurationOfOCompletion) project version: '1.1.2') load.


I cannot fix it now - must go to work.

Laurent

On Sun, Mar 20, 2011 at 11:40 PM, Mariano Martinez Peck <<mailto:marianopeck@gmail.com>marianopeck@gmail.com<mailto:marianopeck@gmail.com>> wrote:
I've added:

- Gofer
- Monticello
- Metacello
- Fuel

If you can check and improve it..please do. It only took me 30 mins.

Cheers

Mariano


On Sun, Mar 20, 2011 at 11:12 PM, Mariano Martinez Peck <<mailto:marianopeck@gmail.com>marianopeck@gmail.com<mailto:marianopeck@gmail.com>> wrote:
I forgot...If someone answer "but you can browse the MetecelloRepository" or "XX" or "blah"....the answer is that we are not targeting the same people. Someone that knows how that he has to browse MetacelloRepository, probably knows how to install the software, what it is, etc.
With this page (after, moved to the pharo website) we want to targe business and new comers. Imagine someone arriving to Pharo and asking himseld "mmmmm does Pharo have XXX that I have in YYY language? ". So the idea is to show all the available tools.

Cheers

Mariano


On Sun, Mar 20, 2011 at 10:42 PM, St�phane Ducasse <<mailto:stephane.ducasse@inria.fr>stephane.ducasse@inria.fr<mailto:stephane.ducasse@inria.fr>> wrote:
thanks mariano this is a good initiative.

Stef

On Mar 20, 2011, at 10:22 PM, Mariano Martinez Peck wrote:

> ifTrue: [ self writeOnPharoBook: aTool]
>
> We need to improve our documentation. Right now, we have a collaborative book where everyone can join and write: <http://book.pharo-project.org/> http://book.pharo-project.org/
>
> Here we have a list of tools that run on Pharo: <http://book.pharo-project.org/book/PharoTools> http://book.pharo-project.org/book/PharoTools
> and it is REALLY important to have such list updated and maintained.
>
> So, if you have a tool that works in pharo and it is not there, please add it. If you don't have a user, I can create one for you. If you are TOO lazy, you can send by email the text to me and I write it.
>
> Thanks
>
> Mariano