[Pharo-dev] Raw pane on byteStrings
thierry.goubier at gmail.com
Fri Feb 24 04:37:30 EST 2017
if you're using fasttable for the Raw view, you should be able to reach one
100k elements without issues. I did some experiments and it handles the
load very well.
Avoid the paginator at any cost. This thing is really user-unfriendly.
2017-02-23 20:19 GMT+01:00 Andrei Chis <chisvasileandrei at gmail.com>:
> Hi Stef,
> Currently that's the default behaviour of the Raw view: it displays for
> collections only the first and the last 21 elements. The Items view however
> always should display all the elements of a collection.
> The main problem with the Raw view in Pharo 5 is the speed. In Pharo 6 now
> the speed of the Raw view is greately improved so we could increase those
> limits. Still for now there should still be some limit for the Raw view.
> Ideally we should add a small widget, something like a paginator, for
> navigating through large and very large collections.
> On Feb 23, 2017 19:35, "stepharong" <stepharong at free.fr> wrote:
>> I'm trying to debug citezen generation and I have to compare strings.
>> Now I think that the raw views (in Pharo 50) is not good because we
>> cannot see all the items in raw format.
>> See the attachements. It jumps from 21 to 174 ...
>> and what I want to see is of course in the middle.
>> Is it me or there is something wrong there.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pharo-dev