Moose-dev September 2012

moose-dev@list.inf.unibe.ch

25 participants
124 discussions

Cytoscape, maybe interesting for someone
by Mariano Martinez Peck 20 Sep '12

20 Sep '12

I was just reading a blog post and I found this visualization tool: http://www.cytoscape.org/what_is_cytoscape.html maybe it is useful for someone in this list. Cheers, -- Mariano http://marianopeck.wordpress.com

2 1

Roassal - resize strategy for shrinking
by Ben Coman 17 Sep '12

17 Sep '12

Just one more thing that has been playing on my mind. It is really a nice feature that the parent element grows when the child is moved past its boundary, but would be more good if it also shrank when the child element is moved back towards center. cheers ben

2 6

Re: PetitParser handling preprocessor directives?
by Stephan Eggermont 17 Sep '12

17 Sep '12

Guillermo wrote: >Maybe you can use a -completely separate- pre-parser? :) > >It takes the input with the pre processor directives, and answers a new >processed string which the original parser will handle?. Yes, I guess so. I'm fighting a bit with PetitParser, wondering if the traditional style of building parsers wouldn't be faster. But that might be just about trying something new. I like the tests, the separate lexicon, syntax and semantics subclassing not so much better than preprocessing, scanning, parsing. I definitely don't like having 80 productions in a class (growing to 300, not sure how to grow over the max nr of instVars ). Is there an array or dictionary based PPCompositeParser? Stephan

3 2

Roassal nested layout
by Ben Coman 16 Sep '12

16 Sep '12

I have been looking at the ROExample "Nesting" examples and expanded #nesting2 with another level as shown in the code below, such that there is the outer view, middle "#1" nodes and inner "#2" nodes. However the initial state of this has much of the middle node1 and inner node2 nodes overlapping. How can these be made for the circle layout to leave spacing between the middle node1 nodes? cheers -ben -------------------- | view nodes1 | view := ROView new. view add: (ROElement sprite addAll: (nodes1 := ROElement spritesOn: (1 to: 10))). nodes1 do: [:n | n addShape: ROLabel]. nodes1 do: [ :node1 | ( (node1 model) *100+1 to: (node1 model)*100+5 ) do: [ :x | node1 add: ( (ROElement spriteOn: x) addShape: ROLabel). ]. ROGridLayout on: node1 elements. ]. ROCircleLayout on: nodes1. view openInWindow.

4 17

D3 - Javascript visualization
by Andre Hora 14 Sep '12

14 Sep '12

Hello, Just to show you a nice Javascript library (D3) for create visualization: http://d3js.org https://github.com/mbostock/d3/wiki/Gallery -- Andre Hora

7 11

Roassal: Opacity
by Dennis Schenk 14 Sep '12

14 Sep '12

Hi, Is it possible in Roassal to draw nodes in a layout with different opacities? A simple example would be: drawing a tree with nodes less opaque the deeper their nesting level is. Cheers, Dennis

2 1

Re: PetitParser handling preprocessor directives?
by Stephan Eggermont 14 Sep '12

14 Sep '12

Guillaume wrote: >You can use PetitPreprocessor: >Gofer new > squeaksource3: 'PetitPreprocessor'; > package: 'PetitPreprocessor'; > load > >Now it's just transform a matching regex to a substitution String (MyParser >preProcess: ('toPreprocess' asRegex) into: 'preProcessed' ) but I plan to >improve it by providing a PParser to detect a matching and apply its >transformation block (myParser preProcessor: (matchingParser ==> [:m | >..... ])). Thank you. Will try that first Stephan

1 0

PetitParser handling preprocessor directives?
by Stephan Eggermont 14 Sep '12

14 Sep '12

Hi What is the best way to handle pre-processor directives with PetitParser without polluting the parsing too much? Any suggestions? unit forms; interface {$IFDEF WINDOWS} uses bla; {$ENDIF} {$IFDEF LINUX} uses bla2; {$ENDIF} Diego & Stephan

3 2

glamour perf
by Usman Bhatti 14 Sep '12

14 Sep '12

Hello all, I sat with Benjamin today to have a look at Glamour performance when displaying large text files. For reminder, when displaying text in glamour, the time to display text increases exponentially with the size of the text being displayed. Two observations: 1/ Whereas, with the following script the execution time remains equivalent to that of morphs MessageTally spyOn: [ (*GLMPluggableTextMorph* on: [ (StandardFileStream fileNamed: 'testfile-glam-3500.txt') contents ] text: #value accept: nil) openInWindow extent: (1273.0(a)738.0) ] the execution of this script is four times longer: | browser text| browser := *GLMTabulator* new. browser column: #text. browser transmit to: #text; andShow: [ :a | a text title: 'Text with selection'; display: [(StandardFileStream fileNamed: 'testfile-glam-3500.txt') contents]]. MessageTally spyOn: [browser openOn: 2]. 2/ A bit of digging (using time profiler) shows that the garbage collector is taking 75% of the execution time. [image: Inline image 1] Doru, will you have an idea what makes garbage collector execute and take extra seconds when the text is displayed in a glamour browser instead of individual glmaour widget? The moose image with the scripts can be found here if you want to have a look. http://dl.dropbox.com/u/11804892/glamour-perf-tests.zip thanx in advance, Usman

3 2

some graph drawing references
by Ben Coman 11 Sep '12

11 Sep '12

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev September 2012