- Pharo-dev - lists.pharo.org

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

Re: [Pharo-dev] pragma syntax

by Peter UhnÃ¡k

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

Re: [Pharo-dev] Doubled setting for now showing catalog projects in Spotter

by Tudor Girba

Hi Torsten, Thanks for raising this up. Indeed, this requires a bit of a discussion. The âuglyâ settings are not a hack, but they are indeed not well presented and explained :). We already had an issue with this (https://pharo.fogbugz.com/f/cases/18472/GTSpotter-settings-are-unusable) but we are slow in these months because the focus is still to release Moose on Pharo 5 and then we can move all our attention to Pharo 6. I am sorry for that. The problem that these generated settings solves is that of allowing us to disable any processor we might want without requiring a manual setting for that. This is important in order to strike a balance between extensibility and control. As I said, I agree that we need to find a way to present these settings better, but they are needed. Please read this and let me know what you think: http://www.humane-assessment.com/blog/discovering-and-managing-spotter-exte… Cheers, Doru > On Jul 26, 2016, at 4:49 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi, > > I today wondered as in latest image it was not possible to download projects from Spotter anymore. > The setting for downloading projects from Catalog was enabled. > > In latest Pharo 6 there is a new (second and redundant) setting to exclude catalog projects from > Spotter (now provided by the GT tools). > > Also it is not implemented very nice: > - it uses reflection and is therefore hard to find (implemented in #catalogSettingsOn:) > - it shows ugly symbols in the settings browser without any description > - while the method is called #catalogSettingsOn: the way it is implemented > it allows to disable ANY GT Spotter extension in the settings browser > as it uses "GTSpotter spotterExtendingMethods". Not very intention revealing. > > To me this really looks like a BIG AND QUICK HACK and a solution to a problem that was already > solved before. Please remove it/roll back this unnecessary addition. > > > Side note: > ========== > There ALREADY WAS A SETTING FOR THAT (since Pharo 5 or 4) to not query the catalog (because > a few people lamented before that it slows down when connected with low bandwidth network). > > It is implemented in CatalogSettings and you can find it in the settings browser > under "Tools" -> "Catalog" -> "Display catalog projects in Spotter" and is used > in the spotter extension #spotterCatalogProjectsFor: > > Second side note: > ================= > If the intention was to generally provide an ability to disable any spotter extension > (via reflection) then use #spotterExtensionSettingsOn: instead of the name #catalogSettingsOn: > and set the default to true for the catalog extension. > If you want to disable projects showing up by default in spotter via network connection > than use the one that was already there and set it to false by default. > (which I would not do as network should be fast enough these days for catalog in most places > also catalog is already cached and the call implemented asynchronously, so Spotter opens > right away). > > Thanks > Torsten > -- www.tudorgirba.com www.feenk.com "Problem solving efficiency grows with the abstractness level of problem understanding."

July 26, 2016

Re: [Pharo-dev] pragma syntax

by Nicolai Hess

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

Re: [Pharo-dev] pragma syntax

by Eliot Miranda

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 >. > (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. > > 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

pragma syntax

by Nicolai Hess

Hi, is this valid pragma syntax: foo <func: #operation arg: #+> ^ self (note the closing angle and the +-symbol) The above code is what the pretty printer creates if you pretty-print this code 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.

July 26, 2016