October 2017 - Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #192: 20528-Use-Spec-presenters-in-internal-projects
by ci-pharo-ci-jenkins2＠inria.fr Oct. 13, 2017

Oct. 13, 2017

There is a new Pharo build available! The status of the build #192 was: SUCCESS. The Pull Request #350 was integrated: "20528-Use-Spec-presenters-in-internal-projects" Pull request url: https://github.com/pharo-project/pharo/pull/350 Issue Url: https://pharo.fogbugz.com/f/cases/20528 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #191: 20180-Deprecate-fractionsoffsets-and-fractions-
by ci-pharo-ci-jenkins2＠inria.fr Oct. 13, 2017

Oct. 13, 2017

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…

1 0

[Pharo 7.0-dev] Build #190: 20504-Integrate-Iceberg-061
by ci-pharo-ci-jenkins2＠inria.fr Oct. 13, 2017

Oct. 13, 2017

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…

1 0

[Pharo 7.0-dev] Build #189: 20535 Cleanup SmartSuggestions-Tests and Shout-Tests package
by ci-pharo-ci-jenkins2＠inria.fr Oct. 13, 2017

Oct. 13, 2017

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…

1 0

[Pharo 7.0-dev] Build #188: 20534 Cleanup Graphics-Tests package
by ci-pharo-ci-jenkins2＠inria.fr Oct. 13, 2017

Oct. 13, 2017

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…

1 0

Let's prepare for Google Code-In 2017 with Pharo Consortium
by Jigyasa Grover Oct. 12, 2017

Oct. 12, 2017

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 runs for about 6-8 weeks in December & January generally. With organisation applications beginning in October/November, 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 grover.jigyasa1(a)gmail.com 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

1 2

[Spec] ComposableModel renamed to ComposablePresenter
by Pavel Krivanek Oct. 12, 2017

Oct. 12, 2017

Hello, important change for the Spec users. In "The Spec UI Framework" book you can read: Considering the construction and orchestration of the different widgets in > a user interface, Spec is inspired by the Model-View-Presenter pattern. The > model that is defined in Spec corresponds to a presenter in the MVP triad. > Note that because of this, future versions of Spec may rename the > ComposableModel into ComposablePresenter for naming consistency. This change was done in the Pharo 7 development images by this pull request: https://github.com/pharo-project/pharo/pull/344 All other Spec presenters that use suffix -Model were renamed too to end with -Presenter suffix. This is the complete list: AbstractFormButtonModel AbstractWidgetModel ButtonModel CheckBoxModel ComposableModel ContainerModel DateModel DialogWindowModel DiffModel DropListModel DynamicComposableModel FastTableModel IconListModel ImageModel LabelModel ListModel ListSelectionModel MenuGroupModel MenuItemModel MenuModel MultiColumnListModel PickListModel RadioButtonGroupModel RadioButtonModel SliderModel TabManagerModel TabModel TableContainerModel TestingComposableModel TextInputFieldModel TextModel TickingWindowModel TransferModel TreeColumnModel TreeModel TreeNodeModel WindowModel WorldModel 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. Currently such deprecation does not make any action so no exception is generated nor no code is rewritten. We will add such mechanisms in future as soon as most users and documentation will adopt his change. This deprecation can cause problems in two cases: you use code like 'isKindOf:' or if your package adds extension methods to the basic Spec classes. To rename these classes was only the first step. We need to rename some Spec tests classes and mainly touch methods like *instantiateModels:* and later make them deprecated. We are sorry for troubles that these changes can cause but it is necessary to make the Spec code less confusing. Cheers, -- Pavel

3 2

[Pharo 7.0-dev] Build #187: 20524-ExecuteTree-method-comment
by ci-pharo-ci-jenkins2＠inria.fr Oct. 12, 2017

Oct. 12, 2017

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

1 0

[Pharo 7.0-dev] Build #186: 20509 MD5Test, SHA1Test, SHA256Test should be moved to a new package "System-Hashing-Tests"
by ci-pharo-ci-jenkins2＠inria.fr Oct. 12, 2017

Oct. 12, 2017

There is a new Pharo build available! The status of the build #186 was: SUCCESS. The Pull Request #345 was integrated: "20509 MD5Test, SHA1Test, SHA256Test should be moved to a new package "System-Hashing-Tests"" Pull request url: https://github.com/pharo-project/pharo/pull/345 Issue Url: https://pharo.fogbugz.com/f/cases/20509 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #135: 20434-use-Ring2-during-the-bootstrap
by ci-pharo-ci-jenkins2＠inria.fr Oct. 12, 2017

Oct. 12, 2017

There is a new Pharo build available! The status of the build #135 was: SUCCESS. The Pull Request #294 was integrated: "20434-use-Ring2-during-the-bootstrap" Pull request url: https://github.com/pharo-project/pharo/pull/294 Issue Url: https://pharo.fogbugz.com/f/cases/20434 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

5 5