Moose-dev February 2013

moose-dev@list.inf.unibe.ch

21 participants
145 discussions

Issue 870 in moose-technology: ROFocusView focuses on the wrong spot

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: alexandr...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Roassal Component-Glamour New issue 870 by tu...(a)tudorgirba.com: ROFocusView focuses on the wrong spot http://code.google.com/p/moose-technology/issues/detail?id=870 Open a Roassal Easel and paste this: | node | node := view node: #a. ROFocusView new on: node view: view raw. The node is selected somewhere at the bottom. The reason is likely to be that the canvas has a static size, instead of adapting by default to the size of the surrounding pane

11 years, 6 months

Issue 894 in moose-technology: Roassal revised ROSelection and example

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 894 by benjamin...(a)gmail.com: Roassal revised ROSelection and example http://code.google.com/p/moose-technology/issues/detail?id=894 Initially I contributed ROSelection as part of the rubberbanding feature. The attached changeset generalizes it a bit and provides the folllowing example of its use. ------------- activeSelection := ROSelection new onInclusion: [ :element | ROHighlightElement on: element color: Color red ]; onExclusion: [ :element | ROUnhighlightElement on: element ]. statusBar := (ROElement on: activeSelection) + (ROLabel text: [ :el | el model asString ]) + ROBox white. view stack add: statusBar. statusBar translateTo: 0 @ 480. view shape label. view interaction on: ROMouseLeftClick do: [ :ann | activeSelection clear. activeSelection add: ann element. ]. view nodes: #(1 2 3 4 5). view gridLayout. --------------- There are two things I need help with: 1. Deselecting all elements when clicking on the background.** 2. Multiple selection, which if I knew the right way to work with the announcement events, would conceptually be as simple as the following modification... [ :ann | ann isShiftClicked ifFalse: [ activeSelection clear ]. activeSelection add: ann element. ]. **may also relate to Issue 884 comment #9 . Attachments: ROSelectionAndExample.1.cs 1.4 KB

11 years, 7 months

Issue 911 in moose-technology: Nested nodes in Roassal take too long

by moose-technology＠googlecode.com

Status: New Owner: alexandr...(a)gmail.com CC: usman.bh...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Roassal New issue 911 by usman.bh...(a)gmail.com: Nested nodes in Roassal take too long http://code.google.com/p/moose-technology/issues/detail?id=911 Try this script for creating nested nodes in Roassal. The execution seems to never return. The behavior is similar with both Mondrian DSL or Roassal API. view := ROMondrianViewBuilder new. view shape rectangle withoutBorder. view node:#aaa forIt:[ view shape rectangle. view nodes: (1 to: 10000). view gridLayout. ]. view shape rectangle withoutBorder. view node:#bbb forIt:[ view shape rectangle. view nodes: (1 to: 1000). view gridLayout. ]. view verticalLineLayout. view open

11 years, 7 months

Issue 895 in moose-technology: Lack of entities in verveineJ model

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-VerveineJ Milestone-4.7 New issue 895 by andreho...(a)gmail.com: Lack of entities in verveineJ model http://code.google.com/p/moose-technology/issues/detail?id=895 I'm parsing the single .java attached file (I have also copied in the end of this message), and I have some points: - A stub class FileUtils is not created. As consequence the receiver os the static invocation "FileUtils.close(ti)" (see last line) is "nil". - A stub class ArchiveScanner (superclass) is not created. What do you think about that? In addition (I believe it is OK): - A stub class Map is created as FAMIXParameterizableClass (it should just be used to Generics, no?). - A 'V' FAMIXParameterType is created - A Comparable is created as FAMIXParameterizedType Maybe these three points are coming from the class Map in Java, then it is OK. Basically this is the code attached: ========= public class TarScanner extends ArchiveScanner { ... protected void fillMapsFromArchive(Resource src, String encoding, Map fileEntries, Map matchFileEntries, Map dirEntries, Map matchDirEntries) { TarEntry entry = null; TarInputStream ti = null; try { try { ti = new TarInputStream(src.getInputStream()); } catch (IOException ex) { throw new BuildException("problem opening " + srcFile, ex); } while ((entry = ti.getNextEntry()) != null) { Resource r = new TarResource(src, entry); String name = entry.getName(); if (entry.isDirectory()) { name = trimSeparator(name); dirEntries.put(name, r); if (match(name)) { matchDirEntries.put(name, r); } } else { fileEntries.put(name, r); if (match(name)) { matchFileEntries.put(name, r); } } } } catch (IOException ex) { throw new BuildException("problem reading " + srcFile, ex); } finally { FileUtils.close(ti); } } ... =========

11 years, 7 months

importers page

by Tudor Girba

Hi, I created a page dedicated to importing instructions: http://www.moosetechnology.org/docs/importers A good example of how these instructions should look like can be found here: http://www.moosetechnology.org/docs/importers/importJavaWithinFusion We would need more detailed information about: - Import C# with PMCS http://www.moosetechnology.org/docs/importers/importCSharpWithPMCS - Import C with CAnalyzer http://www.moosetechnology.org/docs/importers/importCWithCAnalyzer Cheers, Doru -- www.tudorgirba.com "Obvious things are difficult to teach."

11 years, 7 months

Roassal temporary edges

by Martin Dias

Hello, I have some nodes on a view, and I would like that on ROMouseEnter, some edges are shown, and on ROMouseLeave they disappear. My code is a bit complex, but I can recreate the scenario in a script if you need. Best regards, Martin

11 years, 8 months

node: forIt: in Roassal takes too long

by Usman Bhatti

Hello, I am trying to arrange two sets of nodes in verticalLineLayout with Roassal, and within a set, the nodes are arranged in a gridLayout. The script below allows works fine except that the execution time is too long when the number of nodes is large and hence I am unable to achieve multi-layout visualization for large number of nodes. view := ROMondrianViewBuilder new. view shape rectangle withoutBorder. view node:#aaa forIt:[ view shape rectangle. view nodes: (1 to: 10000). view gridLayout. ]. view shape rectangle withoutBorder. view node:#bbb forIt:[ view shape rectangle. view nodes: (1 to: 1000). view gridLayout. ]. view verticalLineLayout. view open Can you please have a look or could you suggest an alternate solution? I have created my own custom layout but that is tied to the structure of my nodes and hence not generic. tx. usman

11 years, 8 months

pharo and moose

by Haroldo Stenger

hi! I'm totally new to smalltalk, although I've heard of it since a lot of time ago. In my arch linux installation, I've found some dificulties running squeak, so I went into pharo once I've discovered they are two free implementations of smalltalk. Then I wondered myself, How can I do now to put moose into here ? And then I saw that by selecting the proper text in one of the default windows that pharo opens for me, I could have moose (and other subsystems) installed in the image I'm workin on. So I did. I've found myself pretty impressed at the ease by which the subsystems get installed. I started installing one of the web development systems, and I got thru the whole automated process without any problems. Then I evaluated the code that installs moose. It started running, and run a lot without a problem too. But at some point, some missing methods poped up a window in which I'm asked what to do. At the firsts of them, I put 'proceed' (because I wouldn't abandon, nor debug because I woudn't know what to do), and it proceeded. At some later pop up errors, I was offered a fourth option namely 'create', I did, and put the method I was asked to put somewhere in systembase or some similar name (I can be more precise if needed or asked to), then a code that showed a 'to be implemented' dummy method or something, and then again, asked to proceed, and and did this process a number of times, until I realized that there were many of them, and I abadoned. And went here, asking for some kind help of you. I could insist with squeak if that would do better, or go Cuis alternatively (but from what I've read, maybe Cuis would not fit). I've also read that pharo support from moose is in some development phase. Is that true? So if I'm a beginner I should try it until it's ready. I'm interested in moose mainly, and derived from this, in smalltalk and in any of its free versions if they work. Any hint is welcome. cheers Haroldo

11 years, 9 months

Issue 845 in moose-technology: some Roassal layouts broken when nested

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 845 by google....(a)ben.coman.com.au: some Roassal layouts broken when nested http://code.google.com/p/moose-technology/issues/detail?id=845 The application I am developing needs to apply layouts to nested elements. I noticed that some layouts did not work when nested - so I've done a full review of the layout listed in ROMondrianExample>>chooseLayoutOn: as per the attached image. On the left is the non-nested-result and on the right is the nested-result. I have attached the mcz with a slightly modified #chooseLayoutOn: as well as #chooseLayoutNestedOn: for comparison. Attachments: Roassal-BenComan.313.mcz 241 KB ROMondrianExample-chooseLayoutNestedOn.png 127 KB

11 years, 9 months

Re: Issue 382 in moose-technology: CMD + W does not close Mondrian window

by moose-technology＠googlecode.com

Comment #1 on issue 382 by tudor.gi...(a)gmail.com: CMD + W does not close Mondrian window http://code.google.com/p/moose-technology/issues/detail?id=382 This is still an issue and it hinders usability. Alex, could you take a look at it?

11 years, 9 months

← Newer
1
...
4
5
6
7
8
9
10
...
15
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev February 2013