Moose-dev March 2016

moose-dev@list.inf.unibe.ch

19 participants
25 discussions

by Alexandre Bergel

Hi! We have an opportunity for doing a postdoc in Chile, in the field of software engineering and/or data visualization. I could provide a lengthy description about living in Chile, and its fantastic food, latin atmosphere, and gorgeous nature. But I will surely be far from the truth. If you want to know more about this possibility, get in touch! Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

8 years, 9 months

Re: [Pharo-users] Call for action for Roassal

by Peter Uhnák

On Thu, Mar 10, 2016 at 12:36 AM, Martin Bähr <martin(a)realss.com> wrote: > hi, > > i just remembered two things: > > i'd like to see rounded corners on nodes. > We've added this quite some time ago, unless you have something else in mind. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |v e| v := RTView new. e := RTRoundedBox new size: 100; borderRadius: 20; borderColor: Color black; borderWidth: 1; element. v add: e. v ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > Excerpts from stepharo's message of 2016-02-24 12:42:49 +0100: > > - having a better output (arrows, edge) > > and related to edges: > > i'd like edges to connect to a node on the border of the box, not to the > center > of the node. this means the connecting point would always be at the middle > of > the side of one edge: > We have about 10 different attach points already. See the 'attach point' protocol of RTAbstractLine. Some of them also automatically add extra space if there are multiple lines between the same elements. As for bezier and multiline edges, their curvature isn't currently handled properly, but it's in my todo list (I'll work on this probably during the weekend). I'm sure it can be presented in more revealing way, but it's too late for me today (or is it too early?). You can play with it (drag the elements to see how it behaves). ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |v attachOptions es e offset| v := RTView new. attachOptions := RTAbstractLine selectors select: [ :each | each beginsWith: #with ]. offset := 0 @ 0. attachOptions do: [ :each | es := RTBox new borderColor: Color black; size: 50; elementsOn: #(a b). each = #withContinuousCircleAttachPoint ifTrue: [ es := RTEllipse new borderColor: Color black; size: 50; elementsOn: #(a b). ]. es translateBy: offset. es @ RTDraggable. offset := offset + (0 @ 100). v addAll: es. es second translateBy: 300 @ 25. e := RTArrowedLine new color: Color black; perform: each; edgeFrom: es first to: es second. e model: each. v add: e. e @ (RTLabelled new color: Color black). ]. v ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > ___\|/___ > | | > \| |/ > --| |-- > /| |\ > |_________| > /|\ > > bezier edges should always leave at a 90deg angle: > ____|____ > | | > | | > --| |-- > | | > |_________| > | > > optionally, starting at the corners could also be nice: > > \_________/ > | | > | | > | | > | | > |_________| > / \ > > and in such a case bezier edges should leave at 135deg to each side. > > by default the edge should find the nearest connection point, but i'd like > to > configure a list of allowed points. > > finally, multiple edges in the same general direction should either leave > at > the same point, pick the nearest side that doesn't have an edge already. > or spaced evenly along the same side if all available sides have edges > already. > > the list of allowed connection points would have 12 options: > the middle of 4 sides, 4 corners, and 4 sides as a whole when multiple > edges > should be spaced evenly. > > greetings, martin. > > -- > eKita - the online platform for your entire academic > life > -- > chief engineer > eKita.co > pike programmer pike.lysator.liu.se caudium.net > societyserver.org > secretary > beijinglug.org > mentor > fossasia.org > foresight developer foresightlinux.org > realss.com > unix sysadmin > Martin Bähr working in china > http://societyserver.org/mbaehr/ > >

8 years, 9 months

Roassal not working? (at least on Linux)

by Jan Kurš

Hi, When I download the latest and greatest moose image and the latest stable VM, I get an errorKeyNotFound: exception when evaluating: RTGrapher new. For more details see the stacktrace below. It does not seem to happen on MacOS. Any hint, help, solution, workaround? Cheers, Jan Stacktrace: Dictionary>>errorKeyNotFound: [ self errorKeyNotFound: arg1 ] in Dictionary>>at: Dictionary>>at:ifAbsent: Dictionary>>at: IRMethod>>indexForVarNamed: IRTranslatorV2>>visitPushTemp: IRPushTemp>>accept: IRTranslatorV2(IRVisitor)>>visitNode: IRTranslatorV2>>visitInstruction: [ :arg2 | self visitInstruction: arg2 ] in IRTranslatorV2(IRVisitor)>>visitSequence: OrderedCollection>>do: IRSequence>>do: IRTranslatorV2(IRVisitor)>>visitSequence: IRTranslatorV2>>visitSequence: IRSequence>>accept: IRTranslatorV2(IRVisitor)>>visitNode: [ :arg2 | self visitNode: arg2 ] in IRTranslatorV2(IRVisitor)>>visitNodes: SortedCollection(OrderedCollection)>>do: IRTranslatorV2(IRVisitor)>>visitNodes: IRTranslatorV2>>visitSequences: IRTranslatorV2>>visitMethod: IRMethod>>accept: IRTranslatorV2(IRVisitor)>>visitNode: IRMethod>>generate: FFICalloutMethodBuilder>>generateMethodFromSpec: FFICalloutMethodBuilder>>generate FFICalloutMethodBuilder>>build: FFICalloutAPI>>function:module: AthensCairoSurface class(Object)>>nbCall: AthensCairoSurface class>>primImage:width:height: AthensCairoSurface class>>extent:format: AthensCairoSurface class>>extent: TRCanvas>>initialize TRCanvas class(Behavior)>>new RTView>>initialize RTView class(Behavior)>>new RTGrapher(RTAbstractGrapher)>>createView RTGrapher(RTBuilder)>>initialize RTGrapher(RTAbstractGrapher)>>initialize RTGrapher>>initialize RTGrapher class(Behavior)>>new UndefinedObject>>DoIt OpalCompiler>>evaluate RubSmalltalkEditor>>evaluate:andDo: RubSmalltalkEditor>>highlightEvaluateAndDo: [ textMorph textArea editor highlightEvaluateAndDo: arg1 action. textMorph shoutStyler style: textMorph text ] in [ textMorph textArea handleEdit: [ textMorph textArea editor highlightEvaluateAndDo: arg1 action. textMorph shoutStyler style: textMorph text ] ] in GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>actOnHighlightAndEvaluate: RubEditingArea(RubAbstractTextArea)>>handleEdit: [ textMorph textArea handleEdit: [ textMorph textArea editor highlightEvaluateAndDo: arg1 action. textMorph shoutStyler style: textMorph text ] ] in GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>actOnHighlightAndEvaluate: WorldState>>runStepMethodsIn: WorldMorph>>runStepMethods WorldState>>doOneCycleNowFor: WorldState>>doOneCycleFor: WorldMorph>>doOneCycle [ [ World doOneCycle. Processor yield. false ] whileFalse: [ ] ] in MorphicUIManager>>spawnNewProcess [ self value. Processor terminateActive ] in BlockClosure>>newProcess

8 years, 9 months

issue with spotter

by Alexandre Bergel

Hi! When I activate spotter, and _quickly_ type something, “roassal” for example, and press the down arrow, the selection jumps to the top. I guess this happens when spotter is retrieving data from the system which somehow move the selection to the top most item. This is particularly annoying. Am I the only one to experience this? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

8 years, 9 months

Celebrating the upcoming Open Data Day (March 5) with Pharo

by Offray Vladimir Luna Cárdenas

Hi all, I just want to share a post made on the Open Knowledge Foundation Forum talking about what we're doing in our local community to celebrate the Open Data Day: https://discuss.okfn.org/t/our-poryect-and-hackathon-workshop-for-the-open-… Pharo, Roassal and Moose will be an integral part of our celebration. As I said in the link, we're going to try some treemapping techniques. I know about Quick Silver, but if any has some other advice, is very welcomed. Probably I will be making some questions here and in the chat channel regarding treemapping and some SQLite queries to get the proper info, so I'll keep you posted on how our pharo powered workshop/hackathon for the celebration of the Open Data Day advances. Cheers, Offray

8 years, 9 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev March 2016