[Pharo-project] Do you have a tool that works on Pharo ?
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/ Here we have a list of tools that run on Pharo: 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
It is not necesary that you document 10 pages. Just put the name of the project, explain in 2 lines what it is, how to install it, and if you have documentation in some other place, a link. And that's all. For example, I have in mind these projects: aidaWeb scribo Iliad RFB autotest mockery XML support Help system PetitParser Helvetia Opal Gofer RefactoringBrowser Chronos Citizen FileSystem Grease ODBC OSProcess XML-RPC XStreams but I don't know what each of them is exacty, how to install it, or its link. So, if their developers help us it would be cool cheers Mariano On Sun, Mar 20, 2011 at 10:22 PM, Mariano Martinez Peck < marianopeck@gmail.com> 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/
Here we have a list of tools that run on Pharo: 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
Hi Mariano--
Chronos
I mentioned your note to Alan Lovejoy, the developer of Chronos (a Date/Time library, see http://chronos-st.org ). -C -- Craig Latta www.netjam.org/resume +31 06 2757 7177 + 1 415 287 3547
Thanks Graig, and thanks to all who have asked me a user to edit ;) On Tue, Mar 22, 2011 at 3:29 PM, Craig Latta <craig@netjam.org> wrote:
Hi Mariano--
Chronos
I mentioned your note to Alan Lovejoy, the developer of Chronos (a Date/Time library, see http://chronos-st.org ).
-C
-- Craig Latta www.netjam.org/resume +31 06 2757 7177 + 1 415 287 3547
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/
Here we have a list of tools that run on Pharo: 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
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 < 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/
Here we have a list of tools that run on Pharo: 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
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 < 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 < 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/
Here we have a list of tools that run on Pharo: 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
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 < 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 < 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 < 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/
Here we have a list of tools that run on Pharo: 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
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> 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 <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 <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 <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/
Here we have a list of tools that run on Pharo: 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
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. 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
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
Mariano, You are correct, you need 1.0-beta.28 or later for symbolic versons to work. I intend to keep Metacello running on all versions of Pharo and Squeak4.x and GemStone. For example, I load Seaside30 into a Pharo1.0 image every time a new Seaside30 version is released. ... If anyone finds a problem with Metacello on any platform or version report it (send mail to the Metacello Group or submit an issue: http://code.google.com/p/metacello/issues/entry) and I will fix the bug. Which just leaves use with "upgrade magic" and the user will have to do that ... at this point, I don't think it is a good idea to have Metacello "phone home" for automatic upgrading, so it takes a manual operation to upgrade: ConfigurationOfMetacello project updateProject. ConfigurationOfMetacello load. I am continuously fixing bugs in Metacello and I recommend that users periodically update to pick up the latest bug fixes, so it is probably worth mentioning at the beginning of the section that folks should upgrade to the latest Metacello version whether or not they plan to load additional tools. You can check for new versions on this page: http://code.google.com/p/metacello/wiki/10betaVersionDescriptions and you can tell what version you are currently running by printing this expression: ConfigurationOfMetacello project currentVersion. Dale On Mar 21, 2011, at 8:55 AM, Mariano Martinez Peck wrote: On Mon, Mar 21, 2011 at 4:50 PM, Dale Henrichs <dhenrich@vmware.com<mailto: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><mailto: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<mailto:marianopeck@gmail.com>>marianopeck@gmail.com<mailto:marianopeck@gmail.com><mailto: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<mailto:marianopeck@gmail.com>>marianopeck@gmail.com<mailto:marianopeck@gmail.com><mailto: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<mailto:stephane.ducasse@inria.fr>>stephane.ducasse@inria.fr<mailto:stephane.ducasse@inria.fr><mailto: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
Hey great idea, and very informative page although some of them a little outdated. I can update some. Can you create me an account? Thanks El dom, 20-03-2011 a las 22:22 +0100, Mariano Martinez Peck escribió:
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/
Here we have a list of tools that run on Pharo: 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
-- Miguel Cobá http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx
participants (7)
-
Alexandre Bergel -
Craig Latta -
Dale Henrichs -
laurent laffont -
Mariano Martinez Peck -
Miguel Cobá -
Stéphane Ducasse