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

[ANN] Pharo Sprint June 30

by Marcus Denker

Hi! Next Friday, June 30 will be the next Pharo Sprint! It will start 10:00am. (Local Time Paris). For more infos, see: https://association.pharo.org/event-2492492 Marcus

June 23, 2017

Ideas for TechTalks wanted

by Marcus Denker

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

June 23, 2017

Techtalk June 27 postponed to July 25

by Marcus Denker

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

June 23, 2017

Re: [Pharo-dev] Iceberg diff colours seem reversed?

by Yuriy Tymchuk

I have to look into it, because the colors were reversed 100% and then I swapped them. And now I donât know (need some sleep, Iâll look tomorrow) Uko > On 22 Jun 2017, at 18:18, Tim Mackinnon <tim(a)testit.works> wrote: > > Itâs worth saying that the diff view on Epicea appears to be correct assuming left is previous and right is new (so I think it also shows the panes the other way around like I expected). > > Tim > >> On 22 Jun 2017, at 17:03, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >> >> I think the left to right or right to left is probably a very opinionated thing (and I think Araxis, another tool Iâve used does it the other way around). >> >> However the colour coding is something that should properly communicate what is going on - and Iâm curious if anyone else has noticed it seems to be wrong (it sounds like for you its definitely confusing). >> >> I think there are known bugs in iceberg (not sure how much on the diff view - I also noticed that class comments donât seem to appear in the diff and I also see spurious method categorisation differences as well). >> >> Tim >> >>> On 22 Jun 2017, at 06:51, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: >>> >>> I didn't look at the iceberg diff right now. But I can say whenever I see a diff view in pharo it is so confusing I never know what I see. In the changes window I alwas switch from diff to source to see at least what I have now. Maybe a general problem how to put chronological change. And maybe for left-to-right readers to only way is older left - newer right >>> >>> Norbert >>> >>> Am 22.06.2017 um 03:40 schrieb Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>>: >>> >>>> 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 >> >

June 22, 2017

Re: [Pharo-dev] Error in ByteArray>>booleanAt:

by Sven Van Caekenberghe

> On 22 Jun 2017, at 17:39, Raffaello Giulietti <raffaello.giulietti(a)lifeware.ch> wrote: > > 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 Good catch, probably a typo. IMO, there should have been unit tests to validate such code.

June 22, 2017

Re: [Pharo-dev] Iceberg diff colours seem reversed?

by Tim Mackinnon

Itâs worth saying that the diff view on Epicea appears to be correct assuming left is previous and right is new (so I think it also shows the panes the other way around like I expected). Tim > On 22 Jun 2017, at 17:03, Tim Mackinnon <tim(a)testit.works> wrote: > > I think the left to right or right to left is probably a very opinionated thing (and I think Araxis, another tool Iâve used does it the other way around). > > However the colour coding is something that should properly communicate what is going on - and Iâm curious if anyone else has noticed it seems to be wrong (it sounds like for you its definitely confusing). > > I think there are known bugs in iceberg (not sure how much on the diff view - I also noticed that class comments donât seem to appear in the diff and I also see spurious method categorisation differences as well). > > Tim > >> On 22 Jun 2017, at 06:51, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: >> >> I didn't look at the iceberg diff right now. But I can say whenever I see a diff view in pharo it is so confusing I never know what I see. In the changes window I alwas switch from diff to source to see at least what I have now. Maybe a general problem how to put chronological change. And maybe for left-to-right readers to only way is older left - newer right >> >> Norbert >> >> Am 22.06.2017 um 03:40 schrieb Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>>: >> >>> 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 >

June 22, 2017

Re: [Pharo-dev] Iceberg diff colours seem reversed?

by Tim Mackinnon

I think the left to right or right to left is probably a very opinionated thing (and I think Araxis, another tool Iâve used does it the other way around). However the colour coding is something that should properly communicate what is going on - and Iâm curious if anyone else has noticed it seems to be wrong (it sounds like for you its definitely confusing). I think there are known bugs in iceberg (not sure how much on the diff view - I also noticed that class comments donât seem to appear in the diff and I also see spurious method categorisation differences as well). Tim > On 22 Jun 2017, at 06:51, Norbert Hartl <norbert(a)hartl.name> wrote: > > I didn't look at the iceberg diff right now. But I can say whenever I see a diff view in pharo it is so confusing I never know what I see. In the changes window I alwas switch from diff to source to see at least what I have now. Maybe a general problem how to put chronological change. And maybe for left-to-right readers to only way is older left - newer right > > Norbert > > Am 22.06.2017 um 03:40 schrieb Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>>: > >> 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

June 22, 2017

Error in ByteArray>>booleanAt:

by Raffaello Giulietti

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

June 22, 2017

Re: [Pharo-dev] vested interest in PharoJS?

by askoh

There seem to be some interesting work with SqueakJS by Craig Latta. https://thiscontext.com/ I hope Smalltalk of all dialects can get together to develop a killer web development environment. All the best, Aik-Siong Koh -- View this message in context: http://forum.world.st/Re-vested-interest-in-PharoJS-tp4952248p4952307.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 22, 2017

Re: [Pharo-dev] [Pharo-users] vested interest in PharoJS?

by Norbert Hartl

> Am 22.06.2017 um 13:57 schrieb Siemen Baader <siemenbaader(a)gmail.com>: > > Very cool, Norbert. I have been watching what you are doing at 2denker and thought you might be interested ;) > > What is holding you back - do you need more from PharoJS before starting to use it commercially, or are you waiting for a (paid) project before you can start? > What is keeping me? A project and the feasibility. The amber project we could do because the project was more of a research project so I said "why not". For anything serious you need to check if it is feasible to use. And my trials with PharoJS were only little so I don't have the feeling, yet, if it is a huge benefit using it. But I feel a huge potential in it so it is on my list of things I wanna try but not on top. Norbert > -- Siemen > > On Thu, Jun 22, 2017 at 1:08 PM, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: > I thought I responded already. We are interested in pharoJS. We developed stuff with amber but stopped using it. We have one app in the app store with ionic and amber and I'd like to do another one with pharoJS. Additionally I think that combining pharoJS with electron could be a nice thing to have in order to create desktop apps. And finally I was shortly researching native callouts from javascript with javascript core on ios and it seems you can do pharo code, transpile to javascript that calls javascript functions which are OS-native functions. > > Norbert > > > Am 14.06.2017 um 11:46 schrieb Siemen Baader <siemenbaader(a)gmail.com <mailto:siemenbaader@gmail.com>>: > > > > Hi all, > > > > Is anyone else interested in PharoJS and making it mature for their own commercial mobile and single page web app (and node.js) development? > > > > I think it has a huge potential because it brings the browser runtime and many libraries and online services from the JS world to us Smalltalkers while letting us keep our agile development and good CS practices. But it does not yet have the necessary features and documentation to work smoothly. > > > > -- Siemen > >

June 22, 2017