On 11 Mar 2019, at 11:39, Ben Coman <btc@openinworld.com> wrote:



On Mon, 11 Mar 2019 at 15:00, <estebanlm@gmail.com> wrote:
Hello!

This is my weekly ChangeLog, from 4 March 2019 to 10 March 2019.
You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=4/3/2019&to=10/3/2019

ChangeLog
=========

6 March 2019:
-------------

*    I spent last two days trying approaches to make the introduction of +Application+ concept less intrusive.

    Thing is, since several applications can be alive at the same time (in general at least two: Pharo and the 
    application the user is developing, but there can be more), when you create a window, is mandatory to know
    the application it belongs to. 

    And this is a problem.

    Why? Well, because there are two ways to do it: 

    It can be: 

    ----
    MyWindowClass newApplication: myApplication.
    ----

    or:

    ----
    myApplication new: MyWindowClass.
    ----

    And well... both approaches require that you are in possesion of an application when you create a window.

Really random thought...  If somehow a window is created without it knowing the application,
could it create a new application for it - it occurs to me it might be called an "anonymous application"
but I've no idea if that makes sense within the framework, and too many random applications might be unmanageable.

That���s what happens now: they are assigned to an ���NullApplication���. But this means you cannot track flow, etc��� so at the end this should not happen (even if for now is good to allow migration of things).

Esteban


cheers -ben

P.S. Thanks for these ChangeLogs.  Great to see whats in the pipeline.