>
> Does anyone know why was Spotlight removed from distribution v4?
>
Because Spotter replaces it.
Marcus
Hi Doru ,
On Fri, Feb 6, 2015 at 9:40 AM, Tudor Girba wrote:
>
>
> In the latest Pharo 4 Spotter works properly with the Dark Theme.
>
Starting from a fresh image (downloaded this week), and doing nothing more
than setting the theme to Pharo 3 Dark, GTSpotter shows white, what is
curious because
Hi,
On Tue, Feb 3, 2015 at 6:39 PM, Laura Risani wrote:
> I'm using v3, and the #Spotlight (class name) that comes with it.
>
> I didn't know about Spotter of v4 before your comment. I've just tried it,
> it could be handy for some specific situations, after i manually tweak its
> non-sense whit
I'm using v3, and the #Spotlight (class name) that comes with it.
I didn't know about Spotter of v4 before your comment. I've just tried it,
it could be handy for some specific situations, after i manually tweak its
non-sense whiteness which somewhy escapes global theme defaults (lovely
dark theme
Hi!
Spotlight or Spotter? Which version of Pharo are you using?
I ask because the old Spotlight should be using the same code completion
mechanism => it should appear/disappear from both at the same time...
As for spotter, I don't have an answer now :)
Saludos,
Guille
El Tue Feb 03 2015 at 5:2
Thank you all for your answers.
Hi Guille ,
Nice solution! It worked perfectly for Code Completition!
Yet the obsolete symbols (class names and selectors) keep showing in
Spotlight, but i guess this is too implementation specific. I will step
through its execution to try to find out how it works
Well yes, but GCs are happening all the time :). So the problem is that
someone is keeping a strong reference on the symbol.
I tried the following:
- create a method named #unusedUnexpectedMessage: That came up in the auto
completion, ok
- remove it: Still in auto completion
- force GC a looot: s
But weak refs are only killed after GC, right ?
And even then...
> On 02 Feb 2015, at 12:03, Guillermo Polito wrote:
>
> It's the table that keeps the symbols and checks their uniqueness.
>
> but AFAIK the symbol table is weak. So probably it's the completion mechanism
> that is keeping extra
It's the table that keeps the symbols and checks their uniqueness.
but AFAIK the symbol table is weak. So probably it's the completion
mechanism that is keeping extra references...
El Mon Feb 02 2015 at 11:52:28 AM, p...@highoctane.be
escribió:
> Got the same problem here.
>
> Annoying when thir
Maybe try
Symbol compactSymbolTable
But completion could do its own caching, I don't know.
> On 02 Feb 2015, at 11:44, stepharo wrote:
>
> Probably by resetting the Symbol intern table. but no time to dive into it
> now.
>> Hi all,
>>
>> Code completition tools show class/method old
Got the same problem here.
Annoying when third parties have to do something in the environment as they
are shown things that do not exist.
Where to look? What's the symbol intern table?
Phil
On Mon, Feb 2, 2015 at 11:44 AM, stepharo wrote:
> Probably by resetting the Symbol intern table. but
Probably by resetting the Symbol intern table. but no time to dive into
it now.
Hi all,
Code completition tools show class/method old names i've changed and
no longer use. How can i remove all unused (occurring nowhere in
source code) or unimplemented names?
Best,
Laura
Hi all,
Code completition tools show class/method old names i've changed and no
longer use. How can i remove all unused (occurring nowhere in source code)
or unimplemented names?
Best,
Laura
13 matches
Mail list logo
