- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Vm-dev] Squeak and Pharo speed differences
by Shaping May 16, 2020

May 16, 2020

> Squeak 5.3 release notes describe arithmetic improvements. Nice. I crunch very big numbers, and these improvements therefore have value. Why would they not be included in OSVM (forked or not) and the basic class-set for both Squeak and Pharo? The VM changes *are* in the VM code. If pharo haven't bothered to take advantage of them, that's their job to do. There are also image changes involved. Again, somebody has to do the work. > The obvious question is: Will Squeak be improving GUI look/behavior and speed with Spec2? If not, can I load Spec2 into Squeak so that I can do new GUI work there? Unlikely and unlikely. > > Both Squeak and Pharo have slow text selection. Pick any word in any pane, and double click it to select it. Really? I can't detect any difference. And that's with the Squeak running on a Pi and VW on a big iMac. Yeah, itâs bad, and I often wonder why no one says anything about it. It definitely slows my work, and Iâm not talking about the extra time for rendering. Itâs mentally disruptive. It mostly depends on how you detect a double-click as opposed to a single, or a mouse-down-drag etc. I go by the definition of a double click: the button-up event of the second click ends the double-click event. Searching for and rendering of the selected text then begins. This takes roughly 75 to 100 ms consistently in Pharo and Squeak. > (Dolphin and VW have quick GUIs). Never used Dolphin but I disagree about the (currnet)VW GUI; I'm using both for work right now and Squeak (again, on a Pi vs the VW/iMac) seems much faster to me. Note that I was specific about the current porting problem as it relates to GUI deficiencies. The problem is not about general GUI speed (like opening and closing windows), which is okay to good in VW, and better overall in Pharo, especially in a Spec2 component (the Launcher). This problem is about text selection speed. Iâm running Windows 10 Pro on an 2.7 GHz Xeon with 96 GB. I just tried text selection again in Pharo 9 in a Playground and in VW 8.3.2âs Transcript. VW is much faster. This is stopping my port--that and the debuggerâs slowness (even slower than the text selection). The porting problem for me reduces to two little, but extremely important GUI dynamics I experience frequently when coding. > Is speeding up the Pharo debugger with Spec2 a priority? I canât think of a better GUI-related priority for Pharo. Why ask that here? (I thought I was posting to the Pharo lists too; corrected above.) Font importer. It's right there in the Apps list, second row. Yes, I found it. > > - Where in the Squeak and Pharo images can I change mouse-selection behavior to be leading-edge? Some of the Squeak panes have this; others donât. I want leading-edge action in all panes, and wish the feature were in Preferences/Settings. As a general UI point, leading edge action is rarely a good thing. I use leading edge single clicks all the time for most of the last 25 years of Smalltalk coding. The choice is for me as dev, not for clients. The issue is once again about high-speed continuity of gesture and thought during coding. Eliminating the delay matters. Iâve had time to try it both ways. Shaping

1 0

[Pharo 9.0] Build #297: DebugSession: removing "keep-alive" dead-code
by ci-pharo-ci-jenkins2＠inria.fr May 14, 2020

May 14, 2020

There is a new Pharo build available! The status of the build #297 was: FAILURE. The Pull Request #6315 was integrated: "DebugSession: removing "keep-alive" dead-code " Pull request url: https://github.com/pharo-project/pharo/pull/6315 Issue Url: https://github.com/pharo-project/pharo/issues/remove Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #296: 6351-SyntaxErrorDebugger-messes-up-display-state-when-closed
by ci-pharo-ci-jenkins2＠inria.fr May 14, 2020

May 14, 2020

There is a new Pharo build available! The status of the build #296 was: FAILURE. The Pull Request #6352 was integrated: "6351-SyntaxErrorDebugger-messes-up-display-state-when-closed" Pull request url: https://github.com/pharo-project/pharo/pull/6352 Issue Url: https://github.com/pharo-project/pharo/issues/6351 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #295: DeprecateObject-notify-at
by ci-pharo-ci-jenkins2＠inria.fr May 14, 2020

May 14, 2020

There is a new Pharo build available! The status of the build #295 was: SUCCESS. The Pull Request #6348 was integrated: "DeprecateObject-notify-at" Pull request url: https://github.com/pharo-project/pharo/pull/6348 Issue Url: https://github.com/pharo-project/pharo/issues/DeprecateObject Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Pharogenesis?
by Michael Rueger May 14, 2020

May 14, 2020

Hi all, after digging out some old pet project about an archive of historical Smalltalk code I came across the Pharogenesis project (http://scg.unibe.ch/research/Pharogenesis) The git link is unfortunately dead, any chance somebody still has a fork/copy? The source code is still up on SqueakSource, but probably not really useful with the git repo? Cheers Michael

3 2

git and Pharo new book...
by StÃ©phane Ducasse May 13, 2020

May 13, 2020

Hello we are happy to announce a new little book that we hope will help you to master git and Pharo. http://books.pharo.org/booklet-ManageCode/pdf/2020-05-12-ManageCode.pdf <http://books.pharo.org/booklet-ManageCode/pdf/2020-05-12-ManageCode.pdf> Thanks for your reading. S. BTW if you like my pharo free books you can donate at http://stephane.ducasse.free.fr/FreeBooks.html <http://stephane.ducasse.free.fr/FreeBooks.html> -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

2 1

[Pharo 9.0] Build #294: fix-keyUp-keyDown-eventHandler
by ci-pharo-ci-jenkins2＠inria.fr May 12, 2020

May 12, 2020

There is a new Pharo build available! The status of the build #294 was: SUCCESS. The Pull Request #6305 was integrated: "fix-keyUp-keyDown-eventHandler" Pull request url: https://github.com/pharo-project/pharo/pull/6305 Issue Url: https://github.com/pharo-project/pharo/issues/fix Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #293: IRBuilder-fill-TempOffsets
by ci-pharo-ci-jenkins2＠inria.fr May 11, 2020

May 11, 2020

There is a new Pharo build available! The status of the build #293 was: FAILURE. The Pull Request #6198 was integrated: "IRBuilder-fill-TempOffsets" Pull request url: https://github.com/pharo-project/pharo/pull/6198 Issue Url: https://github.com/pharo-project/pharo/issues/IRBuilder Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Mm10s] 2020-05-11
by Esteban Lorenzano May 11, 2020

May 11, 2020

Last week and this one are still in low-motion, but here we are :) ### Last week: * [Spec2] uncovered a bug in RubAbstractTextArea: it does not fires eventHandler events! (but I will need to see how deep is this problem tomorrow, maybe it affects all events there). * [Pharo 9] added a PR (https://github.com/pharo-project/pharo/pull/6305) to fix a missing event handling of keyUp/keyDown events when morphic event handling is used. * [Spec2] add cursorPosition protocol to SpTextPresenters, who will answer a column@row position, instead of cursorPositionIndex who will answer the position in the text (an offset) * [Spec2] add cmd+t to show context menus * [Spec2-doc] SpStyle * [NewTools] add a generic StHeaderPanel to contain a StHeaderBar and a content presenter. Add also a global addWindowShortcurTo: to override on the presenters who wants to add global shortcuts to its owner window. * [NewTools-Playground] add line and cursor position information in the status bar. * [NewTools-Playground] pass on load page dialog (presenter). Is working, but not as I want * [NewTools-Playground] added headers to page selector window. * [NewTools-Playground] auto-save current page * [Spec2] added shortcut based context menu popup for morphic (it was implemented in Gtk already) * [NewTools-Playground] add publish code * [Pharo 9] bug: spanNewSessionFrom: breakes debugging tests (moved to new tools, which is where is actually needed) ### This week (starting 2020-05-11): - move new playground to beta status (open it for test) - finish some keybindings issues on Gtk backend - work on idle vm to fix remaining bugs - sync with Ronnie to start testing lowcode memory access - document transmission sub-framework

2 1

May 11, 2020

Dear Pharo users, lovers, businessers Context ********* You may not know it clearly but the Pharo consortium succeeds to pay one full time engineer: Esteban Lorenzano. Due to legal concerns with the Inria foundation effort, Inria converted the position of Esteban into a permanent position. It was a great deal because it secures Esteban. Now based on contracts between the consortium and Lifeware ( https://www.lifeware.ch <https://www.lifeware.ch/> ) and Schmidt (http://bauing-schmidt.de <http://bauing-schmidt.de/>) the consortium is able to pay another engineer: Pablo Tesone until April 2021. All this was announced at ESUG 2019 but not all of you may have known it. <Mini news> * The consortium has been working to get Pharo in the database of the CNRS platforms (CNRS is a huge research organisation in France covering all research fields. Guillermo Polito has a permanent position from CNRS allocated to the Lille University Lab and we want to convince the lab that having Guille working on Pharo is the best ROI that they can make). * We also are pursing a process to be recognized by the University of Lille for the same reason. We are also working to get PharoPro out of the ground but this is another story. * All these efforts in communication are done to secure people position. We have got many new academic members. Some should be announced soon. </mini news> Now THE announce. ************************* During the last consortium meeting, we learned that David Margery (the Inria software manager that is managing around 10 ofconsortiums for Inria) wants to propose to Inria to allocate another permanent position to Pharo even if the consortium does not raise two full salaries. This will secure the effort of the consortium for the coming years. We were excited by the news because such positions are rare and lifelong! David is building a case to defend his proposal: * first the pharo consortium is in a good shape - thank you all * second, Inria is interested to "assess if Pharo is usedâ David told us that having more industrial partners (even first entry ones) will really help our case: the fact that members are willing to pay to secure the future of Pharo is the key indicator, the amount paid being only secondary. Remember that the first membership fee is at 1K Euros. Therefore the consortium is sending an official call. If you hesitated to join the consortium this is clearly the moment. Your money will be multiplied. Because a full job for an expert engineer is around 90 K so if we get 8 new members at 1/2 K we have a strong multiplication effect and this will have an important impact on Pharo. http://consortium.pharo.org <http://consortium.pharo.org/> http://consortium.pharo.org/web/Membership <http://consortium.pharo.org/web/Membership> So I hope that we convince you that you can get a real impact on Pharo. The consortium engineering team wants to thank all the current consortium member because they make Pharo happening. S. on the behalf of the consortium. -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

1 0