Moose-dev April 2013

moose-dev@list.inf.unibe.ch

34 participants
198 discussions

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

10 years, 11 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

10 years, 11 months

Issue 917 in moose-technology: ConfigurationOfMerlin on Smalltalkhub needs to be updated

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium New issue 917 by usman.bh...(a)gmail.com: ConfigurationOfMerlin on Smalltalkhub needs to be updated http://code.google.com/p/moose-technology/issues/detail?id=917 ConfigurationOfMerlin on Smalltalkhub needs to be updated because the baseline still loads from squeaksource, it should normally load from the packages from SmallTalkHub. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

10 years, 11 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); } } ... =========

10 years, 11 months

Creating a Configuraton

by Dennis Schenk

Hi All, I'm trying to make ConfiguratonOfQuicksilver work. When running: *Gofer new* * smalltalkhubUser: 'Quicksilver' project: 'Quicksilver';* * package: 'ConfigurationOfQuicksilver';* * load.* *ConfigurationOfQuicksilver loadDefault.* I get: 'Could not resolve: Quicksilver-Core-Tests [Quicksilver-Core-Tests] in /[...]/package-cache http://smalltalkhub.com/mc/Quicksilver/Quicksilver/main ' Does anybody have an idea why MetacelloFetchingMCSpecLoader is looking in my local package-cache for the package and not on smalltalkhub? Cheers, Dennis

10 years, 11 months

Name cloud and Overview pyramid migrated into Roassal

by Juraj Kubelka

Hi! Name cloud and Overview pyramid has been migrated into Roassal. There are two new tests which explains fixes of ROLabel (ROAbstractLabel>>testSize2 and #testSize3). Cheers, Jura

10 years, 11 months

roassal-based blueprint review

by Tudor Girba

Hi, I looked over the Roassal blueprint implementation. We start to have a working solution. Good work. However, there is still some work left :) What is nice: - Edges are properly drawn below the nodes - The implementation layer shows a tree layout - The morph menus work - The layers do not capture the interaction What is not so nice: - Morph menus are shown even on left click. They should only appear on right click. I fixed this. - The size of the root node grows too large and we get a little gap at the bottom (see the first attached picture). This has likely something to do with the latest fix from Alex related to padding. - When dragging a method or attribute node outside of the bounds of the parent, the parent continues to grow (see the second picture). This is not good :). The problem is that the logic depends on setting the parent to have extensible size. Instead, in the case of the blueprint, it should be the responsibility of the layout to grow the parent as needed without actually making the parent to be extensible. This is why in Mondrian the layout could be set to stretch. - Right now, the edges start and end in the center of the nodes. The convention in the blueprint is to have edges drawn starting from the right side and end on the left side of nodes. In any case, I already added it to the MooseFinder (the blueprint tab). Cheers, Doru -- www.tudorgirba.com "There are no old things, there are only old ways of looking at them."

10 years, 11 months

Metaceller

by Diego Lont

Hi all, Recently I have been working on some configurations, and I felt the need to have something better (more specific for configurations) to edit my configurations than the standard OB / Nautilus. On the PharoConf Doru told me about GTMetataceller, but this tool needed some work. So I did some work on it, and now I am looking for feedback how you like it. It is built in glamour, and you get it, when you download the latest Moose. Just type GTMetaceller open somewhere in the browser and you are ready to rock. If you know how Metacello works, the editor should be more or less self explaining. In case you run into trouble, there is a help button that explains the tool a bit. I also did a screencast: http://youtu.be/LaJF_dfGsD8. If you want to load this in your image, just do: Gofer new url: 'http://www.smalltalkhub.com/mc/Moose/GToolkit/main'; package: 'ConfigurationOfGToolkit'; load. (Smalltalk at: #ConfigurationOfGToolkit) project development load. (Smalltalk at: #GTMetaceller) open. Note: I only tested this in Pharo 2.0, this loading does not work in Pharo 1.4. It should work in Pharo 1.4, since loading the GT-Metaceller package in Moose 4.7 works fine. I think I should create a stable version as well … that loads in Pharo 1.4 as well. Cheers, Diego

10 years, 11 months

roassal + athens

by Tudor Girba

Hi, I would like to start adopting Athens behind Roassal. I believe there already is a binding. The question is what keeps us from adding Athens as a dependency to RoassalMorphic? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

10 years, 11 months

Jenkins build is back to normal : moose-latest-dev-4.8 #374

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/374/>

10 years, 12 months

← Newer
1
...
5
6
7
8
9
10
11
...
20
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev April 2013