Re: [Pharo-dev] [Pharo6] [Issue Tracker] Current Status

> On 3 Mar 2017, at 09:59, Marcus Denker wrote: > > Hi, > > The current status is: > > Issues Tagged Pharo6: 52 > Overall: 598 > Post Sprint: Issues Tagged Pharo6: 26 Issues Overall: 585

Re: [Pharo-dev] Growing large images: the case of Moose models

tx clement this is indeed really important On Fri, 03 Mar 2017 11:56:05 +0100, Clément Bera wrote: Hello everyone, This morning I investigated with Vincent Blondeau a problem reported by the Moose community a while ago: loading Moose model is slower in Spur

Re: [Pharo-dev] [Pharo6] [Issue Tracker] Current Status

excellent! Tx to all the sprinters Stef On Sat, 04 Mar 2017 09:24:58 +0100, Marcus Denker wrote: On 3 Mar 2017, at 09:59, Marcus Denker wrote: Hi, The current status is: Issues Tagged Pharo6: 52 Overall:

[Pharo-dev] Spotter idea - bring existing code windows to front

A quick note on an idea that strikes me, I often find myself with a large number of windows open and I know I have a code window open previously but the task bar is a bit opaque to find it, and its so cheap to open a new code window from Spotter, thats what I do, and open yet another window,

[Pharo-dev] Seamless integration with GTInspector

Hi Denis, Can you try Seamless with GTInspector in the latest version of Pharo or Moose and let me know if you see any slowness. Not sure how Seamless uses GTInspector to inspect proxy objects but now as the inspector uses FastTable by default there is no cache whatsoever. What this means is

Re: [Pharo-dev] Seamless integration with GTInspector

Hi Andrei I already adopted Seamless to changes in GTInspector. So everything works well. For now I do not follow your fast table solution. Remote and local presentations are implemented with old approach. I just copied few methods from old GT version to make it work. So it works same way as

Re: [Pharo-dev] Seamless integration with GTInspector

Hi Denis, Thanks for the clarification. Then it's good as Seamless will not be impacted by this. Let me if/when you start looking making GTInspector in Seamless use FastTable. I think I'll still add a tiny cache so that the string representation is not recomputed every time. Cheers, Andrei On

Re: [Pharo-dev] Spotter idea - bring existing code windows to front

I made a little experiment to get the windows listed in spotter. [image: Inline image 1] I have still an issue with the activation and some weird windows listed but should be able to give you just that in a couple hours. This is a good opportunity for me to jump into spotter extensions, thx for

Re: [Pharo-dev] Code Completion in Pharo

One thing that is broken in current code completion and needs to be addressed is when you try to edit keyword messages. For example you have: dict at: #foo and you want to add ifAbsent: part. Current implementation won't help you, because it works out of context and doesn't recognize the whole

Re: [Pharo-dev] [Pharo-users] [ANN] XML Metadata Interchange (XMI) for Pharo

On Thu, 02 Mar 2017 10:02:04 +0100, Peter Uhnak wrote: We spoke briefly on Tuesday. I need to take a look (also at his EMF generator) and see how the tools could benefit from each other. I think it could simplify some of my code or streamline the use of it. super cool

Re: [Pharo-dev] Regarding the autocomplete project information

Hello Siddarth I know that one student from Prague lukas started to work on analysing the ecompletion of Pharo. I think that it would be fair to let him the priority. Then if he does not/cannot work on it we can offer it to you. I sent a mail to him because he is often too busy. Stef

Re: [Pharo-dev] [Pharo-users] [ANN] Regex Tester Tool for Pharo

And I think that his remark makes sense. I was wondering if we should not ressurect the RePlugin to make sure that users can use perlish regexp and do not feel that our world is strange. +1 +23 I've been using regexes casually for years and yet every time I use them in Pharo I have

Re: [Pharo-dev] Code Completion in Pharo

On Sat, 04 Mar 2017 20:07:00 +0100, webwarrior wrote: One thing that is broken in current code completion and needs to be addressed is when you try to edit keyword messages. For example you have: dict at: #foo and you want to add ifAbsent: part. Current implementation

Re: [Pharo-dev] Spotter idea - bring existing code windows to front

Hi Ben. I think it is good strategy for general usage, not only spotter. If user requests browser for item which already shown in existing window then this window should be shown instead of opening new one 2017-03-04 16:19 GMT+01:00 Ben Coman : > A quick note on an idea