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

Re: [Pharo-dev] Did the selection in Playground or rubric change?

by Tim Mackinnon

Actually I played around with all of that stuff and got it working well - but I got scared off with how to contribute with the new process etc. I can look again when the Xmas holidays kick in, and see if my small changes work in a 7.x image - I found that I could get the AST to work, but I had to add a little heuristic to it and if I found nothing and there was a selection then it worked the old way. Tim > On 12 Dec 2017, at 13:06, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Yes, I have it already on my list of things to fixâ¦ (not issue tracker entry yet, will add one). > > Marcus > >> On 12 Dec 2017, at 13:52, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> just type >> >> margins: Put the cursor here and press command + M or command + N >> in the past >> margins: was selected and used. >> >> What you see is that we cannot rely on the AST. >> Now selecting items is boring. >> >> Stef >> >> On Tue, Dec 12, 2017 at 1:47 PM, Pavel Krivanek >> <pavel.krivanek(a)gmail.com> wrote: >>> Hi, >>> >>> Andrew improved that so it now works on AST and provides better results. If >>> you have some code where it does not work, please try to describe the >>> particular case so we can fix it. >>> >>> -- Pavel >>> >>> 2017-12-12 13:31 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >>>> >>>> Hi >>>> >>>> usually in previous version we could put the cursor on the line and >>>> get senders and implementors without having to select the code. >>>> Now this super cool features does not work anymore. >>>> >>>> Is it only my image? >>>> >>>> Stef >>>> >>> >> > >

Dec. 13, 2017

Re: [Pharo-dev] Epicea feedback - save points

by Ben Coman

Hi Stef, I think that is incorrect. Its easy to be certain... 1. Open Epicea 2. Save and continue 3. Open Epicea and observe there is no difference cheers -ben On 13 December 2017 at 17:59, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > I think that epicea save point are the list elements on the left. > > > On Wed, Dec 13, 2017 at 9:05 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > > Same for me. I thought the last save point would be the last session in > the list but I donât think that is really true. So Iâm confused by Epicea, > too. > > > > Norbert > > > >> Am 13.12.2017 um 08:27 schrieb Ben Coman <btc(a)openinworld.com>: > >> > >> When I'm in need Epicea, the common scenario is that I've working in > the same session of an Image most of the day, or even days, and I've done > something stupid to lock up the UI, and its only been an hour since my last > save point (force of habit). When I review Epicea, "Filter > Show latest > changes" its still ahrd to determine which changes I'm missing. What I've > just realised is I miss the visibility of the Save Point in the old changes > system. I'd find it really useful for the save points to be show in the > changes list, and also a filter I'd find really useful is "Shows latest > changes since last save". > >> > >> > >> cheers -ben > > > >

Dec. 13, 2017

[Website] Updated Linux download instructions

by Marcus Denker

Hi, I have updated the download instruction with the infos from https://pharo.fogbugz.com/f/cases/20799/Update-Linux-Download-instructions Here are the two pages: https://pharo.org/gnu-linux-installation-64 https://pharo.org/gnu-linux-installation <https://pharo.org/gnu-linux-installation> for the 32 bit version I opted to list the package based installation first as the zip file is quite complex (requiring manual setup). TODO - add a pointe to get.pharo.org <http://get.pharo.org/> - add two to actually start Pharo for all cases. - Check https://pharo.fogbugz.com/f/cases/20147/ <https://pharo.fogbugz.com/f/cases/20147/> - Check if some linux infos from http://pharo.org/download <http://pharo.org/download> should not be better moved to the linux page. Marcus

Dec. 13, 2017

Re: [Pharo-dev] Moving from mc to tonel?

by stephan

On 05-12-17 08:59, Peter UhnÃ¡k wrote: > > In my case, it turned out to be a non-UTF8 encoded character in one > of the commit messages. > > I've ran into this problem in a sister project (tonel-migration), and do > not have a proper resolution yet. I was forcing everything to be > unicode, so I need a better way to read and write encoded strings. :< To be exact, exactly none of the older commits will be UTF8 encoded. For most it doesn't matter as they are ASCII, but if we want to have a change of converting older french or german code (or japanese), we need support for what was done with WideString. That probably needs a look in the squeak mailing list archives. Stephan

Dec. 13, 2017

Re: [Pharo-dev] spurious characters in class comments

by Stephane Ducasse

Yes I saw that too and this is probably an iceberg glitch or revealing a copy paste. On Wed, Dec 13, 2017 at 8:10 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > IMHO this would be the case if the sourde code is written in utf-8 but read > in latin1. > > Norbert > > Am 12.12.2017 um 23:41 schrieb Nicolas Cellier > <nicolas.cellier.aka.nice(a)gmail.com>: > > Take a look at Dictionary.class.st for example > > https://github.com/pharo-project/pharo/blob/bc8b9658958f4464189cf3e7fffd8c9… > > on line 10: > > IÃÆÃÆÃâÃâÃÆÃâÃâÃ am use when we need a collection of objects which I can > access with a key. For example if you associate some words with a > definition, the word will be the key and the definition will be the value. > Both of them can be any kind of objects. > > At each commit, the number of odd characters increases...

Dec. 13, 2017

Re: [Pharo-dev] odd behaviour dragging method between protocols

by Stephane Ducasse

Same here. It is a bug. Now I would like to deprecate Nautilus and use Calypso but but but we need to make sure that documentation is better and that we can have a spec based calypso because we do not want to rewrite everything again with bloc. stef On Wed, Dec 13, 2017 at 8:32 AM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > Happened to me too. > I think. I sometimes thought hey where is that method gone, couldn't > remember I deleted it. > > Am 13.12.2017 03:42 schrieb "Ben Coman" <btc(a)openinworld.com>: > > > I could just be having a brain freeze, but just sharing in case > anyone else is similarly going mad... > a few times recently in Nautilus I've dragged a method from the fourth pane > and dropped it on a protocol in the third pane and the method disappeared > from the system. Luckily its easily recovered from Tools > Code Changes, > where it shows as deleted. But its weird that a delete could be triggered > from the action I (thought I) performed. > > I've yet to detect a pattern. Unfortunately its kind of > blink-and-you-miss-it. > Its not until a second later when selecting the target protocol > that the behaviour becomes apparent. > > This is in 60527-64, Unix built on Jul 20 2017 20:40:36 Compiler: 4.6.3 > > cheers -ben > >

Dec. 13, 2017

Re: [Pharo-dev] Epicea feedback - save points

by Stephane Ducasse

I think that epicea save point are the list elements on the left. On Wed, Dec 13, 2017 at 9:05 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > Same for me. I thought the last save point would be the last session in the list but I donât think that is really true. So Iâm confused by Epicea, too. > > Norbert > >> Am 13.12.2017 um 08:27 schrieb Ben Coman <btc(a)openinworld.com>: >> >> When I'm in need Epicea, the common scenario is that I've working in the same session of an Image most of the day, or even days, and I've done something stupid to lock up the UI, and its only been an hour since my last save point (force of habit). When I review Epicea, "Filter > Show latest changes" its still ahrd to determine which changes I'm missing. What I've just realised is I miss the visibility of the Save Point in the old changes system. I'd find it really useful for the save points to be show in the changes list, and also a filter I'd find really useful is "Shows latest changes since last save". >> >> >> cheers -ben >

Dec. 13, 2017

About a shared trello board

by Stephane Ducasse

Hi I'm thinking that we are not good at communicating and coordinating effort I would like start a (read only) and welcome contributions on demand trello board so that we know each others on what parts of pharo we are currently working and what are the next steps. Does it make sense for you guys? Stef

Dec. 13, 2017

Re: [Pharo-dev] Epicea feedback - save points

by Norbert Hartl

Same for me. I thought the last save point would be the last session in the list but I donât think that is really true. So Iâm confused by Epicea, too. Norbert > Am 13.12.2017 um 08:27 schrieb Ben Coman <btc(a)openinworld.com>: > > When I'm in need Epicea, the common scenario is that I've working in the same session of an Image most of the day, or even days, and I've done something stupid to lock up the UI, and its only been an hour since my last save point (force of habit). When I review Epicea, "Filter > Show latest changes" its still ahrd to determine which changes I'm missing. What I've just realised is I miss the visibility of the Save Point in the old changes system. I'd find it really useful for the save points to be show in the changes list, and also a filter I'd find really useful is "Shows latest changes since last save". > > > cheers -ben

Dec. 13, 2017

Re: [Pharo-dev] odd behaviour dragging method between protocols

by Nicolai Hess

Happened to me too. I think. I sometimes thought hey where is that method gone, couldn't remember I deleted it. Am 13.12.2017 03:42 schrieb "Ben Coman" <btc(a)openinworld.com>: I could just be having a brain freeze, but just sharing in case anyone else is similarly going mad... a few times recently in Nautilus I've dragged a method from the fourth pane and dropped it on a protocol in the third pane and the method disappeared from the system. Luckily its easily recovered from Tools > Code Changes, where it shows as deleted. But its weird that a delete could be triggered from the action I (thought I) performed. I've yet to detect a pattern. Unfortunately its kind of blink-and-you-miss-it. Its not until a second later when selecting the target protocol that the behaviour becomes apparent. This is in 60527-64, Unix built on Jul 20 2017 20:40:36 Compiler: 4.6.3 cheers -ben

Dec. 13, 2017