Moose-dev February 2013

moose-dev@list.inf.unibe.ch

21 participants
145 discussions

Re: Issue 482 in moose-technology: Use JNIPort to connect to VerveineJ

by moose-technology＠googlecode.com

Comment #2 on issue 482 by cy.delaunay: Use JNIPort to connect to VerveineJ http://code.google.com/p/moose-technology/issues/detail?id=482 you should now use that: Gofer new url: 'www.squeaksource.com/DelaunayTmpStuffs'; package: 'JNIPort-Initialization'; load. Gofer new url: 'www.squeaksource.com/DelaunayTmpStuffs'; package: 'JNIPortExample'; load. The initialization part still has to be fixed, sometimes it works, sometimes not.

11 years, 5 months

Re: Issue 432 in moose-technology: Popup should appear only when a certain modifier key is pressed

by moose-technology＠googlecode.com

Comment #1 on issue 432 by tu...(a)tudorgirba.com: Popup should appear only when a certain modifier key is pressed http://code.google.com/p/moose-technology/issues/detail?id=432 Another option would be to have the rendering happening in another thread.

11 years, 5 months

Issue 912 in moose-technology: Glamour presentations should update their own actions when receiving GLMPresentationUpdated

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 912 by chisvasi...(a)gmail.com: Glamour presentations should update their own actions when receiving GLMPresentationUpdated http://code.google.com/p/moose-technology/issues/detail?id=912 Right now when a presentation receives GLMPresentationUpdated it does not update its own actions. For example bellow is some code to see this behaviour. When the action from the composite presentation is triggered it updates the action from the contained presentations but not its action. Also if there is just one presentation in the composite then, due to how a composite with one presentation is implemented, it won't update any action. |browser| browser := GLMTabulator new. browser row: #aRow. browser transmit to: #aRow; andShow: [ :composite | composite title: 'Composite'; updateOn: Announcement from: [ browser announcer ]; dynamicActions: [ :list || actions | actions := OrderedCollection new. actions add: ((GLMGenericAction new) action: [ :presentation :model | browser announce: Announcement]; icon: GLMUIThemeExtraIcons glamorousAdd; title: DateAndTime now asString; yourself). actions ]. composite list title: 'List 1'; updateOn: Announcement from: [ browser announcer ]; dynamicActions: [ :list || actions | actions := OrderedCollection new. actions add: ((GLMGenericAction new) action: [ :presentation :model | browser announce: Announcement]; icon: GLMUIThemeExtraIcons glamorousAdd; title: DateAndTime now asString; yourself). actions ]. composite list title: 'List 2']. browser openOn: (1 to: 10)

11 years, 5 months

Issue 829 in moose-technology: Roassal Label Text does not scale with Zoom Out

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 829 by google....(a)ben.coman.com.au: Roassal Label Text does not scale with Zoom Out http://code.google.com/p/moose-technology/issues/detail?id=829 Actions 1. Open Roassal Easel > Example > #arrowed edges > umlLike 2. Click the <Zoom out> button multiple times Expected Behaviour Text gets smaller so as to stay within the border as the label box gets smaller. Observed Behaviour Only the border of the label gets smaller. The text gets the same size until it all overlaps.

11 years, 6 months

Re: Issue 736 in moose-technology: Moose crashes when importing Citezen (OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:)

by moose-technology＠googlecode.com

Updates: Summary: Moose crashes when importing Citezen (OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:) Comment #3 on issue 736 by tudor.gi...(a)gmail.com: Moose crashes when importing Citezen (OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:) http://code.google.com/p/moose-technology/issues/detail?id=736 (No comment was entered for this change.)

11 years, 6 months

Issue 647 in moose-technology: Integrate torch package visualization

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 647 by cy.delau...(a)gmail.com: Integrate torch package visualization http://code.google.com/p/moose-technology/issues/detail?id=647 Maybe it would be a good idea (?) to use / integrate the torch packages visualization in moose ? http://hal.archives-ouvertes.fr/docs/00/53/15/08/PDF/Uqui10a-Torch-WCRE10.p…

11 years, 6 months

Re: Issue 469 in moose-technology: integrate Kontractor

by moose-technology＠googlecode.com

Updates: Labels: Milestone-4.3 Comment #4 on issue 469 by tudor.girba: integrate Kontractor http://code.google.com/p/moose-technology/issues/detail?id=469 What is the status of this?

11 years, 6 months

Re: Issue 437 in moose-technology: Text is not affected by zooming in Mondrian

by moose-technology＠googlecode.com

Comment #1 on issue 437 by alexandre.bergel: Text is not affected by zooming in Mondrian http://code.google.com/p/moose-technology/issues/detail?id=437 Situation has been slightly improved, but this is clearly not satisfactory

11 years, 6 months

Issue 907 in moose-technology: VerveineJ does not export source anchors for FAMIXAnnotationType and FAMIXAnnotationTypeAttribute

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Famix New issue 907 by tu...(a)tudorgirba.com: VerveineJ does not export source anchors for FAMIXAnnotationType and FAMIXAnnotationTypeAttribute http://code.google.com/p/moose-technology/issues/detail?id=907 When we have an explicit annotation in the code, we should also get the source anchor associated with it. For example, in the below case, SomeAnnotation.java should be associated with SomeAnnotation: SomeAnnotation.java @Documented @Target({ ElementType.FIELD }) @Retention(RetentionPolicy.CLASS) public @interface SomeAnnotation {...} The same applies for the contained FAMIXAnnotationTypeAttributes.

11 years, 6 months

Issue 910 in moose-technology: [VerveineJ] Some methods have 'private' modifier in source code but not in model

by moose-technology＠googlecode.com

Status: New Owner: anquetil...(a)gmail.com CC: damien.c...(a)gmail.com Labels: Type-Defect Priority-High Component-VerveineJ New issue 910 by damien.c...(a)gmail.com: [VerveineJ] Some methods have 'private' modifier in source code but not in model http://code.google.com/p/moose-technology/issues/detail?id=910 1- Take ant-1.8.2.mse 2- Search methods with each isProtected not and: [each isPublic not and: [each isPrivate not and: [each isStub not]]] 3- Some methods are private here

11 years, 6 months

← Newer
1
2
3
4
5
6
7
8
9
...
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 February 2013