Hi,

I think Kilon refers to the search in the Items presentation of a collection. If so, that search field accepts a Pharo expression of the form:
�� �� each isMatchingSomething

In that case, this will translate in��
�� ��self select: [:each | each isMatchingSomething]

If you hover with the mouse over the search input you should get this info.

Cheers,
Doru


On Thu, Dec 4, 2014 at 12:26 PM, Usman Bhatti <usman.bhatti@gmail.com> wrote:


On Thu, Dec 4, 2014 at 12:15 PM, kilon alios <kilon.alios@gmail.com> wrote:
"Did you try this script in the discussion that shows the other possibility of list scrolling in Morph without talking about GT-*: This covers your requirement of omnipresent buttons and a list showing a fix number of items (in your case 50)."

I did try but was giving me an error . The code you provide here works. Yes its as I assumed you want to go down the route of pages, but as I said again its not related to my issue.

Yes I really like your solution. I wonder why Tudor prefer continuous scroll , is there any advantage ?

Just a side note here even paging is very limited and unsuitable for big data, I think in the end a search facility on steroids would be an ideal solution, possible one supporting regex like finder tool already does.��

It is already possible to search in lists by sending filterOn:/searchOn: message to the list presentation in Glamour. An example:
| finder |
finder := GLMFinder new.
finder show: [:a |��
a list
beMultiple;
title: 'Simple'.
a list
title: 'With filter';
beMultiple;
filterOn: [:text :each | (Smalltalk evaluate: '[:each | ', text, ']') value: each];
helpMessage: ��'Enter a filtering request (e.g., "each > 10")'.
a list
title: 'With search';
beMultiple;
searchOn: [:text :each | (Smalltalk evaluate: '[:each | ', text, ']') value: each];
helpMessage: ��'Enter a search request (e.g., "each > 10")' ].
^ finder ��openOn: (1 to: 100)��
��




--
www.tudorgirba.com

"Every thing has its own flow"