July 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Accept in Debugger Meltdown in Pharo 5.0

by Tudor Girba

That is not good. Did it happen repeatedly, or only once? Do you remember the situation? Cheers, Doru > On Jul 27, 2016, at 8:49 AM, stepharo <stepharo(a)free.fr> wrote: > > I know that christophe and me got it too. > > Stef > > > Le 26/7/16 Ã 19:00, Sean P. DeNigris a Ã©crit : >> <http://forum.world.st/file/n4908072/Screenshot_2016-07-26_13.png> >> >> Mac spinning beachball of death followed after about a minute by "... quit >> unexpectedly". Bugforeveryoneorjustme? >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/Accept-in-Debugger-Meltdown-in-Pharo-5-0-tp4908072.ht… >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> >> > > -- www.tudorgirba.com www.feenk.com "Presenting is storytelling."

July 27, 2016

Re: [Pharo-dev] Accept in Debugger Meltdown in Pharo 5.0

by Tudor Girba

> On Jul 27, 2016, at 8:57 AM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > 2016-07-27 2:58 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Tudor Girba-2 wrote > > So, could you describe what you did in more details? > > What details would help? > > > - the image version > - the code you debugged and changed (if public) > - as acccepting code can trigger a lot of system action, it may be useful to report, if there were aother applications open (Senders/Implementors or System Browser). > - and maybe the PharoDebug.log has some usefull information. > +1 Also, is this an isolated case, or did it occurred several times? (this might give us an indication of where to look) Cheers, Doru > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Accept-in-Debugger-Meltdown-in-Pharo-5-0-tp4908072p49… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > -- www.tudorgirba.com www.feenk.com "One cannot do more than one can do."

July 27, 2016

Option for as-in-moose debugger layout

by Yuriy Tymchuk

Hi, is it possible to have some setting to switch the debugger into the layout that is used in Moose? I.e. have the stack vertically on the left. Because come on, look at this image: only 3 lines of variables? And you see all that empty space on the right both in source code and variables pane? Cheers. Uko

July 27, 2016

Re: [Pharo-dev] Accept in Debugger Meltdown in Pharo 5.0

by Nicolai Hess

2016-07-27 2:58 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Tudor Girba-2 wrote > > So, could you describe what you did in more details? > > What details would help? > > - the image version - the code you debugged and changed (if public) - as acccepting code can trigger a lot of system action, it may be useful to report, if there were aother applications open (Senders/Implementors or System Browser). - and maybe the PharoDebug.log has some usefull information. > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Accept-in-Debugger-Meltdown-in-Pharo-5-0-tp4908072p49… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

July 27, 2016

Re: [Pharo-dev] magritte extras

by stepharo

Last time we played with magritte with skip the xml looks really an old version of magritte and it did not work. I have to run now. I know that the magritte repo were a bit messy. Check the magritte version we use in the tinyblog mooc exercise. Stef > I am looking at creating a tool that works like the magritte example. > It uses Magritte-XMLBinding. I ran the tests and had a small number of > failures in Magritte-Tests-XMLBinding. The example > class MADescriptionEditor is in the examples tag of > the Magritte-Seaside package. It came from Repository: > http://smalltalkhub.com/mc/Magritte/Magritte3/main/ and the XML > binding for the examples comes > from Repository:http://smalltalkhub.com/mc/Magritte/Magritte3Addons/main/ > > So if someone has these working and playing together that would be > great. If it is outdated and we are to use something else I would like > to know what the preferred way is so I can build the example building > the descriptions using I guess json. > > Many thanks :-) > Kind Regards, > Sean Glazier

July 27, 2016

Re: [Pharo-dev] Accept in Debugger Meltdown in Pharo 5.0

by stepharo

I know that christophe and me got it too. Stef Le 26/7/16 Ã 19:00, Sean P. DeNigris a Ã©crit : > <http://forum.world.st/file/n4908072/Screenshot_2016-07-26_13.png> > > Mac spinning beachball of death followed after about a minute by "... quit > unexpectedly". Bugforeveryoneorjustme? > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Accept-in-Debugger-Meltdown-in-Pharo-5-0-tp4908072.ht… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

July 27, 2016

Re: [Pharo-dev] Accept in Debugger Meltdown in Pharo 5.0

by Sean P. DeNigris

Tudor Girba-2 wrote > So, could you describe what you did in more details? What details would help? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Accept-in-Debugger-Meltdown-in-Pharo-5-0-tp4908072p49… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 27, 2016

magritte extras

by Sean Glazier

I am looking at creating a tool that works like the magritte example. It uses Magritte-XMLBinding. I ran the tests and had a small number of failures in Magritte-Tests-XMLBinding. The example class MADescriptionEditor is in the examples tag of the Magritte-Seaside package. It came from Repository: http://smalltalkhub.com/mc/Magritte/Magritte3/main/ and the XML binding for the examples comes from Repository: http://smalltalkhub.com/mc/Magritte/Magritte3Addons/main/ So if someone has these working and playing together that would be great. If it is outdated and we are to use something else I would like to know what the preferred way is so I can build the example building the descriptions using I guess json. Many thanks :-) Kind Regards, Sean Glazier

July 26, 2016

Re: [Pharo-dev] http://source.squeakfoundation.org down

by Dale Henrichs

As an FYI to folks who st using FFI in their projects and are using the url http://source.squeakfoundation.org/FFI to reference the project, the domain has been fixed and redirected, but more importantly, the proper domain to use is source.squeak.org: http://source.squeak.org/FFI... Dale On 7/26/16 9:46 AM, Dale Henrichs wrote: > It's not just me: > > http://downforeveryoneorjustme.com/source.squeakfoundation.org > > I'm getting a '502 Bad Gateway' error ... I seems to have broken in > the last hour or so ... > > It also appears that the squeak mailing list is down --- which is why > I've sent the mail here --- The FFI code is hosted on > http://source.squeakfoundation.org so this will likely impact others > as well ... > > Dale >

July 26, 2016

Re: [Pharo-dev] pragma syntax

by Chris Cunningham

I would hope there are exceptions - at least $. and $; . Otherwise mass chaos would ensue. Search for the method #initializeTypeTable. That should steer you towards what can be in a binary method (everything not specifically called out as something besides #xBinary). -cbc On Tue, Jul 26, 2016 at 1:12 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > So binary selector can be any non-alphanumeric symbol? > > On Tue, Jul 26, 2016 at 9:35 PM, Nicolai Hess <nicolaihess(a)gmail.com> > wrote: > >> Thanks Eliot, >> >> 2016-07-26 21:24 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: >> >>> Hi Nicolai, >>> >>> On Tue, Jul 26, 2016 at 12:09 PM, Nicolai Hess <nicolaihess(a)gmail.com> >>> wrote: >>> >>>> Hi, >>>> >>>> is this valid pragma syntax: >>>> >>>> foo >>>> <func: #operation arg: #+> >>>> ^ self >>>> >>> >>> You could say it was ambiguous. With the change to the syntax of binary >>> selectors in recent years #+> is a binary selector, and so you need >>> whitespace after the token to separate it from the closing >. >>> >> >> I was a bit supprised, why '+>' would be a binary selector, as for >> example greater-or-equal is ">=" and not "=>". But I like that we can >> define (any?) combination as binary selector and create new ones like >> => >> ==> >> or >> --> >> >> >> >>> >>> >>>> (note the closing angle and the +-symbol) >>>> >>>> The above code is what the pretty printer creates if you pretty-print >>>> this code >>>> >>> >>> IMO, the pretty printer is the thing that needs fixing. If the last >>> token in the pragma is a binary selector symbol literal then a space should >>> be printed. >>> >> >> :( yes, but I don't like that we need to insert spaces. >> >> >>> >>> >>>> >>>> foo >>>> <func: #operation arg: #+ > >>>> ^ self >>>> >>>> (note the space between #+ and > >>>> >>>> Or a bug in the parser ? >>>> >>>> this pragma definition >>>> <func: #operation arg: #a> >>>> seems to work. >>>> >>> >>> >>> _,,,^..^,,,_ >>> best, Eliot >>> >> >> >

July 26, 2016