Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

by Dennis Schenk

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

12 years, 9 months

Re: PetitParser handling preprocessor directives?

by Stephan Eggermont

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

12 years, 9 months

PetitParser handling preprocessor directives?

by Stephan Eggermont

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

12 years, 9 months

glamour perf

by Usman Bhatti

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

12 years, 9 months

some graph drawing references

by Ben Coman

12 years, 9 months

PetitParser // FLFactorialExample

by H. Hirzel

Hello PetitParser comes with a Factorial Language example. The comment of the class FLFactorialExample states "I implement the example given in "factorial.txt". The code can be edited directly in the Smalltalk code browser and is automatically parsed, transformed and eventually compiled down to Smalltalk bytecodes." Where do I find the description of this language, i.e. the file 'factorial.txt'? Regards Hannes

12 years, 9 months

Issue 834 in moose-technology: Roassal layouts do not properly take into account userDefinedEdges

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: alexandr...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Roassal Milestone-4.7 New issue 834 by tu...(a)tudorgirba.com: Roassal layouts do not properly take into account userDefinedEdges http://code.google.com/p/moose-technology/issues/detail?id=834 To reproduce see the example below: | edges | view nodes: #(1 2 3). edges := view edgesFrom: [:each | each - 1]. view shape line color: Color red. view edges: #(3) from: [:each | each - 2] to: #yourself. view treeLayout userDefinedEdges: edges If the user defined edges would be taken into account, the tree would appear on one line (1->2->3). Instead it appears laid out as 1->2, 1->3 .

12 years, 10 months

Re: ROCircleLayoutNew & ROCircleDynamicLayout

by Ben Coman

Ben Coman wrote: > > I've been playing with ROCircleLayout in the form of ROCircleLayoutNew > and ROCircleDynamicLayout. This was mainly to deal with where element > dimensions are much different (eg much wider than they are high). Its > not polished but I've come to the limit of time I can be distracted by > it at this time, so I'm just presenting it in case you find anything > useful. > Have a look at ROExample... > #circleWideElements > #circleWideElementsNewLayout > #circleWideElementsDynamic > #dynamicCirclePlay > > cheer -ben > > btw, I'm a bit confused by what Monitcello is showing me in terms of changes versus your Roassal.289 version. It shows ROCircleLayout2 and ROCircleLayout3 as missing from your 289 mcz, which implies they are is in my image, except I have previously deleted those two classes from my image prior to saving through Monticello. Do they show up to you?

12 years, 10 months

how to export PNG from Roassal

by Tudor Girba

Hi, How do I programmatically export a PNG of the entire visualization from Roassal? I tried to use the ROView>>bitmap, but it returns a cropped image. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

12 years, 10 months

Jenkins build became unstable: moose-latest-dev #1118

by admin＠moosetechnology.org

See <http://hudson.moosetechnology.org/job/moose-latest-dev/1118/>

12 years, 10 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev