Re: [Pharo-users] Re: Call for action for Roassal
by Peter Uhnák
On Wed, Feb 24, 2016 at 11:03 AM, Martin Bähr <
mbaehr(a)email.archlab.tuwien.ac.at> wrote:
> Excerpts from Peter Uhnák's message of 2016-02-24 10:35:05 +0100:
> > In any case, I wrote a simpler layout delegator in Roassal that delegates
> > the layouting to graphviz and it works reasonably well, so I could
> probably
> > add it to Roassal (you however need graphviz installed and it would add
> > another dependency to Roassal, which I'm not so keen on).
>
> how does that work? does it ask graphviz for the position of the nodes and
> then
> recreate that in roassal?
>
Yes, I generate .dot file that describes the nodes I want the layout for
(that includes the dimensions of it), and then the .dot file is passed to
GraphViz… from there I parse the generated SVG file (they can also output
other formats like txt, or xml) and move the Roassal nodes.
>
> > Maybe also OGDF (http://ogdf.net/doku.php) could be used if you are ok
> with
> > GPL… they have their own graph format so there could be some interaction.
>
> this would work the same as with graphviz as an additional dependency on
> ogdf, right?
>
GraphViz is good enough for generic graphs, but OGDF is well-founded and
much more powerful layouting library. However C++ coding is required if one
wants to use it.
Peter
7 years, 7 months
Addling lines to RTUMLClassBuilder
by Hernán Morales Durand
Hello,
I am using Moose 6.0 to generate an UML diagram for a paper.
In the UML diagram below is there a way to specify a Line between the
compilationContext instance variable and CompilationContext class box?
| b |
b := RTUMLClassBuilder new.
b
instanceVariables: #instVarNames;
methodselector: #selector;
methodsNames: #();
attributeselector: #yourself.
b attributeShape color: Color black.
b methodShape color: Color black.
b classNameShape color: Color black.
b lineShape color: Color black.
b boxShape borderColor: Color black.
b
addObjects: { Compiler . CompilationContext };
treeLayout;
build;
view
Hernán
7 years, 7 months
GT Presentation: Auto-Fit Morph
by Sean P. DeNigris
For large images, it can really be a drag to have ImageMorphs always open at
the full size of the form. I added Fit and Fit-Width actions to my Morph
presentations, but I can't figure out how to hook in to have Morphs open
Fit-Width by default. As a hack, I was thinking of trying to fire the action
when the presentation comes up, but I'm not sure how to do that either! Any
suggestions?
I have:
gtInspectorFormIn: composite
<gtInspectorPresentationOrder: 0>
^ composite morph
title: 'Morph';
display: [ self asMorph ]
The morph looked like this:
<http://forum.world.st/file/n4877731/Screenshot_2016-02-15_21.png>
But I want to be fit inside the presentation pane, with no parts cut off.
Here's a screencast of the manual process which I'd like to automate:
https://youtu.be/EsJA0dp6k8c
Thanks in advance!
-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/GT-Presentation-Auto-Fit-Morph-tp4877731.html
Sent from the Moose mailing list archive at Nabble.com.
7 years, 7 months
Fwd: GSOC 2016
by Serge Stinckwich
Dear all,
this is a reminder ! The deadline is Feb 19th 2016.
Yuko&Serge, Pharo GSOC 2016 co-administrators
PS: We are looking for more co-administrators to help us finish Pharo
application.
Please ask me in PM.
================================================
Dear pharoers,
this year Pharo consortium (and community) is going to take part in the
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.
I reuse the list of the last year :
https://github.com/pharo-project/pharo-project-proposals/blob/master/Topi...
It is in STON format, and result will be generated at: http://gsoc.pharo.org/
Please add (or update) 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 19th 2016, the
deadline for applying to GSOC 2016.
Do not hesitate to ask me questions.
If you don't know how to edit the list, please send your project description
following the template to me.
[1] https://summerofcode.withgoogle.com/
--
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/
7 years, 7 months
Moose 6.0 Roassal crashing
by Sebastian Heidbrink
Hi!
I already filed a bug on this but I am wondering if somebody here on the
list might have a temporary workaround.
I just downloaded the most current Moose-6.0 image and I also use the
most recent SpurVM.
On Windows 7 and 8 the PharoVM crashes once one moves the mouse pointer
of a Roassal view containing e.g. a graph.
Is there a particular built I could load to make this work until a fix
might be published?
Thanks
Sebastian
7 years, 7 months
[Roassal2] RTResizable leaves callbacks with each selection
by Jan Blizničenko
Hello again
This time I bring a problem without offering solution because I haven't
managed to look deep enough into it yet.
RTResizable leaves callbacks for handles on the selected element even afrer
deselection (calling RTResizable>>#removeHandles). It means that following
screnario happens:
- I click on element
-> handles are created and their callbacks are created
- I click anywhere else
-> handles are removed but their callbacks are not removed
- I click on that element again
-> handles are created again but new callbacks are created
...etc...
So with each select, new callbacks are created and are added to previous
ones.
Those callbacks are created in RTResizable>>#showHandles -
RTResizable>>#attachHandle:toCorner: - RTConstraint>>#stick.
I did not notice any performance (or other) issues caused by this in Roassal
resizableExample, but it causes performance problem in few (but important)
cases in our DynaCASE (I am not sure why only there).
Jan
--
View this message in context: http://forum.world.st/Roassal2-RTResizable-leaves-callbacks-with-each-sel...
Sent from the Moose mailing list archive at Nabble.com.
7 years, 7 months
Fwd: GSOC 2016
by Serge Stinckwich
---------- Forwarded message ----------
From: Serge Stinckwich <serge.stinckwich(a)gmail.com>
Date: Thu, Feb 11, 2016 at 2:02 PM
Subject: GSOC 2016
To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org>
Dear pharoers,
this year Pharo consortium (and community) is going to take part in the
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.
I reuse the list of the last year :
https://github.com/pharo-project/pharo-project-proposals/blob/master/Topi...
It is in STON format, and result is being generated at: http://gsoc.pharo.org/
Please add (or update) 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 19th 2016, the
deadline for applying to GSOC 2016.
Do not hesitate to ask me questions.
If you don't know how to edit the list, please send your project description
following the template to me.
[1] https://summerofcode.withgoogle.com/
Regards,
--
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/
--
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/
7 years, 7 months
