December 2018 - Pharo-dev - lists.pharo.org

[Pharo 7.0] Build #84: 22833-PluggableTextMorph-and-co-should-be-removed

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #84 was: FAILURE. The Pull Request #2121 was integrated: "22833-PluggableTextMorph-and-co-should-be-removed" Pull request url: https://github.com/pharo-project/pharo/pull/2121 Issue Url: https://pharo.fogbugz.com/f/cases/22833 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 28, 2018

Re: [Pharo-dev] [Moose-dev] glamorous toolkit: v0.4.0

by Tudor Girba

Hi, Thanks for the feedback! I am happy you like the new possibilities and that you see the incentives to move to the new world :). The inspector part is working quite well. The main reason we call it an alpha is because of the missing pieces to get to a full environment. You noticed the issue of Spotter. The existing Spotter is the one that is included in the old GT and it lives in the Morphic world. When the focus is in the new inspector, that means that keybindings are handled by Bloc and this is a separate world from Morphic. At present time, we can embed Bloc in Morphic but not the other way around as we want no binding from Bloc to Morphic. For this reason, unhandled keys are not propagated from Bloc to Morphic and that is why pressing Shift+Enter does not open Spotter. So, we will have a Spotter, but that will be another implementation. Other unfinished tools are the Debugger and Coder, but these are likely less relevant for your use case. A few other missing pieces: - some widgets such as a tree are not yet implemented. So, we do not yet have a tree view in inspector. - the text editor requires a few enhancements for navigation support. - scrollbar The Miller-columns interface can be scrolled with the touchpad left-right. Can you confirm? About clicking vs double-clicking: Indeed, we now distinguish between selecting and spawning. As soon as there is a page to the right, selecting will populate that page. However, if there is no page to the right, simply selecting in a list will not spawn, like in the old inspector. Like this, you can work on a page without the page scrolling from underneath you. Please note that between pages we have triangles which are actually buttons. Selecting in a list shows a triangle. Clicking on the triangle spawns. So, you can either double-click to spawn, or you can select and then click on the triangle. Once spawned, simple selection is enough. Does this clarify the situation? About Roassal: In the new GT we have GtMondrian which is similar to the one from Roassal. We do not yet have support for creating charts (like bar or line charts). About the porting strategy: When you have the new GT loaded, the old Inspector will get a _GT pane that will essentially embed the new views in the old inspector. These also allow for interaction. Like this, you can port at your pace and switch only when you are ready. Cheers, Doru > On Dec 27, 2018, at 11:36 AM, Luke Gorrie <luke(a)snabb.co> wrote: > > ... Some comments and questions if I may: > > The "+" button to quickly maximize a panel is fantastic. I am often looking at complex visualizations that should really be full-screen and it was always too much trouble to "drag" them to full screen and back. > > Is the Spotter still a part of GToolkit? If not then what replaces it? (I can see that it is present in the image but Shift-Return doesn't seem to invoke it when the GTInspector window has focus.) > > Is it still possible to pan left-right between "miller columns"? I see the squares at the top representing panes but clicking and dragging them doesn't seem to do anything. > > How come a double-click is now needed to inspect an object? Is single-click going to have a new function? > > Once more - great work you guys are doing ! > > On Thu, 27 Dec 2018 at 11:06, Luke Gorrie <luke(a)snabb.co> wrote: > Hi Doru, > > Thank you very much for the detailed explanation. > > I have spent some time with the alpha now. I think it is absolutely fantastic! > > I love the new narrative style of the UI. This ties everything together beautifully and makes it easy to explore. That's really what I am lacking in my application. Currently it simply opens to a blank quasi-playground and it is not obvious what to type or how to get started. I started writing a separate HTML manual but I don't think that's the right medium -- much better with something interactive in the image like the Documenter. > > Just clicking around everything seemed to work basically smoothly for me. Maybe it's already time for me to port over to the new GT? Or what do you think the most likely obstacles would be in transitioning to this alpha version? > > Currently my custom inspector extensions are mostly based on Roassal and List/Tree/Table views. I also have one or two Glamour browsers. Is that all still there in one form or another? > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.feenk.com "Every thing has its own flow."

Dec. 28, 2018

Re: [Pharo-dev] [ANN] Pharo Lambda Runtime

by Pierce Ng

On Thu, Dec 27, 2018 at 10:32:03AM +0100, Jan van de Sandt wrote: > Last month Amazon extended their serverless runtime platform AWS Lambda > with support for custom runtimes. I created a Pharo Lambda Runtime so now > we can implement Lambda functions in Smalltalk and easily deploy them on > the Lambda platform. Lamba has quite a large "free-tier", more than enough > to do some experiments and to host small applications for free. Very nice! Thanks for making this. Pierce

Dec. 27, 2018

[Pharo 7.0] Build #83: 22841-Fix-printString-related-bugs

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #83 was: SUCCESS. The Pull Request #2131 was integrated: "22841-Fix-printString-related-bugs" Pull request url: https://github.com/pharo-project/pharo/pull/2131 Issue Url: https://pharo.fogbugz.com/f/cases/22841 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 27, 2018

[Pharo 7.0] Build #82: 22826-senders-of-asNonTranslucentColor-should

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #82 was: SUCCESS. The Pull Request #2125 was integrated: "22826-senders-of-asNonTranslucentColor-should" Pull request url: https://github.com/pharo-project/pharo/pull/2125 Issue Url: https://pharo.fogbugz.com/f/cases/22826 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 27, 2018

Re: [Pharo-dev] [ANN] Pharo 8.0 development started

by Torsten Bergmann

and 11. There is no https://get.pharo.org/80 yet ... Bye T.

Dec. 27, 2018

Re: [Pharo-dev] [ANN] Pharo 8.0 development started

by Torsten Bergmann

Hi Esteban, you know I'm neither shy on contributing nor doing any work for Pharo but personally I think we open Pharo 8 too early and should better focus our efforts more on finalizing P7 (see below) instead of opening the next construction site. Things were already shaky and sometimes painful with P7 - nonetheless I managed to get 762 commits into it. Often simple or boring PR's just to get packages, classes, methods in shape and clean up. Funny enough I can now say I'm on top of https://github.com/pharo-project/pharo/graphs/contributors ;) I had a hard time finding out how things work in the new git/pharo/externally managed projects combination - sometimes also with broken or unfinished tools. A newly opened P8 so early adds even more on top... Several things directly came into my mind: 1. http://bugs.pharo.org now points to nirvana now 2. http://ci.pharo.org point to nirvana now as well 3. It's unclear to me what will happen to the bugtracker mailinglist archive. Currently I often use it to stay informed about our changes. Will it stop in december? https://lists.gforge.inria.fr/pipermail/pharo-bugtracker/ 4. The CI for Pharo 7 was not green in most of the latest commits ... and situation for Pharo 8 is not even better now: RED all over on https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… 5. We still have dirty packages in Pharo 7 - the last remaining issue here https://github.com/pharo-ide/Calypso/issues/386 is still not solved and there was no reaction on Discord after reminding it twice. 6. Calypso still has hard issue in Pharo 7 - most of them already fixed in Calypso project. But integration of the new Calypso version is still pending https://github.com/pharo-project/pharo/pull/2115 Nonetheless we already switch to P8? 7. A change done lately (around 17.12.) was resetting the build numbers - so for whatever strange reason we started with 1 again althoug we were already at Build 1416 for Pharo 7 with all the integrations. https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… This build number issue was not yet fixed although this is a serious issue to compare image buils or be able to download using Launcher. Nonetheless we already switch to P8? 8. Lately we switched the branches from "development" to "Pharo7.0" and now also "Pharo8.0". This was also just announced - without any discussion in advance forcing people to resetup their tools and local repos. This change is still not event reflected in the contribution guideline ... but we already switch to Pharo 8 9. We still have lots of important and must-fix cases for Pharo 7 https://pharo.fogbugz.com/f/filters/1412/7-0-All 10. There was nothing said about backporting strategy between the new P8 and P7 now... To me it would already help a little bit to clarify the above raised points and get a more detailed info about the next P7 steps towards the release. Independent from that I fear we constantly decouple more and more people with too many process and contribution scheme changes at once. From the discussions on Discord I already see many people struggle - and often not only the beginners. Bye T.

Dec. 27, 2018

Re: [Pharo-dev] [ANN] Pharo 8.0 development started

by Alistair Grant

Hi Esteban, On Thu, 27 Dec 2018 at 15:52, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi Alistair, > > Iâm waiting to fix some issues in current VM build (new freetype lib, ensure Athens will work on 64bit windows) and I was going to declare that âfinal vm for Pharo7â. > Then this final VM for P7 will be the first for P8 :) Great, that will include the updates that I'm waiting for: updates to FileAttributesPlugin. I'll then be able to (finally) submit the patch for the image code. Thanks! Alistair > Esteban > > > On 27 Dec 2018, at 15:11, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > > > Hi Esteban, > > > > Can I get in an early request for a new VM for Pharo 8? > > > > Since the normal process is to ensure the VM is at least 2 weeks old > > it doesn't require any action now, and of course it can wait until > > Pharo 7 is released. > > > > - Linux 64 bit: > > http://files.pharo.org/vm/pharo-spur64/linux/pharo-linux-x86_64threaded-201… > > - Mac 64 bit: http://files.pharo.org/vm/pharo-spur64/mac/pharo-mac-x86_64-201812211409-10… > > - Win 32 bit: http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386-201812211809-e14d… > > > > Thanks! > > > > Alistair > > > > On Thu, 27 Dec 2018 at 09:51, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> > >> Hello all, > >> > >> We are preparing to release Pharo 7.0 (which will be in January, as soon as we finish some last details). And in the meantime impatient people has asked (and obtained) the aperture of Pharo 8.0 development! :) > >> > >> So you now can start making Pull Requests against Pharo8.0 branch :) > >> > >> Esteban > > > >

Dec. 27, 2018

Re: [Pharo-dev] [ANN] Pharo 8.0 development started

by Esteban Lorenzano

Hi Alistair, Iâm waiting to fix some issues in current VM build (new freetype lib, ensure Athens will work on 64bit windows) and I was going to declare that âfinal vm for Pharo7â. Then this final VM for P7 will be the first for P8 :) Esteban > On 27 Dec 2018, at 15:11, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Esteban, > > Can I get in an early request for a new VM for Pharo 8? > > Since the normal process is to ensure the VM is at least 2 weeks old > it doesn't require any action now, and of course it can wait until > Pharo 7 is released. > > - Linux 64 bit: > http://files.pharo.org/vm/pharo-spur64/linux/pharo-linux-x86_64threaded-201… > - Mac 64 bit: http://files.pharo.org/vm/pharo-spur64/mac/pharo-mac-x86_64-201812211409-10… > - Win 32 bit: http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386-201812211809-e14d… > > Thanks! > > Alistair > > On Thu, 27 Dec 2018 at 09:51, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> Hello all, >> >> We are preparing to release Pharo 7.0 (which will be in January, as soon as we finish some last details). And in the meantime impatient people has asked (and obtained) the aperture of Pharo 8.0 development! :) >> >> So you now can start making Pull Requests against Pharo8.0 branch :) >> >> Esteban >

Dec. 27, 2018

Re: [Pharo-dev] [ANN] Pharo 8.0 development started

by Alistair Grant

Hi Esteban, Can I get in an early request for a new VM for Pharo 8? Since the normal process is to ensure the VM is at least 2 weeks old it doesn't require any action now, and of course it can wait until Pharo 7 is released. - Linux 64 bit: http://files.pharo.org/vm/pharo-spur64/linux/pharo-linux-x86_64threaded-201… - Mac 64 bit: http://files.pharo.org/vm/pharo-spur64/mac/pharo-mac-x86_64-201812211409-10… - Win 32 bit: http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386-201812211809-e14d… Thanks! Alistair On Thu, 27 Dec 2018 at 09:51, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hello all, > > We are preparing to release Pharo 7.0 (which will be in January, as soon as we finish some last details). And in the meantime impatient people has asked (and obtained) the aperture of Pharo 8.0 development! :) > > So you now can start making Pull Requests against Pharo8.0 branch :) > > Esteban

Dec. 27, 2018