- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Spec bindings assignment

by Benjamin

Now the bindings are provided to the interpreter and not to the model it self. Can you point me where to load your code, like that I have an interesting use case :) Thanks Ben On Dec 6, 2012, at 9:28 AM, Pavel Krivanek wrote: > Hi Ben, > > what was changed in the Spec bindings assignment in the new Spec versions? Because Periscope uses own subclass of MorphicBindings to provide own widgets including window widget but now only standard widgets are used and the different binding is not taken into account. > > Cheers, > -- Pavel

Dec. 6, 2012

Re: [Pharo-project] Progress Update

by Sven Van Caekenberghe

Thanks a lot for all the hard work, Camillo. You are improving Pharo a lot - often by just doing the hard work on your own. All these UX improvements are the icing on the internal cleanups. On 06 Dec 2012, at 13:05, Camillo Bruni <camillobruni(a)gmail.com> wrote: > I promised to fix my partial refactoring for the ProgressBar. > Finally this evening I hacked on the whole progress mess :), now I am almost done with one little bug left. > > - the progress bar is always responsive > - all processes showing a progress with priority <60 can be interrupted > - refreshes periodically 16 times per second > - only forces a manual refresh when blocking the UI > - no more out of bounds progress bars > - no more ugly display buffer pattern when resizing the screen during a running progress > > this is a massive improvement for me :) For instance now you can simply interrupt the test runner > with a click on the progress bar. > > I have one bug left, that is when I run the test runner, the UI event handling gets > somehow disturbed. Windows no longer receive events, but everything is directly forwarded > to the World. Opening the World menu is the only thing you can do :/ > > > Anyone has a clue? The slice is in the inbox, see issue > > http://code.google.com/p/pharo/issues/detail?id=7103 > > > best > cami

Dec. 6, 2012

Re: [Pharo-project] [update 2.0] #20430

by Guillermo Polito

:D!!!!! On Thu, Dec 6, 2012 at 1:18 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > 20430 > ----- > > Issue 7056: integrate NativeBoost > http://code.google.com/p/pharo/issues/detail?id=7056 > > Diff information: > http://ss3.gemstone.com/ss/Pharo20/Kernel-EstebanLorenzano.1264.diff > > Yep, finally NativeBoost (v 1.7) is integrated into the system. You still > need a special VM to use it, I'm working now in produce branded Pharo VMs > with NB support out of the box. > > > >

Dec. 6, 2012

Re: [Pharo-project] [update 2.0] #20430

by Camillo Bruni

yes !! On 2012-12-06, at 09:18, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > 20430 > ----- > > Issue 7056: integrate NativeBoost > http://code.google.com/p/pharo/issues/detail?id=7056 > > Diff information: > http://ss3.gemstone.com/ss/Pharo20/Kernel-EstebanLorenzano.1264.diff > > Yep, finally NativeBoost (v 1.7) is integrated into the system. You still need a special VM to use it, I'm working now in produce branded Pharo VMs with NB support out of the box. > > >

Dec. 6, 2012

Re: [Pharo-project] An excellent news

by Peter Hugosson-Miller

On Wed, Dec 5, 2012 at 9:41 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > Hi guys > > We mentioned it in the past but now this is really official. To support > the consortium, Inria is paying one full year > to Igor Stasenko. > > We want to thank Inria for its continuous support. > > Stef > Nice! Thanks INRIA, and congratulations Igor :-) -- Cheers,

Dec. 6, 2012

[Pharo-project] [update 2.0] #20430

by Esteban Lorenzano

20430 ----- Issue 7056: integrate NativeBoost http://code.google.com/p/pharo/issues/detail?id=7056 Diff information: http://ss3.gemstone.com/ss/Pharo20/Kernel-EstebanLorenzano.1264.diff Yep, finally NativeBoost (v 1.7) is integrated into the system. You still need a special VM to use it, I'm working now in produce branded Pharo VMs with NB support out of the box.

Dec. 6, 2012

[Pharo-project] Progress Update

by Camillo Bruni

I promised to fix my partial refactoring for the ProgressBar. Finally this evening I hacked on the whole progress mess :), now I am almost done with one little bug left. - the progress bar is always responsive - all processes showing a progress with priority <60 can be interrupted - refreshes periodically 16 times per second - only forces a manual refresh when blocking the UI - no more out of bounds progress bars - no more ugly display buffer pattern when resizing the screen during a running progress this is a massive improvement for me :) For instance now you can simply interrupt the test runner with a click on the progress bar. I have one bug left, that is when I run the test runner, the UI event handling gets somehow disturbed. Windows no longer receive events, but everything is directly forwarded to the World. Opening the World menu is the only thing you can do :/ Anyone has a clue? The slice is in the inbox, see issue http://code.google.com/p/pharo/issues/detail?id=7103 best cami

Dec. 6, 2012

[Pharo-project] gemfire "transferred"

by Esteban Lorenzano

I wonder how this will impact our friends of Gemstone :) http://www.infoq.com/news/2012/12/vmware-spins-out-spring

Dec. 6, 2012

[Pharo-project] [update 2.0] #20429

by Marcus Denker

Dec. 6, 2012

[Pharo-project] Spec bindings assignment

by Pavel Krivanek

Hi Ben, what was changed in the Spec bindings assignment in the new Spec versions? Because Periscope uses own subclass of MorphicBindings to provide own widgets including window widget but now only standard widgets are used and the different binding is not taken into account. Cheers, -- Pavel

Dec. 6, 2012