23 May
2014
23 May
'14
12:15 p.m.
I don't have time today, but I'll have a look over it during the weekend.
It shouldn't be so difficult to implement :)
Andrei
On Fri, May 23, 2014 at 12:03 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
Yes, that should be the default behavior.
Doru
On Fri, May 23, 2014 at 11:47 AM, Andrei Chis <chisvasileandrei(a)gmail.com>wrote;wrote:
Yes, that's a problem. Right now the sorting
block receives the objects
that are displayed and not the string representation that is actually
displayed in a column.
As a solution we could make it so by default a column is sortable by the
text representation that is being displayed. The sorting block could then
be used
only if a different type of sorting is needed.
What do you think?
Cheers,
Andrei
On Fri, May 23, 2014 at 11:23 AM, Yuriy Tymchuk <yuriy.tymchuk(a)usi.ch>wrote;wrote:
--
www.tudorgirba.com
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi guys.
I’ve encountered an error that occurs when we are displaying for example
dict in GTInspector. There is very nice functionality which sorts items
according to one column
column: 'Key'
evaluated: [:each | GTObjectPrinter new
asTruncatedTextFrom: each key ]
sortedBy: [:x :y | x > y ];
but not all objects know how to respond to #>.
Any ideas how to solve this in a mic way?
Uko
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev