Re: [Pharo-project] Issue 3291 in pharo: Missing text field with completion
lukas could you publish CompletionRequest somewhere in a place like a bug entry so that we integrate it :) Stef
Le 25/11/2010 12:03, Lukas Renggli a écrit :
So, its a basic widget which, afaik is missing and that could be used with ob-tools. I don't follow what you and Francisco are saying.
IMHO there is a much better widget already in OB. sorry but why much better? OBCompletionRequest is a dialog. What I propose is to enrich PluggableTextFieldMorph with the possibility to use a completion list. So we have two differents things here. And indeed, OBCompletionRequest should be named CompletionRequest and integrated in the core. Showing it in the browser find class was not a good idea... Cheers Alain
I suggest to make that a standard widget so that other tools outside of OB can take advantage too.
It is simple subclass of DialogWindow morph from Polymorph and can be fully configured and opened for example like this:
OBCompletionRequest new prompt: 'Find Class'; searchBlock: [ :string | self findClassIn: target environment pattern: string ]; labelBlock: [ :class | class name ]; iconBlock: [ :class | class browserIcon ]; signal
Lukas
-- Lukas Renggli www.lukas-renggli.ch
Hi, as ppl use to say a picture is *worth a thousand words (or two thousands in bad written english)* Imho it should look like this, without the static list and with recently used on top :) Francisco ** [image: findClassCompletion.png] ** ---------- Forwarded message ---------- From: Stéphane Ducasse <stephane.ducasse@inria.fr> Date: Thu, Nov 25, 2010 at 2:23 PM Subject: Re: [Pharo-project] Issue 3291 in pharo: Missing text field with completion To: Pharo-project@lists.gforge.inria.fr, alain.plantec@free.fr lukas could you publish CompletionRequest somewhere in a place like a bug entry so that we integrate it :) Stef
Le 25/11/2010 12:03, Lukas Renggli a écrit :
So, its a basic widget which, afaik is missing and that could be used with ob-tools. I don't follow what you and Francisco are saying.
IMHO there is a much better widget already in OB. sorry but why much better? OBCompletionRequest is a dialog. What I propose is to enrich PluggableTextFieldMorph with the possibility to use a completion list. So we have two differents things here. And indeed, OBCompletionRequest should be named CompletionRequest and integrated in the core. Showing it in the browser find class was not a good idea... Cheers Alain
I suggest to make that a standard widget so that other tools outside of OB can take advantage too.
It is simple subclass of DialogWindow morph from Polymorph and can be fully configured and opened for example like this:
OBCompletionRequest new prompt: 'Find Class'; searchBlock: [ :string | self findClassIn: target environment pattern: string ]; labelBlock: [ :class | class name ]; iconBlock: [ :class | class browserIcon ]; signal
Lukas
-- Lukas Renggli www.lukas-renggli.ch
participants (2)
-
Francisco Ortiz Peñaloza -
Stéphane Ducasse