On 03/10/2008, at 2:50 PM, Stéphane Ducasse wrote:
By professional we mean: clean and robust, Of course we would like
to have a good layout and UI. But someone has to do it. :)
What is also important is that people get the fredom to invent new
things and that pharo keeps making progress even at the price to be
incompatible.
I have slightly different goals. I'm less concerned about cleaning up
Squeak to start with, more concerned with making something that is
commercially focussed, with support, that is packaged to allow it to
cross the chasm. To that end I don't care about breaking everything
that I don't intend to support, so my refactoring can be quite
aggressive.
I'm focused on Traits + OmniBrowser.
My reasons for attempting a commercial development is to generate a
revenue stream that ensures continuity of development, so that it
doesn't become abandonware. I'm planning for a situation like
MyEclipse. I can support this project for at least a few years without
revenue.
Is your code free?
Yes, that code is. I haven't explicitly licensed it yet.
Now may be you could join gary effort with polymorph?
My ongoing efforts are commercial, so it's probably not possible. And
I've got a very definite architecture in progress already.
Did you check the way newspeak does it with hopstoch
I was working on a dynamic document-based model before hopscotch was
demonstrated, so yes. I have a background in structured document
editors, which is what motivates me.
What do you mean by new packaging. We are thinking about a module
system but for milestone 4 or 5 (one year or two from now).
My packaging/modularity project is called MirrorImage - some details
are on my blog. It works with VW, although I haven't really released
it because there wasn't much interest, and in any case VW is the wrong
community for such proposals.
MirrorImage is a reworking of how classes are defined. In particular
it uses a DSL approach to system construction that allows classes to
be incrementally constructed, with contributions from different
'Projects' that can be prioritized with dependencies etc based on a
configuration algebra. Such contributions can be more that simply
adding vars and methods (ala GST) - you can delete/add/transform/
shadow any part of the code model (ivar/cvar/methods/traits etc).
Transformation is useful for changing the way traits are integrated
into a class you want to change.
Traits also have an interesting interaction with system construction
from a pragmatic perspective because they act as a conceptual
delimiter, although that may be less interesting once I don't have to
rely on the completely braindead method-category string prefix model
of packaging. My #1 dislike in Squeak.
Can you bootstrap the kernel?
Not yet, I was about to do that when I decided to switch from VW. I
will bootstrap the Kernel using the same technique that Lisp systems
use to bootstrap.
Once that works it will also be the tool I use to cut out the stuff I
don't intend to support.
One which version of Squeak are you based?
I started with the Damien's 3.10 dev packaging, although I'm thinking
of switching to Pharo as a base.
Antony Blakey
-------------
CTO, Linkuistics Pty Ltd
Ph: 0438 840 787
There is nothing more difficult to plan, more doubtful of success, nor
more dangerous to manage than the creation of a new order of things...
Whenever his enemies have the ability to attack the innovator, they do
so with the passion of partisans, while the others defend him
sluggishly, So that the innovator and his party alike are vulnerable.
-- Niccolo Machiavelli, 1513, The Prince.
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
