- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #786: 4670-Deprecation-transfrom-make-sure-the-fallback-is-signal

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

There is a new Pharo build available! The status of the build #786 was: FAILURE. The Pull Request #4723 was integrated: "4670-Deprecation-transfrom-make-sure-the-fallback-is-signal" Pull request url: https://github.com/pharo-project/pharo/pull/4723 Issue Url: https://github.com/pharo-project/pharo/issues/4670 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 26, 2019

[Pharo 8.0] Build #785: OpalSemanticCleanup

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

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

Sept. 26, 2019

PharoLauncher not opening Pharo 7 image on Mac

by Tudor Girba

Hi, Does any of you ever had the problem of a PharoLauncher that does not want to open the image on Mac? We just installed a PharoLauncher from today, added it in /Applications, and when pressing the play button for a Pharo 7 image, nothing happens. Running the same image with the VM that PharoLauncher downloaded works though. Any idea of what could be wrong? Cheers, Doru -- feenk.com "Some battles are better lost than fought."

Sept. 26, 2019

Re: [Pharo-dev] [Pharo-users] Pumping FFI documentation [WAS] FFI beginner question

by ducasse

Hi ted > Thank you, I will; community support will be important -- developers (and > their managers!) are very conscious of the "critical mass" issue. What I can tell you is that we are growing :). When a company with more than 30 millions lines of code wants to migrate to Pharo. It means something :) and we are helping them and they actively support the consortium with immediate impact. Pablo is working full time to improve pharo and we feel it. > They all want to know that if they make an investment in learning and using a new > language, tools, development paradigm, etc. that there's a company/support > structure/resources behind it that will exist for a long time to come. No > one wants to "get stuck" with an orphan product or technology -- even if it > is attractive at first. (The culture here can be a bit risk-averse in > places.) Yes there is a strong support from the community and from the consortium. This is why we create the consortium (since 2012). It is here to support companies and pharo development and pharo and its community are growing steadily. Esteban went to give special lectures or coaching to companies in the past. Since a year the consortium is supporting Schmidt Pro and Lifeware based on contract and so far this is working well. We will continue. Also what is important is that Mooc is a key assets: why because it represents 15 years of teaching experience. There are OOP teachers that are learning things on OOP when watching the mooc. So the mooc is not only about pharo. Now a smart guy can learn Pharo in two days (Henrique Rocha did it and we hired him :), and after 2 weeks to play with the ide you can start to get fluent. BTW the Mooc value is around 150 Keuros and it is free because we did it and it was sponsored by our institute and some other universities. > We also welcome open-source projects, and use them freely. Adopting Pharo > would not be substantially different than our current widespread use of > Linux, C/C++, Python, Lua, Tcl, SVN, Git, etc. There's definitely a place > for it here. But very few know about it! Yes this is why we can help to show how we do things. We will tell you also where we are not so good and where we want to go. Right now we are starting a real effort for the following years on the virtual machine. One day we will revise the Pharo vision document (should be on internet somewhere) but it shows that we have a vision/roadmap and that we built it. > I've attended a Tech Talk (and plan to join tomorrow's talk). And I'm aware > of the consortium; I joined the Pharo Association myself as an individual. > There's no reason why we wouldn't/couldn't do so as an academic > organization, at some point (assuming my plans succeed). > > We have an unusual situation: JPL may be part of NASA (they own the > buildings, the equipment, the property, fund the projects, etc.), but we are > not civil servants -- we don't work for the federal government as do other > NASA center staff. We're actually staff members of Caltech, under > privileged long-term contract. So I can either be "a government employee" > (via contract) or "an academic staff member", depending (usually on what > kind of discount some business may be offering. ;^) :) You see you can play it the way you want. The first ticket for a company is 1000 euros and else you can play as an official academic member of the consortium. Now what is more important is that we listen to our users. So the consortium roadmap is validated by the consortium members and we are helping as much as we can. Our goal is to make people succeed with their Pharo projects. We want to create a vertuous ecosystem. A super concrete example, feenk reported that the windows update 1903/4 changed something and that their guys working on windows could not access git via libgit anymore. Pablo and Guille put this on their highest priority just after ESUG and it was solved within a couple of days. Feenk got problems with a binding or headless VM and pablo pair programmed with one of their engineering during ESUG. > So it may be easier as Caltech to have an academic association. Something > also for the futureâ¦ Academic membership is simple and free. You have the same document than the industrial member. And I think that Caltech fit there. Now we also have some academics that pay to support Pharo. But this is the way people want to play it. > > -t > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Sept. 25, 2019

[Pharo 8.0] Build #784: 4701-Review-asInteger-

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

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

Sept. 25, 2019

Re: [Pharo-dev] [Pharo-users] Pumping FFI documentation [WAS] FFI beginner question

by Brainstorms

Thank you, I will; community support will be important -- developers (and their managers!) are very conscious of the "critical mass" issue. They all want to know that if they make an investment in learning and using a new language, tools, development paradigm, etc. that there's a company/support structure/resources behind it that will exist for a long time to come. No one wants to "get stuck" with an orphan product or technology -- even if it is attractive at first. (The culture here can be a bit risk-averse in places.) We also welcome open-source projects, and use them freely. Adopting Pharo would not be substantially different than our current widespread use of Linux, C/C++, Python, Lua, Tcl, SVN, Git, etc. There's definitely a place for it here. But very few know about it! I've attended a Tech Talk (and plan to join tomorrow's talk). And I'm aware of the consortium; I joined the Pharo Association myself as an individual. There's no reason why we wouldn't/couldn't do so as an academic organization, at some point (assuming my plans succeed). We have an unusual situation: JPL may be part of NASA (they own the buildings, the equipment, the property, fund the projects, etc.), but we are not civil servants -- we don't work for the federal government as do other NASA center staff. We're actually staff members of Caltech, under privileged long-term contract. So I can either be "a government employee" (via contract) or "an academic staff member", depending (usually on what kind of discount some business may be offering. ;^) So it may be easier as Caltech to have an academic association. Something also for the future... -t -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 25, 2019

[Pharo 8.0] Build #783: Improve-stability-of-Docking-bar-morph

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

There is a new Pharo build available! The status of the build #783 was: FAILURE. The Pull Request #4724 was integrated: "Improve-stability-of-Docking-bar-morph" Pull request url: https://github.com/pharo-project/pharo/pull/4724 Issue Url: https://github.com/pharo-project/pharo/issues/Improve Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 25, 2019

Re: [Pharo-dev] [Pharo-users] Pumping FFI documentation [WAS] FFI beginner question

by ducasse

Ok! Let us know how we can help. There is also the Pharo consortium: it is free for âacademixâ but is a nice way to show that we are working in a sound robust eco-âsystemâ. There is enough space for everyone willing to contribute. And I do not know if you saw some of our talks but Pharo is yours means that this is not a product and that people can get an impact. Stef > On 25 Sep 2019, at 20:23, Brainstorms <wild.ideas(a)gmail.com> wrote: > > I'll likely start working with Guillermo on the UFFI booklet. I also see the > 'by example' booklets as being /very/ important, as they give critical first > impressions to those new to the whole concept of Smalltalk. I want to > enroll others in Pharo, and that means I need good docs/web pages to direct > people to. > > There are documents needed for reference; to answer questions & guide style, > usage, conventions, understanding. But there are also documents needed to > enroll newcomers, get attention, provide that "hook"... Both are important. > You're aware of Pharo's "marketing needs" as well as anyone, I'm sure. > > So thanks for the generous offer. I'm thinking about starting here with an > interest group, along with some tools and demonstration projects (based > closely on the work we do) to get attention & interest. That should evolve > into training needs, and that's where I think the MOOC and remote lectures > would come into play. > > We are (also) a national R&D institute where software, automation, etc. > figures prominently. It's long past time that we have an awareness of Pharo > and tap into its advantages to improve the quality, reliability, & > productivity of our missions. This has been on my mind for some months now. > > -t > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Sept. 25, 2019

Re: [Pharo-dev] [Pharo-users] Pumping FFI documentation [WAS] FFI beginner question

by Brainstorms

I'll likely start working with Guillermo on the UFFI booklet. I also see the 'by example' booklets as being /very/ important, as they give critical first impressions to those new to the whole concept of Smalltalk. I want to enroll others in Pharo, and that means I need good docs/web pages to direct people to. There are documents needed for reference; to answer questions & guide style, usage, conventions, understanding. But there are also documents needed to enroll newcomers, get attention, provide that "hook"... Both are important. You're aware of Pharo's "marketing needs" as well as anyone, I'm sure. So thanks for the generous offer. I'm thinking about starting here with an interest group, along with some tools and demonstration projects (based closely on the work we do) to get attention & interest. That should evolve into training needs, and that's where I think the MOOC and remote lectures would come into play. We are (also) a national R&D institute where software, automation, etc. figures prominently. It's long past time that we have an awareness of Pharo and tap into its advantages to improve the quality, reliability, & productivity of our missions. This has been on my mind for some months now. -t -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 25, 2019

[Pharo 8.0] Build #782: 4704-reduce-direct-calls-of-debuggerMap-rangeForPCcontextIsActiveContext

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

There is a new Pharo build available! The status of the build #782 was: FAILURE. The Pull Request #4707 was integrated: "4704-reduce-direct-calls-of-debuggerMap-rangeForPCcontextIsActiveContext" Pull request url: https://github.com/pharo-project/pharo/pull/4707 Issue Url: https://github.com/pharo-project/pharo/issues/4704 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 25, 2019