Pharo Vision is becoming reality

Out of the 14 action items laid out in the 5 year vision, /over half now exist one year later/ in the 2.0 release!

Here's the current progress (corrections/updates welcome):

In 2.0:
2a Rewrite of Filesystem
7 Packages as real objects (RPackage)
8 Package Meta-Data (manifest classes)
9 Less Model Clutter and Duplication (Ring)
10 Building and Reusing UI Logic (Spec)
11 New Network Layer (Zinc/Zodiac)
12 Serializers (Fuel)
13 System Change Notifier replacement (SystemAnnouncer)

For 3.0 [1]:
6 Fully parametrized compiler tool chain (this means Opal, right?)
1 A Robust and Extensible System Events (guessing this is event model from [1])
2b Rewrite of Streams
4 UI Canvas for Zoomable Interfaces (I'm assuming this is part of Athens?)

In progress (deadline unclear)
3 Announcements and Ephemerons
5 Bootstrap of the Core
14 Cleaning Morphic

[1] http://forum.world.st/Pharo-3-td4677109.html

On 2013-04-01, at 17:54, "Sean P. DeNigris" <[hidden email]> wrote:

that is done as well I would say :) => Hazelnut

And as for ephemerons,
the implementation exists, and actually it's in our VMs.
But after discussing with Eliot, it needs some work to use separate
object format for it.

On 1 April 2013 17:57, Camillo Bruni <[hidden email]> wrote:


--
Best regards,
Igor Stasenko.

On Apr 1, 2013, at 3:35 PM, "Igor Stasenko [via Smalltalk]" <[hidden email]> wrote:

> And as for ephemerons,
> the implementation exists, and actually it's in our VMs.

So right now, are blocks held weakly by announcers? That was my major use case. Also, do we still have to send #weak or is weak now the default?

On 1 April 2013 22:08, Sean P. DeNigris <[hidden email]> wrote:
> On Apr 1, 2013, at 3:35 PM, "Igor Stasenko [via Smalltalk]" <[hidden email]>
> wrote:
>
>> And as for ephemerons,
>> the implementation exists, and actually it's in our VMs.
>
> So right now, are blocks held weakly by announcers? That was my major use
> case. Also, do we still have to send #weak or is weak now the default?
>
No, the language-side integration is not done.
It should wait till we will have VM ready for it.

> Cheers,
> Sean
>
> ________________________________
> View this message in context: Re: Pharo Vision is becoming reality
>
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.



--
Best regards,
Igor Stasenko.

On Apr 1, 2013, at 5:54 PM, Sean P. DeNigris <[hidden email]> wrote:

> Out of the 14 action items laid out in the 5 year vision, /over half now
> exist one year later/ in the 2.0 release!
>
> Here's the current progress (corrections/updates welcome):
>
> In 2.0:
> 2a Rewrite of Filesystem
> 7 Packages as real objects (RPackage)
                we should continue on that front
                        - less bugs
                        - remove package info
                        - offer new versionner tools supporting key process patterns
                        and generation of configuration
                        - change RPackage used as categories to real package (and get rid of category) + save package tag in monticello metadata
                       
> 8 Package Meta-Data (manifest classes)
> 9 Less Model Clutter and Duplication (Ring)
        we should continue to remove pseudo classes and others

> 10 Building and Reusing UI Logic (Spec)
        we should have a painter

> 11 New Network Layer (Zinc/Zodiac)
> 12 Serializers (Fuel)
> 13 System Change Notifier replacement (SystemAnnouncer)
                - continue to polish that

> For 3.0 [1]:
> 6 Fully parametrized compiler tool chain (this means Opal, right?)
        - not really
        - when Opal is in the image we can continue.
                systemNavigation (is taking an environment as input),
                test runner should be parametrized

> 1 A Robust and Extensible System Events (guessing this is event model from
> [1])
                we should continue to push the work we did to clean the systemevents

> 2b Rewrite of Streams
> 4 UI Canvas for Zoomable Interfaces (I'm assuming this is part of Athens?)
        Yes
>
> In progress (deadline unclear)
> 3 Announcements and Ephemerons
> 5 Bootstrap of the Core
        This is done but we should now have the complete process building from the core.