Issue 3291 in pharo: Missing text field with completion

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
23 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Issue 3291 in pharo: Missing text field with completion

pharo
Status: Accepted
Owner: aplantec
Labels: Milestone-1.2

New issue 3291 by aplantec: Missing text field with completion
http://code.google.com/p/pharo/issues/detail?id=3291

Could be added as an instrumentation of PluggableTextFieldMorph.


Reply | Threaded
Open this post in threaded view
|

Re: Issue 3291 in pharo: Missing text field with completion

pharo

Comment #1 on issue 3291 by aplantec: Missing text field with completion
http://code.google.com/p/pharo/issues/detail?id=3291

In PharoTaskForces:

SLICE-Issue-3291-Missing-text-field-with-completion

For testing.
Not documented.
Test it with the findClass dialog which now makes use of a completion list  
for class name input field.



Reply | Threaded
Open this post in threaded view
|

Re: Issue 3291 in pharo: Missing text field with completion

Alain Plantec-4
Dear list,
I'm not should it's enough clear so
a screenshot is attached.
Cheers
Alain

findClassCompletion.png (96K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Issue 3291 in pharo: Missing text field with completion

Lukas Renggli
Why two lists when one list is enough?

http://www.lukas-renggli.ch/blog/ob-completion-dialog

Lukas

On 24 November 2010 19:08, Alain Plantec <[hidden email]> wrote:
> Dear list,
> I'm not should it's enough clear so
> a screenshot is attached.
> Cheers
> Alain
>



--
Lukas Renggli
www.lukas-renggli.ch

Reply | Threaded
Open this post in threaded view
|

Re: Issue 3291 in pharo: Missing text field with completion

Francisco Ortiz Peñaloza
I was wondering the same, the top static list dosn't make any sense to me. Like the one when you add a category.

Francisco

On Wed, Nov 24, 2010 at 9:33 PM, Lukas Renggli <[hidden email]> wrote:
Why two lists when one list is enough?

http://www.lukas-renggli.ch/blog/ob-completion-dialog

Lukas

On 24 November 2010 19:08, Alain Plantec <[hidden email]> wrote:
> Dear list,
> I'm not should it's enough clear so
> a screenshot is attached.
> Cheers
> Alain
>



--
Lukas Renggli
www.lukas-renggli.ch


Reply | Threaded
Open this post in threaded view
|

Re: Issue 3291 in pharo: Missing text field with completion

Francisco Ortiz Peñaloza
I would like to add that just watched Lukas ob-completion-dialog and the PluggableTextFieldMorph autocomplete looks better for me.

From an usability point of view it looks more like OSX Spotlight or web autocomplete on html input elements users are used to.

Cheers,
Francisco

On Thu, Nov 25, 2010 at 1:27 AM, Francisco Ortiz Peñaloza <[hidden email]> wrote:
I was wondering the same, the top static list dosn't make any sense to me. Like the one when you add a category.

Francisco

On Wed, Nov 24, 2010 at 9:33 PM, Lukas Renggli <[hidden email]> wrote:
Why two lists when one list is enough?

http://www.lukas-renggli.ch/blog/ob-completion-dialog

Lukas

On 24 November 2010 19:08, Alain Plantec <[hidden email]> wrote:
> Dear list,
> I'm not should it's enough clear so
> a screenshot is attached.
> Cheers
> Alain
>



--
Lukas Renggli
www.lukas-renggli.ch



Reply | Threaded
Open this post in threaded view
|

Re: Issue 3291 in pharo: Missing text field with completion

Alain Plantec-4
In reply to this post by Lukas Renggli
Hi Lukas,
ok, I've plugged the textfield with completion (surely a bad name) in
the find class for testing only.
I don't like the two lists also.
The purpose is to have a normal text field which popup a list of
possible answers only
when you typin something in the field.
So, its a basic widget which, afaik is missing and that could be used
with ob-tools.
btw: even with ob find class, add category, etc, I would prefer to see
only one simple text field.
Cheers
Alain

Le 25/11/2010 00:33, Lukas Renggli a écrit :

> Why two lists when one list is enough?
>
> http://www.lukas-renggli.ch/blog/ob-completion-dialog
>
> Lukas
>
> On 24 November 2010 19:08, Alain Plantec<[hidden email]>  wrote:
>> Dear list,
>> I'm not should it's enough clear so
>> a screenshot is attached.
>> Cheers
>> Alain
>>
>
>


Reply | Threaded
Open this post in threaded view
|

Re: Issue 3291 in pharo: Missing text field with completion

Stéphane Ducasse
In reply to this post by Lukas Renggli
tx alain

this is important to improve basic widgets because they will have a big impact.

Stef


On Nov 25, 2010, at 8:14 AM, Alain Plantec wrote:

> Hi Lukas,
> ok, I've plugged the textfield with completion (surely a bad name) in the find class for testing only.
> I don't like the two lists also.
> The purpose is to have a normal text field which popup a list of possible answers only
> when you typin something in the field.
> So, its a basic widget which, afaik is missing and that could be used with ob-tools.
> btw: even with ob find class, add category, etc, I would prefer to see only one simple text field.
> Cheers
> Alain
>
> Le 25/11/2010 00:33, Lukas Renggli a écrit :
>> Why two lists when one list is enough?
>>
>> http://www.lukas-renggli.ch/blog/ob-completion-dialog
>>
>> Lukas
>>
>> On 24 November 2010 19:08, Alain Plantec<[hidden email]>  wrote:
>>> Dear list,
>>> I'm not should it's enough clear so
>>> a screenshot is attached.
>>> Cheers
>>> Alain
>>>
>>
>>
>
>


Reply | Threaded
Open this post in threaded view
|

Issue 3291 in pharo: Missing text field with completion

Lukas Renggli
In reply to this post by Alain Plantec-4
> 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. 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



--
Lukas Renggli
www.lukas-renggli.ch

Screen shot 2010-11-25 at 07.55.41 .png (34K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Issue 3291 in pharo: Missing text field with completion

pharo
In reply to this post by pharo
Updates:
        Labels: -Milestone-1.2

Comment #2 on issue 3291 by marcus.denker: Missing text field with  
completion
http://code.google.com/p/pharo/issues/detail?id=3291

Not for 1.2?


Reply | Threaded
Open this post in threaded view
|

Re: Issue 3291 in pharo: Missing text field with completion

Alain Plantec-4
In reply to this post by Lukas Renggli
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
>
>
>


Reply | Threaded
Open this post in threaded view
|

Re: Issue 3291 in pharo: Missing text field with completion

Lukas Renggli
> sorry but why much better?
> OBCompletionRequest is a dialog.
> What I propose is to enrich PluggableTextFieldMorph

Ahh, ok. I had the impression you somehow integrated eCompletion into
text fields.

Lukas

--
Lukas Renggli
www.lukas-renggli.ch

Reply | Threaded
Open this post in threaded view
|

Re: Issue 3291 in pharo: Missing text field with completion

Stéphane Ducasse
In reply to this post by Lukas Renggli
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
>>
>>
>>
>
>


Reply | Threaded
Open this post in threaded view
|

Re: Issue 3291 in pharo: Missing text field with completion

Francisco Ortiz Peñaloza
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

findClassCompletion.png


---------- Forwarded message ----------
From: Stéphane Ducasse <[hidden email]>
Date: Thu, Nov 25, 2010 at 2:23 PM
Subject: Re: [Pharo-project] Issue 3291 in pharo: Missing text field with completion
To: [hidden email], [hidden email]


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



Reply | Threaded
Open this post in threaded view
|

Re: Issue 3291 in pharo: Missing text field with completion

Stéphane Ducasse
In reply to this post by Stéphane Ducasse

On Nov 25, 2010, at 7:22 PM, Francisco Ortiz Peñaloza wrote:

> 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  :)

why because I most of the time look for something that I already browsed.


Reply | Threaded
Open this post in threaded view
|

Re: Issue 3291 in pharo: Missing text field with completion

Francisco Ortiz Peñaloza
WITH recently used on top

On Thu, Nov 25, 2010 at 5:26 PM, Stéphane Ducasse <[hidden email]> wrote:

On Nov 25, 2010, at 7:22 PM, Francisco Ortiz Peñaloza wrote:

> 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  :)

why because I most of the time look for something that I already browsed.



Reply | Threaded
Open this post in threaded view
|

Re: Issue 3291 in pharo: Missing text field with completion

Stéphane Ducasse
In reply to this post by Stéphane Ducasse

On Nov 25, 2010, at 9:57 PM, Francisco Ortiz Peñaloza wrote:

> WITH recently used on top

Ok I see :)

>
> On Thu, Nov 25, 2010 at 5:26 PM, Stéphane Ducasse <[hidden email]> wrote:
>
> On Nov 25, 2010, at 7:22 PM, Francisco Ortiz Peñaloza wrote:
>
> > 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  :)
>
> why because I most of the time look for something that I already browsed.
>
>
>


Reply | Threaded
Open this post in threaded view
|

Re: Issue 3291 in pharo: Missing text field with completion

Alain Plantec-4
Le 25/11/2010 22:08, Stéphane Ducasse a écrit :
> On Nov 25, 2010, at 9:57 PM, Francisco Ortiz Peñaloza wrote:
>
>> WITH recently used on top
> Ok I see :)
yes but you have to enter some text to see the list...
so, Lukas's dialog is better for such a fonctionality

>> On Thu, Nov 25, 2010 at 5:26 PM, Stéphane Ducasse<[hidden email]>  wrote:
>>
>> On Nov 25, 2010, at 7:22 PM, Francisco Ortiz Peñaloza wrote:
>>
>>> 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  :)
>> why because I most of the time look for something that I already browsed.
>>
>>
>>
>
>


Reply | Threaded
Open this post in threaded view
|

Re: Issue 3291 in pharo: Missing text field with completion

Tudor Girba
The OB widget is quite nice and snappy. Just for reference, there is also a nice search widget in Gaucho. Fernando said that he would package it separately, but I do not know what the status is.

Cheers,
Doru


On 25 Nov 2010, at 23:19, Alain Plantec wrote:

> Le 25/11/2010 22:08, Stéphane Ducasse a écrit :
>> On Nov 25, 2010, at 9:57 PM, Francisco Ortiz Peñaloza wrote:
>>
>>> WITH recently used on top
>> Ok I see :)
> yes but you have to enter some text to see the list...
> so, Lukas's dialog is better for such a fonctionality
>
>>> On Thu, Nov 25, 2010 at 5:26 PM, Stéphane Ducasse<[hidden email]>  wrote:
>>>
>>> On Nov 25, 2010, at 7:22 PM, Francisco Ortiz Peñaloza wrote:
>>>
>>>> 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  :)
>>> why because I most of the time look for something that I already browsed.
>>>
>>>
>>>
>>
>>
>
>

--
www.tudorgirba.com

"Speaking louder won't make the point worthier."


Reply | Threaded
Open this post in threaded view
|

Re: Issue 3291 in pharo: Missing text field with completion

pharo
In reply to this post by pharo
Updates:
        Labels: Milestone-1.2

Comment #3 on issue 3291 by aplantec: Missing text field with completion
http://code.google.com/p/pharo/issues/detail?id=3291

yes.
In PharoTaskForces:
last version of SLICE-Issue-3291-Missing-text-field-with-completion.
Reasonably tested and documented.
The FindReplaceDialogWindow is using it to popup previously entered tokens  
in the find and in the replace fields. This greatly improve its useability.




12