- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] PharoMinimal ?

by Torsten Bergmann

Cool, thanks! Am 13.10.2017 um 08:32 schrieb Stephane Ducasse: > It is in the roadmap. > > > > On Tue, Oct 10, 2017 at 11:49 PM, Torsten Bergmann <astares(a)gmx.de> wrote: >>> If you will tell me what exactly you need we can make it work together as >>> in case of PharoLambda. >> Even when this offer from Pavel was for Sven I would like to ask: >> What about a minimal "TelePharo ready image" that one can remotely connect >> to and then debug, enhance, ... >> >> Thanks >> T. >>

Oct. 13, 2017

[Pharo 7.0-dev] Build #191: 20180-Deprecate-fractionsoffsets-and-fractions-

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

There is a new Pharo build available! The status of the build #191 was: SUCCESS. The Pull Request #318 was integrated: "20180-Deprecate-fractionsoffsets-and-fractions-" Pull request url: https://github.com/pharo-project/pharo/pull/318 Issue Url: https://pharo.fogbugz.com/f/cases/20180 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 13, 2017

Re: [Pharo-dev] PharoMinimal ?

by Stephane Ducasse

It is in the roadmap. On Tue, Oct 10, 2017 at 11:49 PM, Torsten Bergmann <astares(a)gmx.de> wrote: >>If you will tell me what exactly you need we can make it work together as >> in case of PharoLambda. > > Even when this offer from Pavel was for Sven I would like to ask: > What about a minimal "TelePharo ready image" that one can remotely connect > to and then debug, enhance, ... > > Thanks > T. >

Oct. 13, 2017

[Pharo 7.0-dev] Build #190: 20504-Integrate-Iceberg-061

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

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

Oct. 13, 2017

[Pharo 7.0-dev] Build #189: 20535 Cleanup SmartSuggestions-Tests and Shout-Tests package

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

There is a new Pharo build available! The status of the build #189 was: SUCCESS. The Pull Request #358 was integrated: "20535 Cleanup SmartSuggestions-Tests and Shout-Tests package" Pull request url: https://github.com/pharo-project/pharo/pull/358 Issue Url: https://pharo.fogbugz.com/f/cases/20535 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 13, 2017

[Pharo 7.0-dev] Build #188: 20534 Cleanup Graphics-Tests package

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

There is a new Pharo build available! The status of the build #188 was: SUCCESS. The Pull Request #357 was integrated: "20534 Cleanup Graphics-Tests package" Pull request url: https://github.com/pharo-project/pharo/pull/357 Issue Url: https://pharo.fogbugz.com/f/cases/20534 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 13, 2017

Re: [Pharo-dev] Let's prepare for Google Code-In 2017 with Pharo Consortium

by Jigyasa Grover

Hello Pharo-ers ! On behalf of the community, I would like to thank each one of you for their significant contribution in the recently concluded *Google Summer of Code 2017* with *Pharo Consortium*. We aspire to take-off on a long flight after this successful stint. In this spirit, I proposed at ESUG 2017 that we take part in the upcoming *Google Code-In 2017*. GCI is a contest to introduce pre-university students (ages 13-17) to open source software development. Because Google Code-in is often the first experience many students have with open source, the contest is designed to make it easy for students to jump right in with /bite-sized tasks/ (3 to 5 days) having categorised as: Code, Documentation/Training, Outreach/Research, Quality Assurance, or User Interface. Students search for a task from the list created by us that interests them and claim it. They have at least three days to complete it. The student works on the task, getting guidance from mentors, if needed. Once the student is ready, they submit their work for review through the contest website. Mentors from the organisation evaluate the work, provide feedback, and if it's complete, accept it so that student can claim a new task. Otherwise, specific feedback is provided, and the student goes back to improving it. Participants who complete at least 1 task get a digital certificate. Participants who complete 3 or more tasks receive a t-shirt too. At the end of the contest, each organisation chooses five finalists to receive limited edition Google Code-in hoodies. Two finalists from each organisation get to be the grand prize winners and go on a trip to Google Headquarters in California ! The contest begins for students on November 28, 2017 at 09:00 (PST). *With organisation applications closing on October 24, 2017*, we need to be well prepared for this seasonâs application with a hope to get selected. As an open source evangelist and a Pharo developer, I would like to invite all the experienced members to be a part of the "GCI with Pharo Consortium" Team and mentor students. To get added to the âprivate repositoryâ (we need to keep prospective students away from the task list before the program begins ð ) where you can put in your tasks/suggestions kindly EMail me or any of the previously added mentor. Looking forward to an appreciable representation from the Pharo community. Best regards Jigyasa Grover Pharo Consortium Org Admin, Google Summer of Code 2017 [hidden email] Link to know more about GCI: https://codein.withgoogle.com/archive/ <https://codein.withgoogle.com/archive/ > Link to sample tasks: https://developers.google.com/open-source/gci/resources/example-tasks <https://developers.google.com/open-source/gci/resources/example-tasks> Link to FAQs: https://developers.google.com/open-source/gci/faq <https://developers.google.com/open-source/gci/faq > Link to contest rules: https://developers.google.com/open-source/gci/resources/contest-rules <https://developers.google.com/open-source/gci/resources/contest-rules> Link to GCI presentation for outreach: https://developers.google.com/open-source/gci/resources/downloads/Google-Co… <https://developers.google.com/open-source/gci/resources/downloads/Google-Co…> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 12, 2017

Re: [Pharo-dev] Let's prepare for Google Code-In 2017 with Pharo Consortium

by Jigyasa Grover

Hello Pharo-ers ! On behalf of the community, I would like to thank each one of you for their significant contribution in the recently concluded *Google Summer of Code 2017* with *Pharo Consortium*. We aspire to take-off on a long flight after this successful stint. In this spirit, I proposed at ESUG 2017 that we take part in the upcoming *Google Code-In 2017*. GCI is a contest to introduce pre-university students (ages 13-17) to open source software development. Because Google Code-in is often the first experience many students have with open source, the contest is designed to make it easy for students to jump right in with /bite-sized tasks/ (3 to 5 days) having categorised as: Code, Documentation/Training, Outreach/Research, Quality Assurance, or User Interface. Students search for a task from the list created by us that interests them and claim it. They have at least three days to complete it. The student works on the task, getting guidance from mentors, if needed. Once the student is ready, they submit their work for review through the contest website. Mentors from the organisation evaluate the work, provide feedback, and if it's complete, accept it so that student can claim a new task. Otherwise, specific feedback is provided, and the student goes back to improving it. Participants who complete at least 1 task get a digital certificate. Participants who complete 3 or more tasks receive a t-shirt too. At the end of the contest, each organisation chooses five finalists to receive limited edition Google Code-in hoodies. Two finalists from each organisation get to be the grand prize winners and go on a trip to Google Headquarters in California ! The contest begins for students on November 28, 2017 at 09:00 (PST). With organisation applications closing on October 24, 2017, we need to be well prepared for this seasonâs application with a hope to get selected. As an open source evangelist and a Pharo developer, I would like to invite all the experienced members to be a part of the "GCI with Pharo Consortium" Team and mentor students. To get added to the âprivate repositoryâ (we need to keep prospective students away from the task list before the program begins ð ) where you can put in your tasks/suggestions kindly EMail me or any of the previously added mentor. Looking forward to an appreciable representation from the Pharo community. Best regards Jigyasa Grover Pharo Consortium Org Admin, Google Summer of Code 2017 [hidden email] Link to know more about GCI: https://codein.withgoogle.com/archive/ <https://codein.withgoogle.com/archive/ > Link to sample tasks: https://developers.google.com/open-source/gci/resources/example-tasks <https://developers.google.com/open-source/gci/resources/example-tasks> Link to FAQs: https://developers.google.com/open-source/gci/faq <https://developers.google.com/open-source/gci/faq > Link to contest rules: https://developers.google.com/open-source/gci/resources/contest-rules <https://developers.google.com/open-source/gci/resources/contest-rules> Link to GCI presentation for outreach: https://developers.google.com/open-source/gci/resources/downloads/Google-Co… <https://developers.google.com/open-source/gci/resources/downloads/Google-Co…> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 12, 2017

Re: [Pharo-dev] [Spec] ComposableModel renamed to ComposablePresenter

by Stephane Ducasse

Yes me too and listModel model value killed me On Thu, Oct 12, 2017 at 2:57 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Pavel Krivanek-3 wrote >> To be sure that most of the current code which uses the old name will >> work, >> we created for every renamed class a subclass with the old name. These >> subclasses are moved (mostly) into Spec-Deprecated package. > > Ah, nice trick. Thanks for easing the transition. > > > Pavel Krivanek-3 wrote >> it is necessary to make the Spec code less confusing. > > Sounds good. I often needed a mental pause to translate "model" from "domain > model" to "something modelling a UI on the domain model". > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Oct. 12, 2017

Re: [Pharo-dev] XPath chapter...

by Stephane Ducasse

On Wed, Oct 11, 2017 at 10:43 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > Dont worry Stef you are not alone, I may no longer use Pharo as much I used > to but I will keep stalking you :D > So I have not quit from adding to the pharo documentation. You can at least > expect some video tutorials, minor updated to PBE and minor updates to Pharo > Wiki. thanks this is great > Of course I agree we need more people on this, if every pharo users jusr > dedicated 10 minutes per day on documentations we would have a mind blowing > documentation in quality and quanity. exactly. > 10 minutes is all it takes to update a page of documentation , 100 people, > 100 pages per day. 36.500 pages per year and our documentation needing > updating is not nowhere near this number > > OR > > 10 minutes to write 100 words of documentation (average writting speed is 40 > WPM but I dropped this down to 10 WPM to include research, testing, taking > pictures , general foramt etc) , thats about 1/3rd of a page . 100 people. > 30 pages per day. 10.950 pages per year. so that means with just 100 people > contributing 10 minutes of their time per day we could release around 20 > NEW books per year !!!! > > I am sure Pharo has more than 100 users ;) :) > > On Wed, Oct 11, 2017 at 9:13 AM monty <monty2(a)programmer.net> wrote: >> >> Great effort. The guide is concise and beginner friendly. I emailed you a >> git commit patch you can apply with `git am` (I don't use github) that fixes >> some things and expands on others. >> >> And for the record, I'm not "Monty Kamath" and I don't know him. >> >> > Sent: Sunday, September 24, 2017 at 1:03 PM >> > From: "Stephane Ducasse" <stepharo.self(a)gmail.com> >> > To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >> > Subject: [Pharo-dev] XPath chapter... >> > >> > Hi >> > >> > I'm fully convinced that we can have the best language if we do not >> > let people find their way super easily to do what they want to do we >> > will fail. >> > Documentation is KEY and I feel a bit alone. >> > >> > Since I always wanted to learn XPath I started to write a chapter on >> > XPath. I hope that I did not write too many mistakes. >> > >> > Pull requests are welcome here >> > https://github.com/SquareBracketAssociates/Booklet-Scraping >> > >> > I would love to have one booklet on SAX and DOM handling. >> > >> > >> > Stef >> > >> >

Oct. 12, 2017