- Up arrow in R3RoassalExample>>#exampleSphereLayout ->MessageNotUnderstood:
KeyboardEvent>>direction
- R3RoassalExample examples (seemingly especially the "nice colors" ones)
intermittently crash the VM with "line 11: 58266 Abort trap: 6" to the
console (Mac 10.9.3)
-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Roassal-3D-Bugs-was-Roassal-Easel-Red-X-of-Death-tp47…
Sent from the Moose mailing list archive at Nabble.com.
Hi,
I currently use Charter which is doing nice charts for me. But I experienced some kind of bug with the scales of the chart especially if the values are negatives.
See by yourself:
[cid:image001.jpg@01CFB315.9897E410]
Here the code to draw it:
| b |
b := RTCharterBuilder new.
b extent: 400 @ 300.
b points: { 5 . 6 . 7 .-1 . -3}.
b connectDotColor: Color red.
b interaction popup.
b allY: #yourself.
b stackX.
b axisXWithNumberOfTicks: 4.
b axisYWithNumberOfTicks: 6.
b open.
b view canvas.
Did I make something wrong?
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.
I took the notes below while going through the chapter. In summary:
- maybe RTTabTable is mis-packaged?
- it's hard to keep written examples up-to-date with the code, especially
when they are not automatically tested (of course in my dreams we only have
active essays and never run into this problem, yet I digress...)
- Code comments are key for when users want to drop into the code quickly
from an example in the documentation to adapt it to our own needs
- Nagging thought (not specific to the chapter): most of the Roassal
examples I've seen illustrate procedural scripts. It might be nice to have
more OOP examples, or if the point is to target
non-programmers/Smalltalkers, at least a disclaimer saying that they're in
script form for simplicity of copy/paste or whatever, but a real-world OOP
example can be downloaded at...
Roassal Quick Start says to visualize CSV data starting with RTTabTable, but
shows the table plotted on a map, which does not fit my use case. It seems
like I should be able to use the table not-on-a-map, but I see that it’s in
the Builder-Map package, so I’m not so sure. In the end, that works out okay
because I see that it’s reused in the Timeline example.
Just as an experiment, I adapt the timeline example. Most of it is
straightforward except the send of #normalizeSize:min:max:using: which was
hardcoded and makes my data huge. I’d like to adjust it, but neither the
method nor its class (RTMetricNormalizer) has a comment and I can’t figure
it out from the example senders. Oh, well it was just an experiment…
Next up, the charting example. First hurdle:
#axisXNoLabelledWithNumberOfTicks: does not seem to exist in the system
(fresh download from the link at the start of the chapter). I shorten it to
axisXWithNumberOfTicks:, which works but the resulting chart is overcrowded
with X axis labels. The example now works, but it’s hard to figure out
what’s going on to adapt it to my use. For example, allY: is not a
meaningful name to me and there is no method comment.
HTH.
-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Quick-Start-User-Experience-tp4773949.html
Sent from the Moose mailing list archive at Nabble.com.
Roassal is sooo cool! Maybe /too/ cool?! ;-)
I'm having a hard time with RTCharterBuilder. My confusion comes from
everything appearing on the same level, kind of like Amber's html canvas
being magically changed when you enter a tag #with: block. Check out this
snippet for example:
b := RTCharterBuilder new.
...
b interaction popupText: [ :point | point someMessage ].
b points: aCollectionOfPointsOfTypeA.
b connectDotColor: Color green.
b y: [ :r | r newLikes ].
b x: [ :d | d date julianDayNumber ].
...
b interaction popupText: [ :point | point anotherMessage ].
b points: aCollectionOfPointsOfTypeB.
b connectDotColor: Color red.
b y: [ :r | r second * 50 ].
b x: [ :d | d first julianDayNumber ].
The fact that #x: and y: mean different things depending on the order of the
rest of the script is a little "too helpful" to me. I'd much rather have
things that are a property of a particular data set belong to a tangible
object. Something like:
dataSet := RTDataSet new
points: anotherCollection;
connectDotColor: Color red;
y: [ :r | r second * 50 ];
x: [ :d | d first julianDayNumber ].
b addDataSet: dataSet.
The magic confuses other not-so-magical things. Like, afterwards, I tried to
set #popupText: differently for each data set, but they all seemed to be
applied to the both data sets, and were causing errors because the type of
points were different, so I was getting DNUs. Now here was the real cost: I
wasn't sure whether #popupText: was per-chart, or there was some special
ordering necessary e.g. "#popupText: before #points:". This lead to flopping
around followed by giving up. I eventually got frustrated enough that I
hacked in an #isKindOf: in both #popupText: blocks since I couldn't delegate
the #popupText: to the point objects because it was specific to this
particular chart.
-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Chart-Builder-DSL-Too-Good-tp4773990.html
Sent from the Moose mailing list archive at Nabble.com.
Hi,
I’ve just noticed an interesting thing. When I open roassal examples and then I #fork some block, it’s not being executed. But as soon as I close examples it executes. Maybe some #yield is missing somewhere?
Uko
http://stackoverflow.com/questions/25414857/roassal-conditional-x-axis-labe…
In my chart, the x axis represents the Date. I'd like to only label the
first day of a month. Specifying a number of ticks is problematic because
they can be fractional.
What I'm looking for is something like:
someRoassalObject
if: [ :point | point date dayOfMonth = 1 ]
label: [ :point | point date mmddyyyy ]
(where points are my domain objects that respond to #date)
I did the following quick and dirty hack in the mean time:
b axisConfiguration
labelConvertion: [ :x | (Date julianDayNumber: x rounded) mmddyyyy
].
-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Conditional-X-Axis-Labeling-tp4774245.html
Sent from the Moose mailing list archive at Nabble.com.
Hello.
I implemented Voronyj diagrams for Roassal. You can read about it here: http://natalia.tymchuk.me/RTVoronyjDiagram/ .
I will be on vacation from Monday till Thursday, but it will be really cool if you can write me your opinion about this project and all your remarks.
Best regards,
Natalia
Should've started a separate thread before...
"CompiledMethod DNU #numberOfLinesOfCode"
The transformation from #numberOfLinesOfCode -> #linesOfCode seems to be
needed in many of the examples throughout Roassal & PBE2.
- RTCharterBuilder examples are broken, mostly because of this
- RTCharterBuilder>>#exampleHistogram seems to have a different problem, not
sure; but possibly redundant because there is another histogram example?
HTH
-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Roassal-Examples-Broken-tp4773942.html
Sent from the Moose mailing list archive at Nabble.com.
Hi,
is blueprint diagram only available in moose panel? Because I want to use it outside of Moose, so I wander if there is some Roassal builder for that.
Uko
Hi,
I tried to load inti profiler, but without success:
Gofer new smalltalkhubUser: 'azazael'
project: 'inti';
package: 'ConfigurationOfInti';
load.
(Smalltalk at: #ConfigurationOfInti) load.
When I run "IntiExamples new openExample" I got an error:
MessageNotUnderstood: receiver of "initializeElement:" is nil
(more in the end of the email).
I tried pharo 3, moose 5 and moose 4.9. None of these were without errors.
What am I missing?
Cheers,
Jan
THERE_BE_DRAGONS_HERE
MessageNotUnderstood: receiver of "initializeElement:" is nil
31 August 2014 12:53:37.167557 pm
VM: unix - i686 - linux-gnu - NBCoInterpreter
NativeBoost-CogPlugin-GuillermoPolito.19 uuid:
acc98e51-2fba-4841-a965-2975997bba66 May 6 2014
NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid:
acc98e51-2fba-4841-a965-2975997bba66 May 6 2014
https://github.com/pharo-project/pharo-vm.git Commit:
ef5832e6f70e5b24e8b9b1f4b8509a62b6c88040 Date: 2014-01-26 15:34:28 +0100
By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14794
Image: Pharo3.0 [Latest update: #30856]
UndefinedObject(Object)>>doesNotUnderstand: #initializeElement:
Receiver: nil
Arguments and temporary variables:
aMessage: initializeElement: a RTElement
exception: MessageNotUnderstood: receiver of
"initializeElement:" is nil
resumeValue: nil
Receiver's instance variables:
nil
RTElement(RTAnnounceableObject)>>addInteraction:
Receiver: a RTElement
Arguments and temporary variables:
anInteractionClassOrInstance: nil
Receiver's instance variables:
announcer: an Announcer
shape: a RTArc
trachelShape: a TRArcShape
attributes: a Dictionary(#sbChildren->an OrderedCollection(a
RTNode<nil(ROMondr...etc...
view: nil
model: nil(IntiExamples) >> openExample
isFixed: false
connectedEdges: nil
RTElement(RTAnnounceableObject)>>@
Receiver: a RTElement
Arguments and temporary variables:
anInteractionClassOrInstance: nil
Receiver's instance variables:
announcer: an Announcer
shape: a RTArc
trachelShape: a TRArcShape
attributes: a Dictionary(#sbChildren->an OrderedCollection(a
RTNode<nil(ROMondr...etc...
view: nil
model: nil(IntiExamples) >> openExample
isFixed: false
connectedEdges: nil
[ :i | el @ i ] in RTSunburstNodeVisitor>>createArc
Receiver: a RTSunburstNodeVisitor
Arguments and temporary variables:
el: a RTElement
arc: a RTArc
auxArc: 360
auxRadius: 45
i: nil
Receiver's instance variables:
arcs: an OrderedCollection()
lines: an OrderedCollection()
node: a RTNode<nil(IntiExamples) >> openExample>
builder: a RTSunburstBuilder
radialSpacing: 5
angularSpacing: 0
interactions: an OrderedCollection(RTPopup nil MTInteraction)
weightBlock: [ :n | 1 ]
OrderedCollection>>do:
Receiver: an OrderedCollection(RTPopup nil MTInteraction)
Arguments and temporary variables:
aBlock: [ :i | el @ i ]
index: 2
Receiver's instance variables:
array: {RTPopup. nil. MTInteraction. nil. nil. nil. nil. nil.
nil. nil}
firstIndex: 1
lastIndex: 3
RTSunburstNodeVisitor>>createArc
Receiver: a RTSunburstNodeVisitor
Arguments and temporary variables:
el: a RTElement
arc: a RTArc
auxArc: 360
auxRadius: 45
Receiver's instance variables:
arcs: an OrderedCollection()
lines: an OrderedCollection()
node: a RTNode<nil(IntiExamples) >> openExample>
builder: a RTSunburstBuilder
radialSpacing: 5
angularSpacing: 0
interactions: an OrderedCollection(RTPopup nil MTInteraction)
weightBlock: [ :n | 1 ]
