How would be ported this code using RTCharterBuilder
| b |
b := RTCharterBuilder new.
b extent: 500 @ 200.
b points: keys.
b allY: [ : each | aBag occurrencesOf: each ].
b histogramWithBarTitle: #yourself.
b newAxisConfiguration plain.
b axisXTitled: 'MyTitle'.
Because some methods are missing (#points: #stackX, etc) in the latest
version of Roassal2.
Now in the moose build there are a lot of undeclared warnings:
I will start fixing them once jenkins starts working again. Most of them
come because of the order in which packages are loaded (a test package is
loaded before the code that it tests).
I have been using Moose for some graph analysis and I noticed that Tarjan was a little slow. Analyzing further, I noticed that even though the complexity of Tarjan is linear, building the graph is O(n*m) where n is the number of nodes, and m is the number of edges of the graph.
This happen because Moose creates its own graph nodes using as a model my nodes, and then for building each edge of the graph it looks for the corresponding node using detect: [ :n | n model = aModel ] over the OrderedCollection of nodes.
I fixed it by replacing the nodes OrderedCollection for a Dictionary and replacing the MalTarjan>>findNode:ifAbsent: implemented with a detect:ifAbsent: by a Dictionary lookup. In my benchmark of 2 seconds before the fix, now takes 38ms, and my other experiment that I got bored of waiting after 10 hours now it takes less than 1 hour and a half.
I already committed it, the tests look fine but let me know if something goes bad.
If your are on Moose, you are using the Glamour inspector.
Can you describe more precisely the kind of items you are inspecting? Do you inspect external resources? Or use Semaphores, forks, network?
I am remembering a bug on Roassal. It used external ressources that was desallocated at image shutdown. On image relaunch, the external ressources was still pointed by a cache and the yellow cross on red appears.
By the way, behind the cross, it should be a text, can you see it?
I know that these kind of issues are very difficult to reproduce but if you can do it on a fresh image, it will be easier for us to help you ;)
I cross-posted to the Moose mailing list where people are more aware of this kind of issues.
De : Pharo-users [mailto:email@example.com] De la part de PBKResearch
Envoyé : mercredi 18 février 2015 17:32
À : 'Any question about pharo is welcome'
Objet : Re: [Pharo-users] What happens to saved inspectors?
I am not sure, but I think Moose uses the Glamour inspector. You get exactly the same inspector whether you select ‘Inspect’ or ‘Explore’ from the world menu. As you click on an item in the current display, a new inspector pane opens to the right showing detail of the selected item, with tabs to select the form of display – the first one is always ‘Raw’ but the others are dependent on the kind of item being displayed, e.g. if inspecting an XML document there is always a ‘Tree’ option. I think that sounds like Glamour, doesn’t it?
The main heading on the title bar is static, i.e. it always shows the item you originally inspected. When there are multiple inspector panes open, each one has its own title below the main window title, showing the item that was clicked to open it. In this case, the title of the first inspector pane, which is the same as the main window title, is also replaced by the red error display, but the titles of the other inspector panes are OK.
Hope this helps. If any more detail would be helpful, let me know.
From: Pharo-users [mailto:firstname.lastname@example.org] On Behalf Of Clément Bera
Sent: 18 February 2015 11:37
To: Any question about pharo is welcome
Subject: Re: [Pharo-users] What happens to saved inspectors?
Inspectors are different between Moose and Pharo 3. Can you precise, are you using the Glamour inspector, the EyeInspector or the old Morphic inspector ?
I have never seen that in Pharo. Are your titles dynamic (I mean, when the object changes, can your title change ?) ?
2015-02-18 11:35 GMT+01:00 PBKResearch <peter(a)pbkresearch.co.uk<mailto:email@example.com>>:
I am using Moose 5, which is essentially Pharo 3, downloaded late December 2014. I have a development project which mainly consists of a collection of workspaces and inspectors (I really do intend to turn it into a properly structured set of classes one day!). I have noticed that, whenever I save an image with some inspectors open and then reopen the image, the title bars of the inspectors have become red rectangles with a cross superimposed. Often I can work out what the title should be and carry on, but in many cases all I can do is close down the inspector and reopen it. Is this a known problem, and is there any way to work round it?
Thanks for any help
Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
I’ve switched content of "zoom in" and "zoom out” icons in Glamour-Morphic-Theme-YuriyTymchuk.200. Before that when you’ve pressed on a magnifying glass with “+” sign it zoomed out, and this was awkward.
We use Roassal 2 for visual side of a project we are working on - a
diagram modelling tool (like enterprise architect) and we came to a
specific need. There are notations like UML which need heads/arrows on
both ends of a single line.
As far as I understand the roassal code, line decorations are encoded to
be at the "to" end and can't be on the other one.
We would use help with this problem.
> Begin forwarded message:
> Date: 18 Feb 2015 11:58:29 CET
> From: Emmanuel Jeanvoine <emmanuel.jeanvoine(a)inria.fr>
> To: ci-announces(a)inria.fr
> Subject: Re: [ci-announces] CloudStack upgrade
> Reply-To: Emmanuel Jeanvoine <emmanuel.jeanvoine(a)inria.fr>
> On Fri, 06 Feb 2015, Emmanuel Jeanvoine wrote:
>> Dear users,
>> CloudStack will be upgraded to the 4.4.2 version on 2/11/14. This new
>> version has several stability improvements and is required to prepare the
>> next evolution of the service related to the MacOSX support.
>> As a consequence, the service is planned to be stopped on 2/10/14 at 5pm.
>> In order to avoid any issue, you are strongly encouraged to shutdown the
>> Jenkins instances and the VM of your projects before that.
>> For those who may be interested, more details will be given there:
>> Thank you for your understanding,
>> Emmanuel Jeanvoine Research Engineer
>> Inria Nancy - Grand Est Office B118
>> http://www.inria.fr/nancy Tel +33 3 54 95 86 21
> Dear users,
> Unfortunately the CloudStack maintenance is still not finished. It was not
> possible to create new slave, and slaves have been stopped unexpectedly
> yesterday evening. In order to allow the IT team to investigate the issue
> serenely and to avoid any other issue, it is better to shut down the whole
> Information will be put one the event page (https://wiki.inria.fr/ciportal/Event_20150211_cs)
> when received from the IT team.
> We are very sorry for the inconvenience.
OK, try making a proposal then, http://gsoc.pharo.org has the instructions and the current list, you probably know more about data science than I do.
> On 18 Feb 2015, at 10:53, Andrea Ferretti <ferrettiandrea(a)gmail.com> wrote:
> I am sorry if the previous messages came off as too harsh. The Neo
> tools are perfectly fine for their intended use.
> What I was trying to say is that a good idea for a SoC project would
> be to develop a framework for data analysis that would be useful for
> data scientists, and in particular this would include something to
> import unstructured data more freely.
> 2015-02-18 10:39 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>:
>> Well, you are certainly free to contribute.
>> Heuristic interpretation of data could be useful, but looks like an addition on top, the core library should be fast and efficient.
>>> On 18 Feb 2015, at 10:35, Andrea Ferretti <ferrettiandrea(a)gmail.com> wrote:
>>> For an example of what I am talking about, see
>>> I agree that this is definitely too much options, but it gets the job
>>> done for quick and dirty exploration.
>>> The fact is that working with a dump of table on your db, whose
>>> content you know, requires different tools than exploring the latest
>>> opendata that your local municipality has put online, using yet
>>> another messy format.
>>> Enterprise programmers deal more often with the former, data
>>> scientists with the latter, and I think there is room for both kind of
>>> 2015-02-18 10:26 GMT+01:00 Andrea Ferretti <ferrettiandrea(a)gmail.com>:
>>>> Thank you Sven. I think this should be emphasized and prominent on the
>>>> home page*. Still, libraries such as pandas are even more lenient,
>>>> doing things such as:
>>>> - autodetecting which fields are numeric in CSV files
>>>> - allowing to fill missing data based on statistics (for instance, you
>>>> can say: where the field `age` is missing, use the average age)
>>>> Probably there is room for something built on top of Neo
>>>> * by the way, I suggest that the documentation on Neo could benefit
>>>> from a reorganization. Right now, the first topic on the NeoJSON
>>>> paper introduces JSON itself. I would argue that everyone that tries
>>>> to use the library knows what JSON is already. Still, there is no
>>>> example of how to read JSON from a file in the whole document.
>>>> 2015-02-18 10:12 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>:
>>>>>> On 18 Feb 2015, at 09:52, Andrea Ferretti <ferrettiandrea(a)gmail.com> wrote:
>>>>>> Also, these tasks
>>>>>> often involve consuming data from various sources, such as CSV and
>>>>>> Json files. NeoCSV and NeoJSON are still a little too rigid for the
>>>>>> task - libraries like pandas allow to just feed a csv file and try to
>>>>>> make head or tails of the content without having to define too much of
>>>>>> a schema beforehand
>>>>> Both NeoCSV and NeoJSON can operate in two ways, (1) without the definition of any schema's or (2) with the definition of schema's and mappings. The quick and dirty explore style is most certainly possible.
>>>>> 'my-data.csv' asFileReference readStreamDo: [ :in | (NeoCSVReader on: in) upToEnd ].
>>>>> => an array of arrays
>>>>> 'my-data.json' asFileReference readStreamDo: [ :in | (NeoJSONReader on: in) next ].
>>>>> => objects structured using dictionaries and arrays