Moose-dev December 2012

moose-dev@list.inf.unibe.ch

15 participants
126 discussions

Start a nNew thread

OnMooseHardcodedViewRenderer Report

by Fabrizio Perin

Hi Doru, don't you think you can remove the class MOBenchmarks from this report?

12 years

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

by admin＠moosetechnology.org

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

12 years

Issue 893 in moose-technology: The Moose menu entries labels do not match the window titles

by moose-technology＠googlecode.com

Status: New Owner: tu...(a)tudorgirba.com Labels: Type-Defect Priority-Medium Milestone-4.7 Component-Finder New issue 893 by tu...(a)tudorgirba.com: The Moose menu entries labels do not match the window titles http://code.google.com/p/moose-technology/issues/detail?id=893 For example, the label shows 'Glamorous Glamour Editor' and the title is 'Glamorous Browser Editor'

12 years

Issue 781 in moose-technology: VerveineJ should mark getters setters and constants

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 781 by santiago...(a)gmail.com: VerveineJ should mark getters setters and constants http://code.google.com/p/moose-technology/issues/detail?id=781 The property "kind" of the MSE models should be used to mark if a method is a getter, a setters or constant. Currently is only used to mark if a method is constructor

12 years

[ann] moose talk at the java user group in bern

by Tudor Girba

Hi, On December 12, 18:15 I will give a talk at the Java User Group in Bern. I will be talking about how Moose redefines the meaning of analysis :): http://www.humane-assessment.com/blog/moose-talk-at-jug-bern-2012/ Cheers, Doru -- www.tudorgirba.com "Every successful trip needs a suitable vehicle."

12 years

Issue 889 in moose-technology: All meta-properties should have an MSEComment

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Milestone-4.7 Component-Famix New issue 889 by tu...(a)tudorgirba.com: All meta-properties should have an MSEComment http://code.google.com/p/moose-technology/issues/detail?id=889 Here is the list of missing comments: http://ci.moosetechnology.org/job/moose-on-moose/lastCompletedBuild/testRep…

12 years

Issue 892 in moose-technology: Roassal does not render properly on update

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.7 New issue 892 by tu...(a)tudorgirba.com: Roassal does not render properly on update http://code.google.com/p/moose-technology/issues/detail?id=892 browser := GLMWrapper new. browser show: [:a| a roassal title: 'Patterns'; act: [:roassal | roassal update ] icon: GLMUIThemeExtraIcons glamorousRefresh entitled: 'Update'; painting: [:view :collection | view nodes: collection. view edgesFrom: [:x | x // 2]. view treeLayout ] ]. browser openOn: (1 to: 100)

12 years

Using Roassal as part of a Glamour-based UI

by Stephan Eggermont

Hi, I tried using a Roassal painting as a card-based layout for a glamour UI, but don't have too much luck updating it. The self refresh sends the CPRefresh, and the painting is updated, but all nodes are on top of each other. Related to issue 808? (Roassal 383, Glamour-Roassal-Presentations 7) browser := GLMTabulator new. browser row: #content; title: 'Change Patterns'. browser transmit to: #content; andShow: [:a| a roassal title: 'Patterns'; updateOn: CPRefresh from: self announcer; painting: [:view :patternHolder | |paintingBlock| paintingBlock := [ view shape width: [:el | 180]; height: [:el| 80]; fillColor: [:aPattern | aPattern applicable ifTrue: [Color r: 1.0 g: 1.0 b: 0.8] ifFalse: [Color red]]. view nodes: patternHolder patterns forEach: [:aPattern | view interaction item: 'inspect' action: [:el | aPattern switchApplicable. view raw elementsDo: #remove. self refresh]. view shape label. view nodes: (Array with: aPattern title with: aPattern applicable asString). view verticalLineLayout ]. view gridLayout]. view interaction item: 'inspect' action: [:el | el model inspect]; item: 'switch applicable' action: [:el | el model switchApplicable. view raw elementsDo: #remove. paintingBlock value. self refresh]. paintingBlock value. ]]. ^browser Stephan

12 years

Issue 875 in moose-technology: Moose should test if it runs on a vm with the freetype plugin

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 875 by step...(a)stack.nl: Moose should test if it runs on a vm with the freetype plugin http://code.google.com/p/moose-technology/issues/detail?id=875 There are several vms that don't have a working freetype plugin. This severely reduces the number of fonts available (1 or 2 families with a very limited set of font sizes). This is an issue for 4.6 as well as 4.7 A testcase is added in Moose-Tests-FreeType-StephanEggermont.1 Attachments: Moose-Tests-FreeType-StephanEggermont.1.mcz 1.4 KB

12 years

Issue 883 in moose-technology: viewTree does not work for Glamour browsers

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-High Component-Glamour Milestone-4.7 New issue 883 by tu...(a)tudorgirba.com: viewTree does not work for Glamour browsers http://code.google.com/p/moose-technology/issues/detail?id=883 This should work: GLMTabulator new viewTree

12 years

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev December 2012