April 2019 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-users] [ANN] (Re)Introducing Mars (Spec 2.0 Gtk3 bindings)

by Norbert Hartl

Great! Can you explain what is there, what somebody can load and what to expect. And even more important: what not to expect? I donât get any of the essential details from this mail. Norbert > Am 18.04.2019 um 12:08 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > People that assisted to Pharo Days 2019 (or that follow my twitter account) already know this, but it needs to be formally announced: > > We are working on Spec 2.0, and it will provide not just the classic Morphic bindings but also a new option for developers: Gtk3 bindings! > > Why we want a Spec 2.0 with different backends? > > There are reasons that converged to decide us to make it: > > First, to provide a validated abstract Spec 2.0 that can be used with different backends, preparing Pharo to be able to switch backends without needing to recreate the full IDE from scratch each time (a problem we have partially now in our way to deprecate Morphic). > Second, because we receive from different sources the requirement of having the possibility of developing real native-looking desktop applications. Yes, in moment where people talk about the cloud, SaaS and web-applications as the "next big thing" (something that is been declared since years, by the way), we believe is important to provide this, for two big reasons: > Because there is still an important place for desktop applications market and most medium-size to big business still require them. > Because Pharo itself is a desktop application! (And we need to provide the best experience possible on it). > > For us, this is a fundamental step to continue improving Pharo itself, and it matches also the work we are doing on going real-headless: Pharo users will be able to start the Morphic world, a Gtk application or the next backend to come. > > Why Gtk3? > > There are some other important players in the "native widgets scene", so why we choose Gtk3? > > Again, several reasons were taken into account: > > Gtk3 is cross platform. Yes, technically is just "native" in linux, but it works on Windows and macOS too. > It is very mature and popular. > It is made in plain C. > > Next step: tool migration > > The only way to know if you have covered what is needed is actually taking real-life use cases and implementing them. We have a list of tools that needs to be migrated and we are starting from them: > > Old GT tools will be replaced by new Spec tools (while preserving its power). > Calypso UI needs to be rewritten in Spec 2.0 (it is in plain Morphic now). > Pharo launcher as a standalone application is a good example of what you can do with the Gtk3 bindings. > > And that's it. Pharo 8.0 will come with Spec 2.0 and users will be able to benefit of it immediately :) > > > A small screenshot of the new Inspector (WIP): > > <Screenshot 2019-04-18 at 12.07.16.png> > > Esteban

April 18, 2019

Re: [Pharo-dev] [ANN] (Re)Introducing Mars (Spec 2.0 Gtk3 bindings)

by Esteban Lorenzano

Ah yesâ¦ and same in morphic (but this is kind of boring ;): > On 18 Apr 2019, at 12:08, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > People that assisted to Pharo Days 2019 (or that follow my twitter account) already know this, but it needs to be formally announced: > > We are working on Spec 2.0, and it will provide not just the classic Morphic bindings but also a new option for developers: Gtk3 bindings! > > Why we want a Spec 2.0 with different backends? > > There are reasons that converged to decide us to make it: > > First, to provide a validated abstract Spec 2.0 that can be used with different backends, preparing Pharo to be able to switch backends without needing to recreate the full IDE from scratch each time (a problem we have partially now in our way to deprecate Morphic). > Second, because we receive from different sources the requirement of having the possibility of developing real native-looking desktop applications. Yes, in moment where people talk about the cloud, SaaS and web-applications as the "next big thing" (something that is been declared since years, by the way), we believe is important to provide this, for two big reasons: > Because there is still an important place for desktop applications market and most medium-size to big business still require them. > Because Pharo itself is a desktop application! (And we need to provide the best experience possible on it). > > For us, this is a fundamental step to continue improving Pharo itself, and it matches also the work we are doing on going real-headless: Pharo users will be able to start the Morphic world, a Gtk application or the next backend to come. > > Why Gtk3? > > There are some other important players in the "native widgets scene", so why we choose Gtk3? > > Again, several reasons were taken into account: > > Gtk3 is cross platform. Yes, technically is just "native" in linux, but it works on Windows and macOS too. > It is very mature and popular. > It is made in plain C. > > Next step: tool migration > > The only way to know if you have covered what is needed is actually taking real-life use cases and implementing them. We have a list of tools that needs to be migrated and we are starting from them: > > Old GT tools will be replaced by new Spec tools (while preserving its power). > Calypso UI needs to be rewritten in Spec 2.0 (it is in plain Morphic now). > Pharo launcher as a standalone application is a good example of what you can do with the Gtk3 bindings. > > And that's it. Pharo 8.0 will come with Spec 2.0 and users will be able to benefit of it immediately :) > > > A small screenshot of the new Inspector (WIP): > > <Screenshot 2019-04-18 at 12.07.16.png> > > Esteban

April 18, 2019

[ANN] (Re)Introducing Mars (Spec 2.0 Gtk3 bindings)

by Esteban Lorenzano

People that assisted to Pharo Days 2019 (or that follow my twitter account) already know this, but it needs to be formally announced: We are working on Spec 2.0, and it will provide not just the classic Morphic bindings but also a new option for developers: Gtk3 bindings! Why we want a Spec 2.0 with different backends? There are reasons that converged to decide us to make it: First, to provide a validated abstract Spec 2.0 that can be used with different backends, preparing Pharo to be able to switch backends without needing to recreate the full IDE from scratch each time (a problem we have partially now in our way to deprecate Morphic). Second, because we receive from different sources the requirement of having the possibility of developing real native-looking desktop applications. Yes, in moment where people talk about the cloud, SaaS and web-applications as the "next big thing" (something that is been declared since years, by the way), we believe is important to provide this, for two big reasons: Because there is still an important place for desktop applications market and most medium-size to big business still require them. Because Pharo itself is a desktop application! (And we need to provide the best experience possible on it). For us, this is a fundamental step to continue improving Pharo itself, and it matches also the work we are doing on going real-headless: Pharo users will be able to start the Morphic world, a Gtk application or the next backend to come. Why Gtk3? There are some other important players in the "native widgets scene", so why we choose Gtk3? Again, several reasons were taken into account: Gtk3 is cross platform. Yes, technically is just "native" in linux, but it works on Windows and macOS too. It is very mature and popular. It is made in plain C. Next step: tool migration The only way to know if you have covered what is needed is actually taking real-life use cases and implementing them. We have a list of tools that needs to be migrated and we are starting from them: Old GT tools will be replaced by new Spec tools (while preserving its power). Calypso UI needs to be rewritten in Spec 2.0 (it is in plain Morphic now). Pharo launcher as a standalone application is a good example of what you can do with the Gtk3 bindings. And that's it. Pharo 8.0 will come with Spec 2.0 and users will be able to benefit of it immediately :) A small screenshot of the new Inspector (WIP): Esteban

April 18, 2019

[ANN] Next Pharo Sprint: April 26

by Marcus Denker

We will organize a Pharo sprint / Moose dojo April 26, starting at 10:00am. (Local Time Paris). Goals of this sprint: - Pharo 8: Fix issues from tracker https://github.com/pharo-project/pharo/issues Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events We have added a Board to coordinate the work: https://github.com/orgs/pharo-project/projects/9 Known Local Sprint meetings Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come

April 18, 2019

[Pharo 8.0] Build #230: 3199 Cleanup testAsBit methods

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

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

April 18, 2019

[Pharo 8.0] Build #229: Fixing the broken test

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

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

April 18, 2019

Re: [Pharo-dev] Handling of deprecation packages

by Torsten Bergmann

Hi Stef, It's not a big problem. I primary wanted to ask what is the status and overall plan. The problem with the new vs. old streams seems to be that migration is unfinished even for the base image. Development already switched quickly to newer construction sites instead of finishing these old ones. That does not mean that I do not appreciate the new journeys Pharo 8 will bring - but it still gives this bad feeling of important transitions are incomplete and should have been addressed first. That's why also "Deprecated70" could not easily get removed. And there is no guide in how to migrate to the new stream. At least I do not know of something that could quickly explain on how to convert. If we integrate a "Deprecated80" (which I think we should do to continue deprecating stuff like required for issue #3186) it could easily lead to confusion when we have two deprecated packages. For "Deprecated70" and "Deprecated80" it might be clear from the name but as for P7 there were also deprecations for other packages like "Ring-Deprecated*" it might not be clear over time when and how they were deprecated. The previous scheme we used to directly remove old deprecations when a new Pharo release iteration started was at least more clear and I think it helped people to better sort out what and when to stop using stuff. Bye T. > Gesendet: Donnerstag, 18. April 2019 um 08:26 Uhr > Von: "ducasse" <stepharo(a)netcourrier.com> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-dev] Handling of deprecation packages > > Hi torsten > > I do not remember if I migrated deprecated70 to the migrator package. > I should check but if someone else wants to have a look even better. > Then my thought was that the streams are important and making the live of people easier to migrate > important too especially since we cannot fully automate Stream deprecation. > > Now I would like to understand why this is so a problem for you? > > Stef > > > On 17 Apr 2019, at 23:15, Torsten Bergmann <astares(a)gmx.de> wrote: > > > > Hi, > > > > in the past after each release iteration one of the first things applied to a new development image > > - was to remove the "DeprecatedXX" package of the previous version XX > > - and add a new "DeprecatedYY" package for the new pharo version YY > > > > This allowed then to mark classes that should get obsolete for version YY and put them into "DeprecatedYY" > > > > But in current Pharo 8 dev image we still have the "Deprecated70" package inside and a new "Deprecated80" > > is not yet opened. > > > > I know there > > - were some discussion about having a "migrator" tool first to help in the transition to the new release > > (but I guess this "migrator" could be written using P7 image, no?) > > > > - we can also not just delete "Deprecated70" as StandardFileStream, MultiByteFileStream and others are > > still useds in the code without giving a proper > > > > So I wonder what is the status and on plan this in P8 > > > > Thx > > T. > > > > > >

April 18, 2019

Re: [Pharo-dev] Handling of deprecation packages

by ducasse

Hi torsten I do not remember if I migrated deprecated70 to the migrator package. I should check but if someone else wants to have a look even better. Then my thought was that the streams are important and making the live of people easier to migrate important too especially since we cannot fully automate Stream deprecation. Now I would like to understand why this is so a problem for you? Stef > On 17 Apr 2019, at 23:15, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi, > > in the past after each release iteration one of the first things applied to a new development image > - was to remove the "DeprecatedXX" package of the previous version XX > - and add a new "DeprecatedYY" package for the new pharo version YY > > This allowed then to mark classes that should get obsolete for version YY and put them into "DeprecatedYY" > > But in current Pharo 8 dev image we still have the "Deprecated70" package inside and a new "Deprecated80" > is not yet opened. > > I know there > - were some discussion about having a "migrator" tool first to help in the transition to the new release > (but I guess this "migrator" could be written using P7 image, no?) > > - we can also not just delete "Deprecated70" as StandardFileStream, MultiByteFileStream and others are > still useds in the code without giving a proper > > So I wonder what is the status and on plan this in P8 > > Thx > T. >

April 18, 2019

Re: [Pharo-dev] Roassal Animations

by Norbert Hartl

Great! Will this be part of the minimal roassal? That could improve documentation quite a bit. Norbert > Am 18.04.2019 um 01:05 schrieb Alexandre Bergel <alexandre.bergel(a)me.com>: > > Hi! > > Just as a follow up, we have a UML diagram builder for Roassal3. > > You can load Roassal3 using: > Metacello new > baseline: 'Roassal3'; > repository: 'github://ObjectProfile/Roassal3/src'; > load. > > As indicated on https://github.com/ObjectProfile/Roassal3 > > An UML class diagram can be open using: > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > | builder pharoClassesToBeVisualized | > > "Zooming and position of the view can be controled using the keys: > I O Space > Arrows > " > > pharoClassesToBeVisualized := > TSAbstractLine > withAllSubclasses. > > builder := > RSUMLClassBuilder > new. > builder classes: pharoClassesToBeVisualized. > > builder classDescriptor > methods: [ :cls | | methods | > methods := cls methods sorted: [ :a :b | > a selector < b selector ] ]. > > builder build. > builder view when: > TSExtentChangedEvent > do: [ builder view zoomToFit ]. > builder open > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > We now do have a support for UML class diagrams and we can easily add new features, if wanted. > > > > Cheers, > Alexandre & Milton > > >> On Mar 27, 2019, at 3:37 PM, ducasse <stepharo(a)netcourrier.com> wrote: >> >> >> >>> On 27 Mar 2019, at 18:27, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>> >>> >>> From: Alexandre Bergel <alexandre.bergel(a)me.com> >>> Subject: Re: [Pharo-dev] Roassal Animations >>> Date: 27 March 2019 at 18:27:28 CET >>> To: Pharo Development List <pharo-dev(a)lists.pharo.org> >>> >>> >>> Thanks to all of you for your nice words. >>> These posts are a teaser of what is coming. Code of each animation is part of Roassal3. Note that we have made no official announcement, simply because Roassal3 is still well behind Roassal2 in terms of offered features. Actually, you cannot do much with Roassal3, beside having cool visualization. >>> >>> We will tell you more soon, once we have a UML renderer and code dependency visualizer :-) >>> >>> We are currently working on a nice distribution that can be shipped within Pharo 8. >> >> :) >> >> >

April 18, 2019

Re: [Pharo-dev] Roassal Animations

by Mariano Martinez Peck

Yeah I have been following Milton animarioma and they are great! On Wed, Apr 17, 2019, 20:06 Alexandre Bergel via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > Hi! > > Just as a follow up, we have a UML diagram builder for Roassal3. > > You can load Roassal3 using: > > Metacello new > baseline: 'Roassal3'; > repository: 'github://ObjectProfile/Roassal3/src'; > load. > > > As indicated on https://github.com/ObjectProfile/Roassal3 > > An UML class diagram can be open using: > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > | builder pharoClassesToBeVisualized | > > "Zooming and position of the view can be controled using the keys: > I O Space > Arrows > " > > pharoClassesToBeVisualized := > TSAbstractLine > withAllSubclasses. > > builder := > RSUMLClassBuilder > new. > builder classes: pharoClassesToBeVisualized. > > builder classDescriptor > methods: [ :cls | | methods | > methods := cls methods sorted: [ :a :b | > a selector < b selector ] ]. > > builder build. > builder view when: > TSExtentChangedEvent > do: [ builder view zoomToFit ]. > builder open > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > We now do have a support for UML class diagrams and we can easily add new > features, if wanted. > > > Cheers, > Alexandre & Milton > > > On Mar 27, 2019, at 3:37 PM, ducasse <stepharo(a)netcourrier.com> wrote: > > > > On 27 Mar 2019, at 18:27, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > > > *From: *Alexandre Bergel <alexandre.bergel(a)me.com> > *Subject: **Re: [Pharo-dev] Roassal Animations* > *Date: *27 March 2019 at 18:27:28 CET > *To: *Pharo Development List <pharo-dev(a)lists.pharo.org> > > > Thanks to all of you for your nice words. > These posts are a teaser of what is coming. Code of each animation is part > of Roassal3. Note that we have made no official announcement, simply > because Roassal3 is still well behind Roassal2 in terms of offered > features. Actually, you cannot do much with Roassal3, beside having cool > visualization. > > We will tell you more soon, once we have a UML renderer and code > dependency visualizer :-) > > We are currently working on a nice distribution that can be shipped within > Pharo 8. > > > :) > > > >

April 17, 2019