Moose-dev November 2012

moose-dev@list.inf.unibe.ch

23 participants
145 discussions

Issue 637 in moose-technology: VerveineJ should show an invocation to the default constructor

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ New issue 637 by tu...(a)tudorgirba.com: VerveineJ should show an invocation to the default constructor http://code.google.com/p/moose-technology/issues/detail?id=637 A call to the default constructor should be modeled like: - create a stub constructor in the target class - create an invocation to the constructor See the attached class for a sample. Attachments: DefaultConstructor.java 184 bytes

11 years, 9 months

Issue 636 in moose-technology: VerveineJ should set hasClassScope

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ New issue 636 by tu...(a)tudorgirba.com: VerveineJ should set hasClassScope http://code.google.com/p/moose-technology/issues/detail?id=636 Static fields or methods should be marked with hasClassScope=true: public static int attributeWithClassScope; public static void methodWithClassScope() {} See the attached sample class. Attachments: ClassScope.java 179 bytes

11 years, 9 months

Issue 880 in moose-technology: Improving VerveineJ stub invocations/methods

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Enhancement Priority-Medium Component-VerveineJ Milestone-4.7 New issue 880 by andreho...(a)gmail.com: Improving VerveineJ stub invocations/methods http://code.google.com/p/moose-technology/issues/detail?id=880 When creating models without classpath, invocations/methods (where the biding are not found) are created in the format: anInvocation(???) This is the case even if the real invocation in source code contains parameters such as: anInvocation(a, b) It would be good maintain the information with respect to the number of parameters in such invocation/method, and then export the #signature with something like: anInvocation(?, ?) Like that we can at least count the number of parameters.

11 years, 10 months

Issue 838 in moose-technology: VerveineJ does not export non-javadoc comments

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ New issue 838 by tudor.gi...(a)gmail.com: VerveineJ does not export non-javadoc comments http://code.google.com/p/moose-technology/issues/detail?id=838 VerveineJ exports javadoc comments for both types and methods. However, it does not export line comments like: //This is also a relevant comment

11 years, 10 months

Re: Issue 865 in moose-technology: Reloader should get the list of packages to be loaded from the ConfigurationOfMoose

by moose-technology＠googlecode.com

Comment #2 on issue 865 by tu...(a)tudorgirba.com: Reloader should get the list of packages to be loaded from the ConfigurationOfMoose http://code.google.com/p/moose-technology/issues/detail?id=865 The problem is that we still cannot quite obtain the list of packages from Metacello in proper order.

11 years, 10 months

Issue 851 in moose-technology: Create a stable version for Moose and all its subparts

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Engineering Priority-Medium Maintainability Milestone-4.7 New issue 851 by tu...(a)tudorgirba.com: Create a stable version for Moose and all its subparts http://code.google.com/p/moose-technology/issues/detail?id=851 The configuration of Moose should be versionned, especially for a release. We have to investigate if Reloader is good enough for 4.7.

11 years, 10 months

Roassal how to display bottom corner of graph

by Ben Coman

With Roassal after applying a layout, I would like to be able to translate the graph such that the bottom left corner of the graph is displayed. Is there someway to do that already? I looked into ROFocusView, ROCanvas & ROCamera, but could not work it out what was needed. With the script below, the attached image is what I would like to see. "-------------" #(1 2 3 4 5 6 7 8 9) do: [ :x | rawView add: (ROElement spriteOn: x) + ROLabel. ]. rawView add: (ROEdge lineFrom: rawView elements seventh to: rawView elements eighth). rawView add: (ROEdge lineFrom: rawView elements seventh to: rawView elements ninth). (ROHorizontalTreeLayout new verticalGap: 40; horizontalGap:60) on: rawView elements. "HERE TRANSLATE CANVAS/CAMERA TO SHOW NODES 7, 8 & 9 IN THE BOTTOM LEFT CORNER OF WINDOW PANE" "-------------" cheers -ben

12 years

Development of FAMIX AST meta-model extension

by Yuriy Tymchuk

Hi everyone! I'm extending FAMIX meta-model to add support for AST models.The project can be found at: http://smalltalkhub.com/#!/~YuriyTymchuk/Famix-AST <http://smalltalkhub.com/#!/~YuriyTymchuk/Famix-AST> I'll be thankful for any suggestions an support :) At the moment I've developed a hierarchy of the AST meta-model itself and you can load it from MSE files, as an example you can use this one: https://raw.github.com/Uko/metamodels-support-files/master/mse/ast.mse <https://raw.github.com/Uko/metamodels-support-files/master/mse/ast.mse> Please note that only /middleOf:And:/ method has it's AST defined. To explore AST model you should select a method node and see *statements* as it's subnode. My next step is automatic creation of the AST model from existing source of the method. Here is a diagram of a current Famix-AST class hierarchy: <http://moose-dev.97923.n3.nabble.com/file/n4025674/ClassDiagram.png> -- View this message in context: http://moose-dev.97923.n3.nabble.com/Development-of-FAMIX-AST-meta-model-ex… Sent from the moose-dev mailing list archive at Nabble.com.

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

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

← Newer
1
...
5
6
7
8
9
10
11
...
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 November 2012