I agree.
Now I would really to see how we can integrate that.
For example
- overrides out
- and removing duplicated functionality (AST once we get the new
compiler).
Stef
I think it is *extremely* important to only have one download.
Having pharo nicely bug-free and with green tests is useless if
every users
of it then uses another image. In addition, I don't want a system
where we
need to explain "which image to use?".
On Pharo-Project, there will be *one* download, and it will be a one-
click image.
meta-package 'Pharo packages' permit easy installation of these
packages. The wiki page is at:
http://code.google.com/p/pharo/wiki/Packages.
The list is way to long, I don't use any of these packages and I
wouldn't want to see them in a "base" image.
It's not that bad... shout, e-completion, refactoring-engine and
OmniBrowser. The Regex will be in Pharo anyway
(it's one of the big mistakes of Smalltalk to not bring a standard
regexp, the result are many hard to understand
methods parsing strings in the base system... and no standard for
developers)
If you look at younger people, e.g the students, they are used to
Eclipse. Refactoring, code completion and
syntax highlighting are for them not optional. For them this is what
an IDE does, there is no question about that.
I think not providing that would be the wrong way to go.
As for size: Most code in Sqeueak are abandoned experiments that
nobody uses, if we clean up, we have a lot of
space to grow for stuff that actually is useful.
Marcus
--
Marcus Denker -- [EMAIL PROTECTED]
http://www.iam.unibe.ch/~denker
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
