[Pharo-dev] GTInspector duplicates overriden extensions
Hi, when I override a method with a GTInspector (because I need to change it), then inspector contains the extension twice. It seems Inspector scans the whole hierarchy of the inspected object for methods, but doesn't deduplicate them. Peter
Re: [Pharo-dev] [Moose-dev] GTInspector duplicates overriden extensions
Hi, Usually when we want to specialize a view in a subclass we override the method and do not add the gtInspectorPresentationOrder: annotation. But also removing duplicationd would make sense. Cheers, Andrei On Feb 25, 2017 4:36 PM, "Peter Uhnak" wrote: Hi, when I override a method with a GTInspector (because I need to change it), then inspector contains the extension twice. It seems Inspector scans the whole hierarchy of the inspected object for methods, but doesn't deduplicate them. Peter ___ Moose-dev mailing list moose-...@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
Re: [Pharo-dev] [Moose-dev] Re: GTInspector duplicates overriden extensions
On Sat, Feb 25, 2017 at 04:44:15PM +0100, Andrei Chis wrote: > Hi, > > Usually when we want to specialize a view in a subclass we override the > method and do not add the gtInspectorPresentationOrder: annotation. But > also removing duplicationd would make sense. Ah, I didn't think of just removing the pragma. :) Thanks! Peter
Re: [Pharo-dev] Build Pharo VM
On Thu, Feb 23, 2017 at 03:51:07PM +0100, Esteban Lorenzano wrote: > for linux you can: > $ cd pharo-vm/opensmalltalk-vm//build.linux32x86/pharo.cog.spur/build > $ ./mvm On a fairly fresh 32-bit Linux Mint 17 (based on Ubuntu 14.04), first apt-get install curl, libssl-dev, cmake, uuid-dev, and libtool which are the dependencies. On libtool, the (generated?) source contains a version which doesn't understand a command line argument that it was fed. I changed that libtool file to a symlink to the system-installed one. The HT version that I built segfaults now and then on my 64-bit Linux Mint 17. I'm using the ITHB one. Pierce
Re: [Pharo-dev] Any idea for a cool name for the remote tool suite?
On Fri, Feb 24, 2017 at 04:42:03PM -0800, Sean P. DeNigris wrote: > Andreas Wacknitz wrote > > Everything that is used outside Pharo could have a fancy name. > > For internal tools and frameworks this is... like talking in argot and > > creates high walls around Pharo. > > +100 Just call it Bike Teleporter already. :-P Pierce
