yes! But not only it would enable having multiple windows, because now we "downgrade" all the events to the minimum common denominator, and pass a "raw event" captured from each OS, from the vm to the image.
would be nice to do some surgery on the vm, and cut the windowing management and raw event handling away. It belongs in the image, if it can be implemented using NB to the OS UI frameworks, or in a separate app. We just need a surgeon with the time and ability to do so….i've tried in the past and the related VM code was really hard to understand. Fernando pd: There were some discussion around this idea last year in the mailing list. On Sun, Nov 25, 2012 at 9:40 AM, Stéphane Ducasse <[email protected] > wrote: > > On Nov 24, 2012, at 5:19 PM, Sebastian Nozzi wrote: > > >> sure thing i want as many as we want. > > > > Excellent! > > > >> we need to change VM, to let image be in better control of host system > windows. > >> once we will have that, having multiple windows & effects will not > >> pose any problems anymore. :) > > > > Now when you say "host system windowS" you mean... that the plan is to > > have *many* host windows, not just one as is the case? :-O > > we would love that. > This is not because there is not something right now that this is > something we do not want. > We just try to make progress and not open too many projects. Finishing is > important to pass to the > next level. > > > > > > I was just referring to the Morphic class SystemWindow... > > > > Cheers, > > > > Sebastian > > > > >
