Alexandre,
Sure, I'm implementing pie charts and histograms for Dictionary also. Let me know what next steps might be for properly finishing the existing histogram implementation...
Brennan
-----Original Message-----
From: Moose-dev <moose-dev-bounces(a)list.inf.unibe.ch> On Behalf Of moose-dev-request(a)list.inf.unibe.ch
Sent: Thursday, March 29, 2018 5:00 AM
To: moose-dev(a)list.inf.unibe.ch
Subject: Moose-dev Digest, Vol 139, Issue 14
Send Moose-dev mailing list submissions to
moose-dev(a)list.inf.unibe.ch
To subscribe or unsubscribe via the World Wide Web, visit
https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.list.…
or, via email, send a message with subject or body 'help' to
moose-dev-request(a)list.inf.unibe.ch
You can reach the person managing the list at
moose-dev-owner(a)list.inf.unibe.ch
When replying, please edit your Subject line so it is more specific than "Re: Contents of Moose-dev digest..."
Today's Topics:
1. Re: RTHistorgramSet does not implement xScale/yScale
(Alexandre Bergel)
----------------------------------------------------------------------
Message: 1
Date: Wed, 28 Mar 2018 22:01:47 -0300
From: Alexandre Bergel <alexandre.bergel(a)me.com>
To: Moose-related development <moose-dev(a)list.inf.unibe.ch>
Subject: [Moose-dev] Re: RTHistorgramSet does not implement
xScale/yScale
Message-ID: <C5AEA9B4-82C4-490D-B56E-D68AAEB74B75(a)me.com>
Content-Type: text/plain; charset=us-ascii
Hi Brennan,
The implementation of the histogram was never properly finished.
It would be fantastic to build a new implementation. It should not be that hard actually.
We could have discussion if you wish to help :-)
Cheers,
Alexandre
> On Mar 23, 2018, at 6:43 PM, Brennan Cleveland <cluvius2000(a)hotmail.com> wrote:
>
> Hi,
>
> The 'histogram' method on SequenceableCollection added by Roassal2 fails due to xScale/yScale not being implemented on RTHistogramSet.
>
> I added implementations of both as:
>
> ^ RTLinearTransformation instance.
>
> to RTHistogramSet which at least gets a histogram working. I'm not sure what the proper fix actually is. I thought maybe adding this implementation on RTAbstractDataset would be the right thing to do...
>
> Thanks,
>
> Brennan
>
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)list.inf.unibe.ch
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> list.inf.unibe.ch%2Flistinfo%2Fmoose-dev&data=02%7C01%7C%7C35b54e25b3a
> 7452e761a08d5955bd97b%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636
> 579144077353793&sdata=6dx4HkbAFMV15PYD8ePw00zRIPAR8%2BvesZ8Z8%2Bg8KF8%
> 3D&reserved=0
------------------------------
Subject: Digest Footer
_______________________________________________
Moose-dev mailing list
Moose-dev(a)list.inf.unibe.ch
https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.list.…
------------------------------
End of Moose-dev Digest, Vol 139, Issue 14
******************************************
Hello Moosers,
This is a first for me: I wanted to extend the inspector in a new way and I
was able to work out how to do that myself from reading the code :). So I
am posting not a question but a tip!
If you want to add a Search button to one specific tabbed view in the
inspector (as opposed to above on the object as a whole) then you can do it
like this:
composite list "etc"
addAction: someObject gtInspectorActionSpot;
...
and then you will get a little Search button inside this inspector view
that opens an appropriately-sized Spotter on someObject.
I was surprised not to find a 'GTSpotter openOn: someObject' convenience
method. Should there be one? There is 'on:' but that leaves you to work out
how to open the spotter window with an appropriate size.
Cheers!
-Luke
Hi all -- I'm not sure if I missed it, but does Moose explicitly model the
<<creates>> relationship of UML between two classes, e.g.,
Based on
http://themoosebook.org/book/index.html#h1thefamixfamilyofmeta-models I
found Entity -> SourcedEntity -> Association -> {Access, Invocation,
Inheritance, Reference}. In Moose, I can see outgoingInvocations on methods
of a class contain "new X" for all the X that a class creates, but I
wondered if there's a more efficient way.
Cheers!
Is there an easy way to make a GLM table column right-justified?
I have some numeric columns and I think they would be easier to read if
right-justified.
I am also still looking for a way to use a fixed-width font for various
glamorous components like lists, tables, and text. This would help me to
present semi-structured data that doesn't *quite* fit into uniform columns
in a readable way. Is there a way to do that?
Thanks!
-Luke
Hoi!
Suppose that my GTInspector extension method fails for some interesting
reason. How should I present an error message to the user?
I'm am especially thinking of cases where I am spawning a Unix command
behind the scenes and I want to show the (possibly long) output of the
command to the user. Could happen either in an inspector extension method
or also in a "Go" action of the inspector.
Tips would be much appreciated :).
Hi,
The 'histogram' method on SequenceableCollection added by Roassal2 fails due to xScale/yScale not being implemented on RTHistogramSet.
I added implementations of both as:
^ RTLinearTransformation instance.
to RTHistogramSet which at least gets a histogram working. I'm not sure what the proper fix actually is. I thought maybe adding this implementation on RTAbstractDataset would be the right thing to do...
Thanks,
Brennan
Hello,
Is there a way to set a default selection to a list presentation? so that
when I open the browser, the morphic list has already a value selected.
I tried that:
|tmpBrowser|
tmpBrowser := GLMTabulator new.
tmpBrowser row: #list.
tmpBrowser transmit to: #list; andShow: [:a |
a list
display: [:input | input];
selection: #a;
yourself
].
tmpBrowser openOn: #( b c d v a d f r).
but the list still open with nothing selected