Moose-dev July 2011

moose-dev@list.inf.unibe.ch

26 participants
178 discussions

Re: Issue 408 in moose-technology: Smalltalk importer should import Pragmas as annotations

by moose-technology＠googlecode.com

Comment #4 on issue 408 by tudor.gi...(a)gmail.com: Smalltalk importer should import Pragmas as annotations http://code.google.com/p/moose-technology/issues/detail?id=408 Would anyone be interested in working with these? We need the information for writing detections for Moose.

13 years, 2 months

Issue 562 in moose-technology: MooseElement should be removed

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 562 by alexandr...(a)gmail.com: MooseElement should be removed http://code.google.com/p/moose-technology/issues/detail?id=562 It is legacy code.

13 years, 2 months

Issue 661 in moose-technology: browse package blueprint: DNU

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 661 by jannik.l...(a)gmail.com: browse package blueprint: DNU http://code.google.com/p/moose-technology/issues/detail?id=661 #menuItems: does not exist in Mondrian anymore. (maybe a deprecated would have been good?) What's the replacement?

13 years, 2 months

Issue 542 in moose-technology: Completion in Glamour text presentation for Smalltalk

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.4 New issue 542 by tudor.gi...(a)gmail.com: Completion in Glamour text presentation for Smalltalk http://code.google.com/p/moose-technology/issues/detail?id=542 The Glamour TextPresentation for Smalltalk should offer completion as well.

13 years, 3 months

Issue 681 in moose-technology: SubclassResponsibility: a JPEGReadWriter had the subclass responsibility to implement #nextPutImage:

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 681 by vonbecm...(a)gmail.com: SubclassResponsibility: a JPEGReadWriter had the subclass responsibility to implement #nextPutImage: http://code.google.com/p/moose-technology/issues/detail?id=681 SubclassResponsibility: a JPEGReadWriter had the subclass responsibility to implement #nextPutImage: Pharo image: Pharo1.3a#13258 Virtual machine used: Croquet Closure Cog VM [CoInterpreter VMMaker-oscog.51] Platform Name: unix Class browser used (if applicable): OBSystemBrowserAdaptor Steps to reproduce: #. select a model. #. select all model namespaces #. press left button, select visualize>>dependencies(cycles) you will see the mondrian renderer #. export to jpeg #. enter a filename #. press Ok Actual Result: SubclassResponsibility: a JPEGReadWriter had the subclass responsibility to implement #nextPutImage: Expected Result: a filename.jpeg with the graph * Type-Defect * Component-Mondrian Renderer Attachments: PharoDebug.log 28.6 KB PharoScreenshot.1.png 69.6 KB

13 years, 3 months

Re: Issue 106 in moose-technology: Disable the default Smalltalk shortcuts from the Text Morphic widget in Glamour

by moose-technology＠googlecode.com

Updates: Labels: -Milestone-4.2 Milestone-4.4 Comment #5 on issue 106 by tudor.gi...(a)gmail.com: Disable the default Smalltalk shortcuts from the Text Morphic widget in Glamour http://code.google.com/p/moose-technology/issues/detail?id=106 (No comment was entered for this change.)

13 years, 3 months

Issue 655 in moose-technology: export a moose model raise an error

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 655 by cy.delau...(a)gmail.com: export a moose model raise an error http://code.google.com/p/moose-technology/issues/detail?id=655 Try to import a smalltalk model in moose. Right click on the model and 'export to mse' . at the end of the export you will get: MessageNotUnderstood: receiver of "sender" is nil I think it is related this issue : http://code.google.com/p/moose-technology/issues/detail?id=635 At the end of the export there is a notification signaling that the export succeed. The new way announcements are dealing now with exception signals lead to those kind of behavior

13 years, 3 months

Issue 536 in moose-technology: inFusion should export parentScope instead of container in Function

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 536 by tudor.gi...(a)gmail.com: inFusion should export parentScope instead of container in Function http://code.google.com/p/moose-technology/issues/detail?id=536 currently it exports container, but it should be parentScope

13 years, 3 months

Issue 537 in moose-technology: inFusion should export explicit sourceAnchor for Function

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 537 by tudor.gi...(a)gmail.com: inFusion should export explicit sourceAnchor for Function http://code.google.com/p/moose-technology/issues/detail?id=537 Currently, it exports sourceAnchor as a string like this: (FAMIX.Function (sourceAnchor 'path') ...) It should be (FAMIX.FileAnchor (id: 1) ...) (FAMIX.Function (sourceAnchor (ref: 1)))

13 years, 3 months

Issue 544 in moose-technology: inFusion should point the C++ source text to the implementation, not definition

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 544 by tudor.gi...(a)gmail.com: inFusion should point the C++ source text to the implementation, not definition http://code.google.com/p/moose-technology/issues/detail?id=544 Currently, the source anchor for a c/c++ class or methods points to the definition in the header. It should point to the implementation from the c/cpp file.

13 years, 3 months

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev July 2011