Re: [Pharo-dev] Keyboard events is broken.

2013-08-07 Thread Guillermo Polito
On Wed, Aug 7, 2013 at 2:41 PM, Igor Stasenko siguc...@gmail.com wrote: My understanding how it should be: - you work in own branch (and in git, repository clone is already a branch, just on your computer). If you want to make it public you need to make own branch on gitorious and commit

Re: [Pharo-dev] Keyboard events is broken.

2013-08-07 Thread Igor Stasenko
On 7 August 2013 15:55, Guillermo Polito guillermopol...@gmail.com wrote: On Wed, Aug 7, 2013 at 2:41 PM, Igor Stasenko siguc...@gmail.com wrote: My understanding how it should be: - you work in own branch (and in git, repository clone is already a branch, just on your computer). If you

Re: [Pharo-dev] Keyboard events is broken.

2013-08-06 Thread Stéphane Ducasse
thanks guillermo :) Cleaning events at VM level is important. On Aug 6, 2013, at 4:32 PM, Guillermo Polito guillermopol...@gmail.com wrote: On Tue, Aug 6, 2013 at 3:40 PM, Igor Stasenko siguc...@gmail.com wrote: I changed this method to see better what happens: HandMorph

Re: [Pharo-dev] Keyboard events is broken.

2013-08-06 Thread Guillermo Polito
And the removal of the debugging code is here https://gitorious.org/cogvm/blessed/commit/9e2a77928edf0144f0d5c42ada66eb18918af64b/diffs/506febc8184dfd6c764d8d8fbc5b08dca8f998c0;) On Tue, Aug 6, 2013 at 5:47 PM, Guillermo Polito guillermopol...@gmail.comwrote: ah, forgot to say. Latest vms from

Re: [Pharo-dev] Keyboard events is broken.

2013-08-06 Thread Guillermo Polito
On Tue, Aug 6, 2013 at 4:53 PM, Stéphane Ducasse stephane.duca...@inria.frwrote: thanks guillermo :) Cleaning events at VM level is important. Cleaning is not so easy :). I've been able to reproduce some of these problems (the delete key and the double keyUp:). I've tried to fix them,

Re: [Pharo-dev] Keyboard events is broken.

2013-08-06 Thread Igor Stasenko
On 6 August 2013 17:47, Guillermo Polito guillermopol...@gmail.com wrote: ah, forgot to say. Latest vms from jenkins should be ready in a while, not yet :). yes, and that's why i want you to answer a following question: why you think the repository was named 'blessed' as in [1]? [1]

Re: [Pharo-dev] Keyboard events is broken.

2013-08-06 Thread Guillermo Polito
On Tue, Aug 6, 2013 at 8:06 PM, Igor Stasenko siguc...@gmail.com wrote: On 6 August 2013 17:47, Guillermo Polito guillermopol...@gmail.com wrote: ah, forgot to say. Latest vms from jenkins should be ready in a while, not yet :). yes, and that's why i want you to answer a following

Re: [Pharo-dev] Keyboard events is broken.

2013-08-06 Thread Stéphane Ducasse
I imagine that having a branch is the way to go. Like that esteban can integrate the fixes of eliot and you do not stress to finish. Once this is ready there is a merge. At least this is what I was thinking the process was: one main blessed stream several others at different

Re: [Pharo-dev] Keyboard events is broken.

2013-08-06 Thread Esteban Lorenzano
ok, jumping in... :) so... there are some problems with the recommended approach. 1) having a branch/trunk whatever that contains just blessed versions in the meaning of stable is a nonsense. For that, is easier to have a zip somewhere. One thing that is complete wrong is to keep VMMaker version