- Pharo-dev - lists.pharo.org

[ Pharo 70 ] Build 83 PR 236 introduce-at-at-in-dictionary
by Stephane Ducasse Sept. 3, 2017

Sept. 3, 2017

https://github.com/pharo-project/pharo/pull/236 https://pharo.fogbugz.com/f/cases/20203/

2 1

About allDirectories vs. directories
by Stephane Ducasse Sept. 2, 2017

Sept. 2, 2017

Hi I have been hacking a little page generator based on pillar for the mooc table of contents and I got surprised by the behavior of allDirectories it returns all the subdirectories including itself This is strange and inconsistent with the API in Behavior X = one level allX = deep below withAllX = deep below including me. subclasses allSubclasses withAllSubclasses So now when we do a deep we have to remov the first or scan the result to remove the receiver. I found that not nice. May be I miss something obvious such as .. which would be a child and return the parent = the starting container. Stef

1 0

[ann] moldable editor - documenter and examples without pragma magic
by Tudor Girba Sept. 2, 2017

Sept. 2, 2017

Hi, When we announced the GT Documenter as an application for the moldable editor, one of the remarks was that GT Examples implementation relies too much on pragma magic. We are now happy to announce that this is no longer the case because Andrei did a great job and rebuilt examples without the need for static pragmas for specifying dependencies. So, now we can example dependencies simply through normal calls: emptyView <gtExample> ^ GtMondrian new twoNodes <gtExamples> view := self emptyView view nodes with: {1 . 2} ... and the engine can figure out the static dependencies. This means that examples can be used both as plain unary methods, and as replacement for tests. We think this should address the worry of examples being too heavy (the current implementation is ~350 lines). With a bit of extra effort, we also adapted GT Documenter to expand the example dependencies as seen below. This means that examples can now be used directly as units of documentation as well. We think this is significant. Cheers, The feenk team -- www.tudorgirba.com www.feenk.com "We are all great at making mistakes."

2 2

Re: [Pharo-dev] BOF at ESUG - How about a BOF on Gemstone development environments?
by Tim Mackinnon Sept. 1, 2017

Sept. 1, 2017

I'm envious as I couldn't make it to Esug - but I'd love to hear any conclusions/insights from that bof. Iceberg/git is such a transformative step that we need all the knowledge spread we can get. Tim Sent from my iPhone > On 1 Sep 2017, at 12:40, Reg Krock via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > <mime-attachment>

2 1

review pull request changes view
by Nicolai Hess Sept. 1, 2017

Sept. 1, 2017

When reviewing a pull request, I see this in the changes view: The tab title says "left working copy / right incoming update" but the code on the right side is what is current in my image [image: Inline-Bild 1] And I don't think "working copy" is the correct naming, as this view lets me diff changes within that history, so it may be that none of this code is actually in my "working copy", no ?

4 23

1st CfP: OOPS @ SAC 2018 - April 9 - 13, Pau, France
by Nick Papoylias Sept. 1, 2017

Sept. 1, 2017

************************************************** OOPS 2018 Call for Papers Object-Oriented Programming Languages and Systems http://oops.disi.unige.it/OOPS18 ************************************************** Technical Track at the 33rd ACM Symposium on Applied Computing, SAC 2018 https://www.sigapp.org/sac/sac2018/index.html April 9 - 13, 2018 Pau, France - Important Dates Submission of regular papers and SRC abstracts September 15, 2017 Paper and SRC notifications November 10, 2017 Paper and SRC camera-ready copies November 25, 2017 Author registration December 10, 2017 SAC 2018 April 9 - 13, 2018 - Track Chair Davide Ancona (davide.ancona(a)unige.it) DIBRIS, University of Genova, Italy - SAC 2018 For the past thirty two years, the ACM Symposium on Applied Computing (SAC) has been a primary gathering forum for applied computer scientists, computer engineers, software engineers, and application developers from around the world. SAC 2018 is sponsored by the ACM Special Interest Group on Applied Computing (SIGAPP) and is hosted by hosted by UniversitÃ© de Pau et des Pays de l'Adour (UPPA), Pau, France. - Call For Student Research Abstracts Graduate students seeking feedback from the scientific community on their research ideas are invited to submit original abstracts of their research work in areas of experimental computing and application development related to SAC 2018 Tracks. The Student Research Competition (SRC) Program is designed to provide graduate students the opportunity to meet and exchange ideas with researchers and practitioners in their areas of interest. - OOPS Track: Aims and Topics Object-oriented programming (OOP) has become the mainstream programming paradigm for developing complex software systems in most application domains. However, existing OO languages and platforms need to evolve to meet the continuous demand for new abstractions, features, and tools able to reduce the time, effort, and cost of creating object-oriented software systems, and improving their performance, quality and usability. To this aim, OOPS is seeking for research advances bringing benefits in all those typical aspects of software development, such as modeling, prototyping, design, implementation, concurrency and distribution, code generation, analysis, verification, testing, debugging, evaluation, deployment, maintenance, reuse, and software evolution and adaptation. The specific topics of interest for the OOPS track include, but are not limited to, the following: * Aspects and components * Code generation, and optimization, just-in-time compilation * Context-oriented programming * Databases and persistence * Distribution and concurrency * Dynamic and scripting languages * Evaluation * Feature Oriented Software Development and Programming * Formal verification * Internet of Things technology and programming * Integration with other paradigms * Interoperability, versioning and software evolution and adaptation * Language design and implementation * Modular and generic programming * Reflection, meta-programming * Runtime verification and monitoring * Safe, secure and dependable software * Static analysis * Testing and debugging * Type systems and type inference * Virtual machines OOPS offers a great opportunity to the OOP community to gain visibility, and to exploit the inter-disciplinary nature of SAC. - Submission Instructions Prospective papers should be submitted to the track in pdf format using the START submission system for regular and SRC papers available through the SAC 2018 home page. Submission of the same paper to multiple tracks is not allowed; all papers should represent original and previously unpublished works that are currently not under review in any conference or journal. Both basic and applied research papers are welcome. SAC 2018 will use double-blind reviewing; to facilitate this, author name(s) and institution(s) must be omitted, and references to authors' own related work should be in the third person. The format of the paper must adhere to the sig-alternate style (http://www.acm.org/sigs/publications/proceedings-templates) Full papers are limited to 8 pages, in camera-ready format, included in the registration fee. Authors have the option to include up to two (2) extra pages at additional fee of US$80 per page. Papers accepted as posters are limited to 3 pages, in camera-ready format, included in the registration fee. Authors have the option to include only one (1) extra page at additional fee of US$80. SRC abstracts are limited to 2 pages, in camera-ready format, included in the registration fee. No extra pages are allowed. Papers that fall short the above requirements are subjected to rejection. All papers must be submitted by September 15, 2017. For more information please visit the SAC 2018 home page. - Proceedings Accepted papers will be published by ACM in the annual conference proceedings. Accepted posters will be published as extended abstracts in the same proceedings. Paper registration is required, allowing the inclusion of the papers and posters in the conference proceedings. An author or a proxy attending SAC MUST present the paper. This is a requirement for all accepted papers, posters, and invited SRC submissions to be included in the ACM digital library. No-show of scheduled papers, posters, and student research abstracts will result in excluding them from the ACM digital library. Student registration is only intended to encourage student attendance and does not cover inclusion of papers/posters in the conference proceedings. Finally, following the tradition of the past OOPS editions (http://oops.disi.unige.it/special-issues) depending on the quality and the overall number of accepted papers, authors of selected papers will be invited to submit an extended version for a journal special issue ( http://oops.disi.unige.it/special-issues) after the conference.

1 0

Can not review pull request with iceberg
by Nicolai Hess Aug. 31, 2017

Aug. 31, 2017

Hi, I set up my fork and iceberg as it is described in https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to… now I try to review a pull request from the pharo-project repository. 1. iceberg asked for the github credientials (why ? I can view pull request on the webinterface without beeing looged in) 2. I unchecked the checkbox "'Do you want this credentials to be stored for future use?'" 3. after entering the user/password, it asked again for user and password when selecting one entry from the pull request list, the checkbox is again checked, so for every operation I have to uncheck the checkbox again and again. 4. the dialog for the credentials opens two times right after another, and I have to enter the user/password two times 5. now the iceberg pull request list is un-focus-able, and the main iceberg window too. Every mouse click on the iceberg window, just shows the world menu any ideas what went wrong? (this with pharo 7 on windows)

2 2

Pinning Objects in Pharo
by Torsten Bergmann Aug. 31, 2017

Aug. 31, 2017

As some of you are aware of Spur added memory pinning and in Pharo 6.1 (#60510) as well as Pharo 7 we currently have Object>>pin Object>>unpin Object>>isPinned and also Object>>setPinned:. Object pinning is explained by Eliot here [1]. I would propose two changes (at least for Pharo but ideally also for Squeak): 1. IMHO #setPinned: should be moved to a private protocol 2. Provide a #pinDuring: aBlock method like: pinDuring: aBlock [ self pin. aBlock value ] ensure: [ self unpin ] so we can ensure that a pinned object is unpinned after an operation. What do you think? Also I wonder why FFICallbackTests>>#testCqsortWithByteArray is sending #pin but not #unpin afterwards. Maybe that is the reason why there is a flag in this method that it is crashing on Windows. Bye T. [1] http://lists.squeakfoundation.org/pipermail/squeak-dev/2017-August/195129.h…

4 5

Bloc: Safe to Store SSH Passphrase in Pharo?
by Sean P. DeNigris Aug. 31, 2017

Aug. 31, 2017

https://github.com/pharo-vcs/iceberg/blob/master/README.md suggests to configure Iceberg with the "Use Custom SSH Keys" setting, part of which seems to include pasting one's SSH Key Passphrase into Pharo's settings. Is that a good idea (i.e. is that safe)? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

7 11

I disabled notifications from github
by Esteban Lorenzano Aug. 31, 2017

Aug. 31, 2017

they were far too much. I will comeback when I find a solution for the only two cases I would like to inform to this list: 1) there is a new Pull Request (so people can go and take a look) 2) there is a new merge into development (so people know the change has been integrated) Esteban

2 1