DataFrame inspector issues

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

DataFrame inspector issues

Alistair Grant
Hi Everyone,

I've started using DataFrame, it's great to have this functionality
easily available, and noticed a few issues with the inspector:

1. The inspector always shows row numbers and not the supplied name.

2. The last column label isn't displayed.

If I remember correctly, there has been some discussion about making the
column widths draggable in the inspector.  I would prefer to have a
context menu that is "size to fit".  This could be potentially expensive
to calculate, so it would be user-initiated.

Where should I report issues?
https://github.com/PolyMathOrg/DataFrame/issues

I have a patch that addresses the first issue, although I'm not
completely happy with it, and I'll take a look at the second issue.


Thanks very much,
Alistair

Reply | Threaded
Open this post in threaded view
|

Re: DataFrame inspector issues

SergeStinckwich


On Tue, Sep 12, 2017 at 9:22 AM, Alistair Grant <[hidden email]> wrote:
Hi Everyone,


​Hi Alistair,
I've started using DataFrame, it's great to have this functionality
easily available, and noticed a few issues with the inspector:

1. The inspector always shows row numbers and not the supplied name.

2. The last column label isn't displayed.

If I remember correctly, there has been some discussion about making the
column widths draggable in the inspector.  I would prefer to have a
context menu that is "size to fit".  This could be potentially expensive
to calculate, so it would be user-initiated.

Where should I report issues?
https://github.com/PolyMathOrg/DataFrame/issues


​Thank you for your report.​

​At the moment, you can report issues here. I guess later, we will intregrate
DataFrame in the main PolyMath repository.
I have a patch that addresses the first issue, although I'm not
completely happy with it, and I'll take a look at the second issue.

​This is maybe better to discuss about DataFrame​ and other PolyMath issues 

​See you there !​

--
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/
Reply | Threaded
Open this post in threaded view
|

Re: DataFrame inspector issues

Alistair Grant
On Tue, Sep 12, 2017 at 09:28:13AM +0200, Serge Stinckwich wrote:

>
> On Tue, Sep 12, 2017 at 9:22 AM, Alistair Grant <[hidden email]> wrote:
>
>     Hi Everyone,
>
> ?Hi Alistair,
>
>     I've started using DataFrame, it's great to have this functionality
>     easily available, and noticed a few issues with the inspector:
>
>     1. The inspector always shows row numbers and not the supplied name.
>
>     2. The last column label isn't displayed.
>
>
>     Where should I report issues?
>     https://github.com/PolyMathOrg/DataFrame/issues
>
>
>
> ?Thank you for your report.?
>
> ?At the moment, you can report issues here. I guess later, we will intregrate
> DataFrame in the main PolyMath repository.
> ?
>
>     I have a patch that addresses the first issue, although I'm not
>     completely happy with it, and I'll take a look at the second issue.
>
>
> ?This is maybe better to discuss about DataFrame? and other PolyMath issues
> on the polymath mailing-list: https://groups.google.com/forum/#!forum/scismalltalk
>
> ?See you there !?

Hi Serge,

Thanks, I've joined the group and reposted the message there.

I wrote:
>     If I remember correctly, there has been some discussion about making the
>     column widths draggable in the inspector.  I would prefer to have a
>     context menu that is "size to fit".  This could be potentially expensive
>     to calculate, so it would be user-initiated.

I think this is more of a FastTable / GT issue than DataFrame, so maybe
the discussion should stay here?  (if anyone is interested :-)).

Thanks,
Alistair

Reply | Threaded
Open this post in threaded view
|

Re: DataFrame inspector issues

Stephane Ducasse-3
sure no stress. When it will be with a too large volume we will complain.
Ideally I would like DataFrame not to be part of PolyMath but of Containers
and that PolyMath uses Containers.
What is Containers: a Collection of datastructure that is managed in a
modular fashion.
I would like to remove from the image all the datastructure that are not used
and migrate them to Containers + tests + coverage + consistent documentation.
So that we can cherry pick the one we need.

http://smalltalkhub.com/#!/~StephaneDucasse/Containers/source

Stef



Stef

On Tue, Sep 12, 2017 at 11:39 AM, Alistair Grant <[hidden email]> wrote:

> On Tue, Sep 12, 2017 at 09:28:13AM +0200, Serge Stinckwich wrote:
>>
>> On Tue, Sep 12, 2017 at 9:22 AM, Alistair Grant <[hidden email]> wrote:
>>
>>     Hi Everyone,
>>
>> ?Hi Alistair,
>>
>>     I've started using DataFrame, it's great to have this functionality
>>     easily available, and noticed a few issues with the inspector:
>>
>>     1. The inspector always shows row numbers and not the supplied name.
>>
>>     2. The last column label isn't displayed.
>>
>>
>>     Where should I report issues?
>>     https://github.com/PolyMathOrg/DataFrame/issues
>>
>>
>>
>> ?Thank you for your report.?
>>
>> ?At the moment, you can report issues here. I guess later, we will intregrate
>> DataFrame in the main PolyMath repository.
>> ?
>>
>>     I have a patch that addresses the first issue, although I'm not
>>     completely happy with it, and I'll take a look at the second issue.
>>
>>
>> ?This is maybe better to discuss about DataFrame? and other PolyMath issues
>> on the polymath mailing-list: https://groups.google.com/forum/#!forum/scismalltalk
>>
>> ?See you there !?
>
> Hi Serge,
>
> Thanks, I've joined the group and reposted the message there.
>
> I wrote:
>>     If I remember correctly, there has been some discussion about making the
>>     column widths draggable in the inspector.  I would prefer to have a
>>     context menu that is "size to fit".  This could be potentially expensive
>>     to calculate, so it would be user-initiated.
>
> I think this is more of a FastTable / GT issue than DataFrame, so maybe
> the discussion should stay here?  (if anyone is interested :-)).
>
> Thanks,
> Alistair
>

Reply | Threaded
Open this post in threaded view
|

Re: DataFrame inspector issues

NorbertHartl
+1

Norbert

> Am 13.09.2017 um 09:54 schrieb Stephane Ducasse <[hidden email]>:
>
> sure no stress. When it will be with a too large volume we will complain.
> Ideally I would like DataFrame not to be part of PolyMath but of Containers
> and that PolyMath uses Containers.
> What is Containers: a Collection of datastructure that is managed in a
> modular fashion.
> I would like to remove from the image all the datastructure that are not used
> and migrate them to Containers + tests + coverage + consistent documentation.
> So that we can cherry pick the one we need.
>
> http://smalltalkhub.com/#!/~StephaneDucasse/Containers/source
>
> Stef
>
>
>
> Stef
>
>> On Tue, Sep 12, 2017 at 11:39 AM, Alistair Grant <[hidden email]> wrote:
>>> On Tue, Sep 12, 2017 at 09:28:13AM +0200, Serge Stinckwich wrote:
>>>
>>> On Tue, Sep 12, 2017 at 9:22 AM, Alistair Grant <[hidden email]> wrote:
>>>
>>>    Hi Everyone,
>>>
>>> ?Hi Alistair,
>>>
>>>    I've started using DataFrame, it's great to have this functionality
>>>    easily available, and noticed a few issues with the inspector:
>>>
>>>    1. The inspector always shows row numbers and not the supplied name.
>>>
>>>    2. The last column label isn't displayed.
>>>
>>>
>>>    Where should I report issues?
>>>    https://github.com/PolyMathOrg/DataFrame/issues
>>>
>>>
>>>
>>> ?Thank you for your report.?
>>>
>>> ?At the moment, you can report issues here. I guess later, we will intregrate
>>> DataFrame in the main PolyMath repository.
>>> ?
>>>
>>>    I have a patch that addresses the first issue, although I'm not
>>>    completely happy with it, and I'll take a look at the second issue.
>>>
>>>
>>> ?This is maybe better to discuss about DataFrame? and other PolyMath issues
>>> on the polymath mailing-list: https://groups.google.com/forum/#!forum/scismalltalk
>>>
>>> ?See you there !?
>>
>> Hi Serge,
>>
>> Thanks, I've joined the group and reposted the message there.
>>
>> I wrote:
>>>    If I remember correctly, there has been some discussion about making the
>>>    column widths draggable in the inspector.  I would prefer to have a
>>>    context menu that is "size to fit".  This could be potentially expensive
>>>    to calculate, so it would be user-initiated.
>>
>> I think this is more of a FastTable / GT issue than DataFrame, so maybe
>> the discussion should stay here?  (if anyone is interested :-)).
>>
>> Thanks,
>> Alistair
>>