Dear All,
I have just received a announcement for a position at INRIA Chile.
Here is an extract from the call. It is written in Spanish, however it is also open to non-spanish speaker.
"Inria Chile fue creado en Chile en 2012 por Inria (www.inria.fr) y en colaboración con 9 universidades chilenas. Cuenta con el apoyo de CORFO, que seleccionó el proyecto de Inria Chile en el marco del concurso Atracción de Centros de Excelencia Internacional para la Competitividad dedicado a desarrollar y reforzar las capacidades I+D del país.
Inria Chile desarrolla sus actividades I+D a través de una plataforma de desarrollo de acciones aplicadas, que busca proponer soluciones a desafíos económicos y sociales para Chile, tal como energía, en particular energías renovables, recursos naturales y “ciudades inteligentes”. También se está trabajando en temas aplicados como desarrollo sustentable, gestión de catástrofes naturales o el desarrollo de tecnologías avanzadas para la astronomía.
Buscamos a un postdoc interesado en trabajar part-time en estrecho vínculo con un equipo de desarrollo que lleva a cabo una de estas acciones. Las competencias requeridas son particularmente en las áreas de: aprendizaje, datos masivos, redes de sensores, visualización interactiva. Esta lista no es exhaustiva.”
If you have a PhD and are interested, please contact me!
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Roassal
New issue 1107 by alexandr...(a)gmail.com: problem with centring the view on
the elements
https://code.google.com/p/moose-technology/issues/detail?id=1107
I have to manually press the center button. Would be great to have this
automatically.
From Andrei Chis:
Right now Glamour does not offer a solution for sending notifications when
a morph is added to another morph, as the actual adding of a morph is done
in morphic. However morphic calls #noteNewOwner: on the TRMorph the first
time it has been added to a new morph (or when the owner of a morph
changes). Implementing TRMorph>>noteNewOwner: like below would
automatically shrink and center the canvas to the available space of the
parent every time TRMorph is added to a new morph. Though I'm not sure this
is something you might want all the time. I could add an option in glamour
that could be set then on TRMorph.
noteNewOwner: aMorph
self trachelCanvas focusOnCenterScaled. self signalUpdate
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Roassal
New issue 956 by usman.bh...(a)gmail.com: Problem of focus with GLM-Roassal
http://code.google.com/p/moose-technology/issues/detail?id=956
The focus is not correct in visualizations created with GLM-Roassal: The
focus is centered on the lower right part of the diagram. So zooming-in
hides the upper-left part of the diagram.
To reproduce:
Moose Finder -> a-Moose-Model -> all packages -> visualize -> Dependencies
(cycles) -> zoom-in.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Status: New
Owner: ----
CC: alexandr...(a)gmail.com
Labels: Type-Enhancement Priority-Medium Component-Roassal Milestone-5.0
New issue 1004 by tu...(a)tudorgirba.com: Roassal should offer circular
treemaps
http://code.google.com/p/moose-technology/issues/detail?id=1004
Rectangle treemaps are nice, but the still make it difficult to understand
deep nesting. Circular treemaps do a better job there.
It should not be hard to extend the TreeMapBuilder to support this.
See here:
http://lip.sourceforge.net/ctreemap.html
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Hi!
I have slightly improved the composite shape to enable text to be inserted in an ellipse. I am surprised to have wait for so long before adding this.
This fixes Issue 915 (https://code.google.com/p/moose-technology/issues/detail?id=915)
-=-=-=-=-=-=-=-=-=-=-=-=
v := RTView new.
s := RTEllipse new + (RTLabel new text: #name).
s allOfSameSize.
es := s elementsOn: Collection withAllSubclasses.
es @ RTDraggable.
RTEdgeBuilder new
view: v;
elements: es;
connectFrom: #superclass.
v addAll: es.
RTClusterLayout on: es.
v
-=-=-=-=-=-=-=-=-=-=-=-=
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 915 by cunningh...(a)gmail.com: Roassal Mondrian - Circle with Text
obscures text
http://code.google.com/p/moose-technology/issues/detail?id=915
I want to draw a node in the diagram with a circle (actually, an ellipse)
around it, which works. However, the circle obscures part of the text. If
the text is multi-line, it obscures quite a bit, in fact.
File in the attached extension to ROMondrianExmaple, then run:
ROMondrianExample new labeledCircle
You should see the issue.
Latest Moose Suite 4.7, windows platform.
Labels: Type-Enhancement
Labels: Component-Roassal
Attachments:
LabeledCircle.1.cs 582 bytes
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Dear pharoers,
this year Pharo consortium (and community) is going to take part in a
Google Summer of Code event[1] as a standalone organization. This is
an opportunity to promote Pharo, get some job done and have students
paid.
Currently we are at the most important stage as we are preparing the
organization application, and hoping that we will be accepted and
granted decent amount of project slots. Everyone can help with
application by submitting ideas for student projects.
Current list can be found at:
https://github.com/pharo-project/pharo-project-proposals/blob/master/Topics…
It is in STON format, and result is being generated at: http://gsoc.pharo.org/
Please add your ideas following the format of existing projects and
open a pull request with them (you will need a github account).
Preferably submit ideas with possible mentors, but if none are
available at the moment ideas without mentors are also welcome.
The template to submit projects is :
PharoTopic new
title: 'The name of your project;
contact: 'email address';
supervisors: 'Supervisors names';
keywords: 'keywords separated by spaces;
context: 'a description of the context of the project';
goal: 'description of the goal';
level: 'Beginner or Intermediate or Advanced';
yourself.
We will need a lot of projects/idea before February 20th 2015, the
deadline for applying to GSOC 2015.
Do not hesitate to ask questions. Administrators of this year’s
application are Serge Stinckwich <serge.stinckwich(a)gmail.com> and
Yuriy Tymchuk <yuriy.tymchuk(a)me.com>
If you don't know how to edit the list, please send your project
following the template to the administrators.
[1]: https://www.google-melange.com/gsoc/homepage/google/gsoc2015
Cheers,
--
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/
Hi!
I am doing some experiment to get object-centric debugging.
How can I add a new menu entry in this menu:
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
is it possible to embed (any) editable text field inside Roassal?
I managed to add the editor morph inside Trachel's athens canvas, however
there is no way I can access it... my guess is that TRMorph takes all the
events, or drawing the morph on the canvas destroys something.
I tried it with PluggableTextFieldMorph (shows the border of the edit
field, but no text), and TxTextEditorMorph (shows text).
Is there any way around this? Adding the morph inside AthensWrapMorph works
correctly, so my guess is that TRMorph must be doing something... perhaps I
should also add it as a submorph of TRMorph somehow?
My testing code follows:
------------------------------------------------
"opening the canvas and adding custom shape"
trCanvas := TRCanvas new.
text := SBEditableTextShape new.
trCanvas addShape: text.
trCanvas open.
------------------------------------------------
------------------------------------------------
"content of SBEditableTextShape - same as the attachement"
'From Pharo4.0 of 18 March 2013 [Latest update: #40470] on 1 February 2015
at 10:13:04.069249 pm'!
TRShape subclass: #SBEditableTextShape
instanceVariableNames: 'txMorph txModel wrapMorph textMorph'
classVariableNames: ''
poolDictionaries: ''
category: '_Sandbox'!
!SBEditableTextShape methodsFor: 'drawing' stamp: 'PeterUhnak 2/1/2015
22:10'!
drawOn: aCanvas
" aCanvas fullDrawMorph: textMorph."
aCanvas fullDrawMorph: txMorph.! !
!SBEditableTextShape methodsFor: 'initialization' stamp: 'PeterUhnak
2/1/2015 22:07'!
initialize
| string |
super initialize.
string := 'quick brown fox jumps over the lazy dog'.
txModel := string asTxModel.
txMorph := TxTextEditorMorph text: txModel.
txMorph extent: 150 @ 50.
textMorph := PluggableTextFieldMorph new.
textMorph extent: 150 @ 50.
textMorph setText: string.
textMorph ghostText: 'ghost text'.! !
------------------------------------------------
Any help is appreciated,
Peter
Hi!
Yesterday I have downloaded the last version of Moose, and I was surprised to see what I feel are functionality regression.
- If I open a Playground, and I type 3 times the key “[“ then I end up with "[ [ [ ] ] ]” whereas I would expect to have “[[[]]]”. Since I often use the playground to edit pillar code, this is not cool.
- When I use spotter, and started to type something, when the spotter window is refreshed, the selection goes at the first item, which is not great if I started to move down the selection bar and I get a refresh.
Am I the only one to see this?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi, at the moment border width is absolute (or constant), so if scale the picture border width remains the same. Is it possible to have a border width that scales? I.e. if you have a box of size 20 and border of size 2 then when box is zoomed to 10px the border will have the width of 1px?
Uko
Hi!
I am now digging into Pillar. My goal is to be able to insert Roassal script and having it executed.
Scripts provided within [[[ ]]] may be evaluated using the variable ‘eval=true’. Here is an example:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
PRHTMLWriter defaultConfigurations anyOne
inputString: '100 factorial =
[[[eval=true
stream nextPutAll: 100 factorial asString
]]]';
outputFile: 'myFirstPillarExport.html' asFileReference;
export
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
‘stream’ is a hardcoded variable name which represents the stream on which you have to write your result. What you write in stream is pillar-friendly. This means you can write something like:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
PRHTMLWriter defaultConfigurations anyOne
inputString: '100 factorial =
[[[eval=true
stream nextPutAll: ''""'', 100 factorial asString, ''""''
]]]';
outputFile: 'myFirstPillarExport.html' asFileReference;
export
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
I have tried to insert some Roassal visualization, and it works pretty well.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
PRHTMLWriter defaultConfigurations anyOne
inputString: '
!!Example of a factorial
50 factorial =
[[[eval=true
stream nextPutAll: ''""'', 100 factorial asString, ''""''.
]]]
!!Some Roassal visualizations
Here is a small Mondrian example
[[[eval=true
b := RTMondrian new.
b nodes: (1 to: 100).
b layout grid.
b build.
aView := b view.
RTHTML5Exporter new insert: aView named: ''Roassal test'' inPillarStream: stream
]]]
Another example with Grapher this time:
[[[eval=true
b := RTGrapher new.
b extent: 300 @ 200.
ds := RTStackedDataSet new.
ds interaction popupText.
ds barShape width: 10.
ds points: #(4 5 1 -2 5 6).
b add: ds.
"b axisX noLabel; noTick.
"
b build.
RTHTML5Exporter new insert: b view named: ''A Graph'' inPillarStream: stream
]]]
';
outputFile: 'myFirstPillarExport.html' asFileReference;
export
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Pillar is very well done! Congrats to the authors!
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
DiffMorph has a concept of contextClass that it uses to highlight method sources that are diffed. I’ve added a support of this feature to the glamour presentation and renderer.
Please let me know if it is ok and if I can contribute like this or there is a more formal process.
Uko
I’ve removed explicit white color form the renderer, as on the dark theme it wasn’t working well. Let me know if this is fine, because I thought that maybe a color from theme should be specified, but I didn’t find any colors in other renderers.
Uko
Hi,
Since the work on the integration of PPContext in PetitParser, there is
significant performance degradation. I have already mentioned that on
simple grammar the factor is about 2. But on complex grammar (for example,
our proprietary parser for 4D language ), we have seen that degradation is
goes well beyond this factor. So, for example, for 800K lines that we parse
in under 10 minutes without PPContext work, with the latest version it goes
beyond 2h.
I have not been able to reproduce my case on simple grammars. May be we can
have some benchmarks using open source parsers and large code bases (e.g.
PP Java Parser on JHotDraw or ArgoUML).
Currently, I circumvent this issue by using PP v1.51 but I can provide
relevant feedback and run benches on any improvements.
regards.
Usman
Hi,
I tried to download and use Moose 5.0 on a 10.6 OS X machine but hit some
issues on the way.
So far I did not try anything related to Moose 5.1.
My first attempt was to download from here:
http://moosetechnology.org/#install
However, all Moose links point to non existent files redirecting me to a
'Not Found' HTML page.
Then I followed the link to the Pharo VM download (http://pharo.org/download),
downloaded
the OS X package by clicking on the OS X 'button', and executed the Gofer
statement from the website.
Everything downloaded and installed fine.
But when I tried to run any of the Roassal demos a debugger window opened
complaining about some cairo method which could not be found.
I know that there is ongoing work in the Pharo VM towards a Cairo based
backend,
but unfortunately the Pharo VM I downloaded does not include it.
It would be nice if you could provide me with any hints on how to get a
working Moose/Roassal image.
Also let me know if there is a another/better list where I should ask such
questions.
Many thanks,
Manfred
How would be ported this code using RTCharterBuilder
| b |
b := RTCharterBuilder new.
b extent: 500 @ 200.
b points: keys.
b stackX.
b allY: [ : each | aBag occurrencesOf: each ].
b histogramWithBarTitle: #yourself.
b axisY.
b newAxisConfiguration plain.
b axisXTitled: 'MyTitle'.
b axisX.
b build.
^ b
using RTGrapher?
Because some methods are missing (#points: #stackX, etc) in the latest
version of Roassal2.
Hernán
Hi,
Now in the moose build there are a lot of undeclared warnings:
https://ci.inria.fr/moose/job/moose-5.1/117/console
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).
Cheers,
Andrei
This looks great!
What do you use to handle the interaction?
Doru
On Wed, Feb 18, 2015 at 9:41 PM, Pierre CHANSON <chans.pierre(a)gmail.com>
wrote:
> Hi all,
>
> here is a short video to present how to integrate Roassal graphics in your
> Seaside application !
>
> https://vimeo.com/119983485
>
> http://smalltalkhub.com/#!/~PierreChanson/RoassalSeaside
> cheers,
>
> Pierre
>
--
www.tudorgirba.com
"Every thing has its own flow"
Hello,
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.
Cheers,
Alejandro
Hello Peter,
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.
Vincent
De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] 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?
Clément
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.
Thanks
Peter Kenny
From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.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?
Hey,
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:peter@pbkresearch.co.uk>>:
Hello
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
Peter Kenny
________________________________
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.
FYI
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.
Uko
Hello
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.
Thanks
Jan Blizničenko
Hi,
the jenkins slaves are offline again.
I’ve resurrected the moose ones, but I don’t have rights to manage pharo-contribution. Can someone do that please?
Uko