Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Issue 543 in moose-technology: inFusion does not export in UTF-8
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 543 by tudor.gi...(a)gmail.com: inFusion does not export in UTF-8 http://code.google.com/p/moose-technology/issues/detail?id=543 MSE should be in UTF-8.

1 2

Re: Issue 551 in moose-technology: VerveineJ should export parameterized types
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Comment #2 on issue 551 by tudor.gi...(a)gmail.com: VerveineJ should export parameterized types http://code.google.com/p/moose-technology/issues/detail?id=551 Currently, ParameterizableClass is exported, but the instances are duplicated.

1 3

Issue 532 in moose-technology: inFusion should also export PrimitiveTypes
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 532 by tudor.gi...(a)gmail.com: inFusion should also export PrimitiveTypes http://code.google.com/p/moose-technology/issues/detail?id=532 void, long, int, boolean, char, char[] ... should be PrimitiveTypes, not Classes

1 3

Re: Issue 440 in moose-technology: FamixInvocation>>to should return candidates instead of receiver
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Updates: Status: Fixed Comment #2 on issue 440 by simon.de...(a)gmail.com: FamixInvocation>>to should return candidates instead of receiver http://code.google.com/p/moose-technology/issues/detail?id=440 Fixed as first part of MooseChef integration

1 1

Re: Issue 420 in moose-technology: Shape should be properly initialized to be useful without further parameter
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Comment #3 on issue 420 by tudor.gi...(a)gmail.com: Shape should be properly initialized to be useful without further parameter http://code.google.com/p/moose-technology/issues/detail?id=420 Is this still an issue?

1 3

Re: Issue 340 in moose-technology: XMLElement>>allAttributes
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Updates: Labels: Milestone-4.6 Comment #5 on issue 340 by tudor.gi...(a)gmail.com: XMLElement>>allAttributes http://code.google.com/p/moose-technology/issues/detail?id=340 (No comment was entered for this change.)

1 0

Re: Issue 297 in moose-technology: Multiple selection
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Updates: Labels: Milestone-4.6 Comment #2 on issue 297 by tudor.gi...(a)gmail.com: Multiple selection http://code.google.com/p/moose-technology/issues/detail?id=297 (No comment was entered for this change.)

1 0

Re: Issue 267 in moose-technology: MOEllipseShape is a subclass of MORectangleShape ! It should not be
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Updates: Labels: Milestone-4.6 Comment #2 on issue 267 by tudor.gi...(a)gmail.com: MOEllipseShape is a subclass of MORectangleShape ! It should not be http://code.google.com/p/moose-technology/issues/detail?id=267 (No comment was entered for this change.)

1 0

Re: Issue 232 in moose-technology: Refactor/Harmonize printing of Moose entities
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Updates: Labels: Milestone-4.6 Comment #9 on issue 232 by tudor.gi...(a)gmail.com: Refactor/Harmonize printing of Moose entities http://code.google.com/p/moose-technology/issues/detail?id=232 (No comment was entered for this change.)

1 0

Re: Issue 130 in moose-technology: Mondrian zoom button are static
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Updates: Labels: Milestone-4.6 Comment #7 on issue 130 by tudor.gi...(a)gmail.com: Mondrian zoom button are static http://code.google.com/p/moose-technology/issues/detail?id=130 (No comment was entered for this change.)

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev