[Pharo-project] About Pharo - text to go with version 1.0
Hello, I am thinking that some "getting started" info is a good idea for Pharo 1.0. As a first part, I have tried to compile various statements "about pharo" and what I read on the mailing list into a short text (see below). Does that capture what people doing the work are thinking about the project? Anything I should add? Anything you don't like? Cheers Matthias =About Pharo= The goal of the Pharo Project is to produce a clean and lean open-source Smalltalk for professional software development: * great tools, e.g. OmniBrowser with refactoring support * polished user interface with TrueType fonts and Polymorph widgets * clean and lean image * works out-of-the-box, with clear ways to add functionality Starting from version 1.0, Pharo wants to be stable to make sure that we can produce ideas based on it. An important test for Pharo is that mission critical Seaside (http://www.seaside.st) applications should run on it. Pharo started from Squeak (http://www.squeak.org) [which version, 3.10?] but it is a fork: Do not expect Etoy/Nebraska to work in Pharo. We will try to avoid to reinvent the wheel but will change if changing is better. Pharo wants to take a fresh look at the Smalltalk philosophy and current implementations. Ideally by 2011 we would like to have a small kernel and some cool packages that we can load on top. The current focus is not to produce such a kernel but good packages. Everybody is welcome to contribute. You can find a wiki, bug tracker, and a mailing list via the Pharo home page at http://www.pharoproject.org ==License== [A few words about the code that is already there in Pharo, please] Any code developed and committed to the SqueakSource/Pharo and PharoInbox repository is by default under the MIT License.
On Wed, Nov 5, 2008 at 10:12 PM, Matthias Berth <matthias.berth@googlemail.com> wrote:
* great tools, e.g. OmniBrowser with refactoring support * polished user interface with TrueType fonts and Polymorph widgets
Don't give the tool names. Newcomers don't care.
Starting from version 1.0, Pharo wants to be stable to make sure that we can produce ideas based on it. An important test for Pharo is that mission critical Seaside (http://www.seaside.st) applications should run on it.
Pharo started from Squeak (http://www.squeak.org) [which version, 3.10?]
3.9
but it is a fork: Do not expect Etoy/Nebraska to work in Pharo.
Again, Newcomers don't care in my opinion.
We will try to avoid to reinvent the wheel but will change if changing is better. Pharo wants to take a fresh look at the Smalltalk philosophy and current implementations. Ideally by 2011 we would like to have a small kernel and some cool packages that we can load on top. The current focus is not to produce such a kernel but good packages.
[A few words about the code that is already there in Pharo, please]
Pharo is a free open-source Smalltalk under the MIT License. -- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
On Thu, 6 Nov 2008 08:00:14 +0100 "Damien Cassou" <damien.cassou@gmail.com> wrote:
On Wed, Nov 5, 2008 at 10:12 PM, Matthias Berth <matthias.berth@googlemail.com> wrote:
* great tools, e.g. OmniBrowser with refactoring support * polished user interface with TrueType fonts and Polymorph widgets
Don't give the tool names. Newcomers don't care.
... if they don't know the names from somewhere else. And newcomers are not the only ones reading "about" docs. How about "... with scalable fonts (TrueType) and ??? widgets (Polymorph)"
but it is a fork: Do not expect Etoy/Nebraska to work in Pharo.
Again, Newcomers don't care in my opinion.
Again: a newcomer to Pharo is not necessarily a newcomer to Smalltalk or Squeak. I am a case in point: I intermittently dabbled with Squeak, so I have a rough knowledge about the "kid stuff" living in the image. A clear statement that this (for me) irrelevant stuff and its supporting cruft is removed, is a plus. Just making Smalltalk, s.
Damien, Stefan, thanks for the comments - good points. I have tried to improve the text, see http://code.google.com/p/pharo/wiki/GettingStartedAbout It now has a list of packages that Pharo includes and another list of things that are not included. Newcomers can ignore these. Cheers Matthias On Thu, Nov 6, 2008 at 11:22 AM, Stefan Schmiedl <s@xss.de> wrote:
On Thu, 6 Nov 2008 08:00:14 +0100 "Damien Cassou" <damien.cassou@gmail.com> wrote:
On Wed, Nov 5, 2008 at 10:12 PM, Matthias Berth <matthias.berth@googlemail.com> wrote:
* great tools, e.g. OmniBrowser with refactoring support * polished user interface with TrueType fonts and Polymorph widgets
Don't give the tool names. Newcomers don't care.
... if they don't know the names from somewhere else. And newcomers are not the only ones reading "about" docs. How about
"... with scalable fonts (TrueType) and ??? widgets (Polymorph)"
but it is a fork: Do not expect Etoy/Nebraska to work in Pharo.
Again, Newcomers don't care in my opinion.
Again: a newcomer to Pharo is not necessarily a newcomer to Smalltalk or Squeak. I am a case in point: I intermittently dabbled with Squeak, so I have a rough knowledge about the "kid stuff" living in the image. A clear statement that this (for me) irrelevant stuff and its supporting cruft is removed, is a plus.
Just making Smalltalk, s.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Fri, 7 Nov 2008 21:50:27 +0100 "Matthias Berth" <matthias.berth@googlemail.com> wrote:
Damien, Stefan,
thanks for the comments - good points. I have tried to improve the text, see
http://code.google.com/p/pharo/wiki/GettingStartedAbout
It now has a list of packages that Pharo includes and another list of things that are not included. Newcomers can ignore these.
Nice and clear, starting with understandable stuff, while ending on a technical upbeat :-) Good work! s.
participants (3)
-
Damien Cassou -
Matthias Berth -
Stefan Schmiedl