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

Error in ByteArray>>booleanAt:
by Raffaello Giulietti June 23, 2017

June 23, 2017

Hi, the current (Pharo 6) code reads ^(self integerAt: byteOffset size: 1 signed: false) == true so it always returns false, as no integer is identical to true. Instead, it should read ^(self integerAt: byteOffset size: 1 signed: false) ~= 0 implementing the usual convention that 0 maps to false and every other value maps to true. Greetings Raffaello

4 3

Ideas for TechTalks wanted
by Marcus Denker June 23, 2017

June 23, 2017

Hi! We need to setup the dates and topics for the next tech talks, they are always the last tuesday of the month. We have two kinds: -> presentation of a demo with youtube live, then Q&A (one person talks) -> More open discussion just on Discord with Audio Chat about a topic (one person started and guides a discussion) We need topic ideas and people who take the lead role for the second part of the year (August to December). Marcus

1 0

Techtalk June 27 postponed to July 25
by Marcus Denker June 23, 2017

June 23, 2017

Hi, As too many people can not take part next week Tuesday, we decided to move the Pharo6/Pharo7 roundtable to July 25. https://association.pharo.org/event-2492469 <https://association.pharo.org/event-2492469> Marcus

1 0

Iceberg diff colours seem reversed?
by Tim Mackinnon June 22, 2017

June 22, 2017

Hi Guys - when you launch the Synchronize window in iceberg - is it me, or are the colour highlights backwards (and possibly the ordering of the panes)? If the left pane is my working copy, and I've added some code to a method - why does it appear in red on the left (which typically means deleted?). I notice that in IntelliJ (and other tools) your working changes are typically on the right and things you add are in Green on that right hand side. I think that ordering and colour coding make more sense - from -> to, and red is deleted, green is added. Of course I can live with the different pane ordering, but I think the colours might be wrong? Tim

3 4

Pharo Monthly Newsletter June
by Marcus Denker June 21, 2017

June 21, 2017

Hi, The Pharo Monthly Newsletter for June will be send out Friday. You can subscribe here to get it delivered by email: http://us11.campaign-archive1.com/home/?u=6f667565c2569234585a7be77&id=0486… <http://us11.campaign-archive1.com/home/?u=6f667565c2569234585a7be77&id=0486…> If someone has ideas for topics for the next newsletters, please send them to me. Marcus

1 0

How can I save changes on memory ?
by JÃ©rÃ©mie Regnault June 21, 2017

June 21, 2017

Hi, I would like to know how to save modifications (e.g creating a class/method ) in the memory. Have a nice day, -- JÃ©rÃ©mie Regnault

3 2

Re: [Pharo-dev] GitHub survey on open source projects
by csrabak＠bol.com.br June 21, 2017

June 21, 2017

2 1

GitHub survey on open source projects
by Eliot Miranda June 20, 2017

June 20, 2017

Not sure how much this reflects our communities but this is interesting. GitHub Survey: Open Source Is Popular, Plagued by Poor Docs and Rude People https://adtmag.com/articles/2017/06/05/open-source-survey.aspx _,,,^..^,,,_

4 4

Esteban clone, Pavel clone, Clement clone, Guillermo clone....
by Stephane Ducasse June 20, 2017

June 20, 2017

Dear Pharoers there are many things that we would like to achieve to offer you a much better system but we cannot clone ourselves. Please let us know if you want to participate building better tools around for example Iceberg. Stef

2 4

Esteban's ChangeLog week of 12 June 2017
by estebanlm＠gmail.com June 20, 2017

June 20, 2017

Hello! This is my weekly ChangeLog, from 12 June 2017 to 18 June 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=12/6/2017&to=18/6/2017 ChangeLog ========= 15 June 2017: ------------- * I finished an iteration for allowing cherry-pick into [iceberg](http://github.com/pharo-vcs/iceberg). Now, I just need to make it work on 64bits and we will be ready-to-go for releasing it :) 13 June 2017: ------------- * Still "iceberging", I fixed an annoying bug when browsing diff with parent (in all screens that have it), who was trowing a DNU because of course, first commits do not have a parent to compare with. * I've been working on iceberg 0.5. It will incorporate some needed features (to make it appropriate to work on pharo itself, and better for users). This was also my work last week, but I forget to announce it here ;) So far, I added following features: === Better diff handling It was very naive because it was comparing always all present packages which does not scales on large repositories. Now, I implemented a double dispatch that works in different scenarios: * commit -> commit: It relies in libgit2 to take the list of changed packages. * commit -> branch: it takes last commit on branch on continues as commit->commit scenario * loaded code -> commit: this is the most complicated scenario. It compares what is in image with what is in commit to take a correct diff. With this, now diffs are performant in all cases (bah, if you have a commit that changes 300 packages, you will suffer anyway, but I would argue that is not a very good codign practice) Also with this you will finally be able to add not-dirty packages to your repo and commit them :) === Branch sync with disk copy I had a discussion with author of Iceberg (Nico) on this: originally he weanted to treat loaded code in the image as a got working-copy itself, so he was taking the information of the branch and keepong it. Problem with this is, if you change the repository branch (in command line or another image) and then go back to your current image, you do not have any feedback... and that is severely confusing. So now I'm just taking the information from git repository. That means you can have differences between what you loaded and your current branch, but that's, IMO, perfectly reasonable (you can always switch back or merge or whatever you need to do) === Other * Minor cleanups * Other bugfixes cheers! Esteban

5 5