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
Hi,
Alex Syrel, Andrei Chis and I are happy to announce a new addition to the
Glamorous Toolkit:
GTSpotter, a novel interface for spotting objects.
GTSpotter has two goals:
- Provide a uniform yet moldable interface that can work on any object, and
- Handle searching through arbitrary levels of object nesting.
We think this will have a significant impact on the development workflow in
Pharo.
Here is a couple of screenshots:
[image: Inline image 2] [image: Inline image 1] [image: Inline image 3]
A trailer is available here:
https://www.youtube.com/watch?v=PhSmjR3NOlU
A detailed description is available here:
http://www.humane-assessment.com/blog/introducing-gtspotter
It works already in Pharo 3.0 and can be played with by following the
instructions from:
http://gt.moosetechnology.org
Please let us know what you think.
Enjoy,
The Glamorous Team
Hi,
apparently we broke MorphicRoassalAdapter when cleaning Spec, I attached a
fix.
However my question is - does anybody (except us) actually use the
Roassal2Spec package? Because otherwise we could clean it a bit. For
example I'm not sure of the use case of script:/lastEvent:.
Peter
Hello,
I would like to know why the Meta Editor in the Moose panel and the implementing class GLMMagrittePresentation have been removed from the Moose 5.1 image because I want to annotate a model with it.
If it is not possible to do it work for Moose 5.1, is there an equivalent?
Thanks in advance,
Cheers
Vincent
________________________________
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.
… if we have XML, why not CSV and JSON? This is all wide-spread standard
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hello
Sice I am still playing with composite shapes, I found another problem, in
addition to incorrect behavior of calling update onto it.
This time I found that composite shapes do not send callbacks in lots of
cases. Example:
| compo ellipse |
compo := ((RTBox new size: 50; color: Color red; yourself) + RTBox new)
element.
compo @ RTDraggable.
ellipse := RTEllipse new size: 20; color: Color blue; element.
TRConstraint stick: ellipse below: compo.
(RTView new) add: compo; add: ellipse; open.
When I drag the composite shape, ellipse does not move, although it should.
Jan
--
View this message in context: http://forum.world.st/Roassal-TRCompositeShape-not-sending-callbacks-tp4814…
Sent from the Moose mailing list archive at Nabble.com.
Hello
We use Roassal on Pharo 4, but we ran across another compatibility issue.
On Pharo 4, MouseWheelEvent class got a little rework. It does not use
symbols #up and #down as direction anymore, not even via accessors.
TRMouseWheelEvent copies this direction, so because RTZoomableView looks for
these symbols, it is no longer working on Pharo 4 (mouse wheel now just
moves camera, but does not change scale).
More info about this Pharo 4 change you might find here:
http://forum.world.st/MouseWheelEvent-direction-in-Pharo-4-tp4806863p480686…
I tried to make few changes to make it compatible in both Pharo 3 and 4.
One option is just adding two methods into TRMouseWheelEvent which convert
Pharo 4 direction to Pharo 3 direction, so only interface change is when
creating TRMouseWheelEvent, usage of this event is absolutely same.
http://www.mediafire.com/download/es70j9dko45da2b/mouseWheel_pharo3like.zip
Second option is to rework TRMouseWheelEvent in the same way MouseWheelEvent
got changed, so they will have same usage on Pharo 4, but it means even
interface of TRMouseWheelEvent changes and everything that asks for its
direction has to be changed, too.
http://www.mediafire.com/download/38lwuwr1eauuur0/mouseWheel_pharo4like.zip
Third option is to use your own solution instead of mine.
And last solution might be just ignoring it and not trying to be compatible
with both Pharo versions.
Jan Blizničenko
--
View this message in context: http://forum.world.st/Roassal2-Pharo-4-MouseWheelEvent-compatibility-tp4806…
Sent from the Moose mailing list archive at Nabble.com.
Hello
I am trying to work with composite shapes, but I encountered a problem.
Let's say I need to create a circle... and in the center of it is another,
smaller, circle with label (but I need it to be centered according to both
label and smaller circle, that's why I decided to use composite shapes
instead of RTLabelled).
I am able to create it just fine, problem is when I call update on its
RTElement. I'm not sure whether I am even supposed to do it, but I think I
should be.
I start with just the inner circle with label:
| composite view |
composite := (RTLabel new
text: 'label';
yourself)
+
(RTEllipse new
size: 10;
yourself).
composite horizontal.
element := composite element.
view := RTView new.
view
add: element;
open.
element update.
Before element update, it looks fine, but when I call update, composite
layout (horizontal) gets lost.
Let's say I can ignore this problem (which I can't), and I will try the same
thing with whole shape
| composite view subcomposite |
subcomposite := (RTLabel new
text: 'label';
yourself)
+
(RTEllipse new
size: 10;
yourself).
subcomposite horizontal.
composite := (RTEllipse new
size: 50;
color: Color transparent;
borderColor: Color black;
yourself) + subcomposite.
element := composite element.
view := RTView new.
view
add: element;
open.
element update
this time I get exception MessageNotUnderstood: TRCompositeShape>>text:on:
I will appreciate any help, either by fixing something if it is broken, or
explaining how to reach my goal the correct way.
Jan
--
View this message in context: http://forum.world.st/Roassal-2-updating-CompositeShape-tp4813359.html
Sent from the Moose mailing list archive at Nabble.com.
Dear all,
As many of you know, Grapher is a über-cool charting engine, part of Roassal.
For people who do not know what Grapher is, here is a (compelling we hope) example:
Which is obtained by the following script:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| b colors points ds pts dec lb |
b := RTGrapher new.
colors := Array with: Color red with: Color blue.
points := OrderedCollection new.
colors do: [ :c |
ds := RTStackedDataSet new.
pts := ((1 to: 100) collect: [ :i | 50 atRandom - 25 ]) cumsum.
points add: pts.
ds points: pts.
dec := RTDevVarDecorator new.
dec moveBehind;
desviation: 0.5;
color: (c alpha: 0.3);
points: pts.
ds connectUsing: (RTLine new color: (c alpha: 0.5); width: 1 ).
b add: ds.
b addDecorator: dec.
].
b axisX; axisY.
b build.
lb := RTLegendBuilder new.
lb view: b view.
colors doWithIndex: [ :c :i |
lb addColor: c text: 'Series ', i printString ].
lb build.
b view @ RTZoomableView.
b view
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
In our grand vision of making Roassal the best visualizing engine of the Universe (we also know to be modest time to time, but not today :-), Grapher will play a very important role. We would like to stabilize Grapher and make it sure it happily fits everybody needs. You can help on it:
- When you are tempted to look at the dark side of the planet (this is where R, JFreeChart, gnuplot, D3 and all their friends live), let us know. We will make sure to make you are happy again.
- Share your wishlist with us. We already have a long todo list, but your opinion does matter and will take it seriously
- we are open to contributions, which could be financial, bug fixe, enhancement, or simply encouragement.
I am very happy to be surrounded by very smart engineers. Your encouragement are making them happy :-)
Cheers,
Alexandre, in the name of the Object Profile Team
NB: sorry for the cross-list posting, but this email is very important for us, and for you we hope.
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi all,
I don’t know if this is a know issue so I am reporting it: doing a ConfigurationOfPetitParser loadDevelopment in the latest Pharo 4 (40571) breaks some things. There is a DNU on opening the playground: AnObsoleteGLMLiveStringBrick(Object)>>doesNotUnderstand: #textLogic: It’s called from GTPlayground>>codeIn: where a ref to GLMLiveStringBrick is made.
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile
