but really, the problem is that those issues are mistaking issues�� For OSWindow integration they are understanding three things:

1) the integration of OSWindow mechanism as a way to control the system window.

2) the replacement of current input event mechanism with a new, image-level one, more complete and modern.

3) the replacement of current BitBlt system window with one based on SDL2 and vectorial graphics (Athens-based).

As you might imagine�� steps 2 and 3 are really needed, but far from easy.

The only step that we could mark as ��done�� right now is the first one�� steps 2 and 3 are ��more or less�� worked�� there are prototypes but still not realistic estimation of what amount of time will take to actually do it�� It is ��thought�� to be done in Pharo5�� we��ll see.

And the problem on integrating some of those changes is that are ��one-way-shots�� once done, we cannot go back.

I will mark some of those issues as ��on hold�� with a clarification.

On 18 Feb 2015, at 16:12, Nicolai Hess <nicolaihess@web.de> wrote:

2015-02-18 15:46 GMT+01:00 Esteban Lorenzano <estebanlm@gmail.com>:
it depends on your definition of ��status�� :)

:)
That is easy to define:
definition of "status" = fogbugz status
-> OSWindow 6 open issues

first version is integrated
latest vm includes also SDL2 plugin.

but is there as *preview*, which means a lot of work still needs to be done.

cheers,
Esteban

On 18 Feb 2015, at 14:12, Nicolai Hess <nicolaihess@web.de> wrote:

What is the state of OSWindow integration?
This release or later?

2015-02-18 13:28 GMT+01:00 Esteban Lorenzano <estebanlm@gmail.com>:
Hi,

So�� I��m announcing that we will not introduce any new change to Pharo4 after February 28, and we will work on stabilisation and bug fixed�� we are aiming to release in April 1st.
This version will not be spur-based, that will come with the summer release.

Cheers,
Esteban