Moose-dev May 2013

moose-dev@list.inf.unibe.ch

29 participants
196 discussions

Issue 906 in moose-technology: FAMIXType>>classScope should not return nil

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Famix New issue 906 by tu...(a)tudorgirba.com: FAMIXType>>classScope should not return nil http://code.google.com/p/moose-technology/issues/detail?id=906 Right now, the classScope in FAMIXType returns nil, which is a problem. FAMIXType>>classScope "all types are not classes. Redefined in FamixClass" ^ nil Either we make it return self, or we introduce typeScope.

11 years, 5 months

Issue 897 in moose-technology: Roassal line layout does not work when stretched

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: alexandr...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Roassal Milestone-4.7 New issue 897 by tu...(a)tudorgirba.com: Roassal line layout does not work when stretched http://code.google.com/p/moose-technology/issues/detail?id=897 Try this: view nodes: #(1 2 3) . view horizontalLineLayout stretch We need this to work for the class blueprint

11 years, 5 months

Issue 891 in moose-technology: Right click menu missing in Sample input in PPParserInspector

by moose-technology＠googlecode.com

Status: Accepted Owner: kurs....(a)gmail.com CC: tu...(a)tudorgirba.com Labels: Type-Enhancement Priority-Medium Component-PetitParser New issue 891 by kurs....(a)gmail.com: Right click menu missing in Sample input in PPParserInspector http://code.google.com/p/moose-technology/issues/detail?id=891 There is no right click menu in Sample input field in PPParserInspector. It would be nice to put items such as: - Copy - Paste - Cut - Parse Any other suggestions?

11 years, 5 months

Issue 748 in moose-technology: DistributionMap examples not working

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 748 by cy.delau...(a)gmail.com: DistributionMap examples not working http://code.google.com/p/moose-technology/issues/detail?id=748 When you try to execute the examples in the class side of DistributionMap, you get an error. This bug looks complicate and it does not seem to be related to distributionMap: When I debug and I go down to the method DistributionMap>>elementsWithProperty:inPart: If I insert this lign: (elementsAndPropertyValue keys detect: [:each | each == element]). it returns me one element. Then if I execute: (elementsAndPropertyValue at: element) I have a KeyNotFound error

11 years, 5 months

Issue 555 in moose-technology: DSM improve visualization

by moose-technology＠googlecode.com

Status: New Owner: jannik.l...(a)gmail.com Labels: Type-Defect Priority-Medium Component-DSM Milestone-4.4 New issue 555 by jannik.l...(a)gmail.com: DSM improve visualization http://code.google.com/p/moose-technology/issues/detail?id=555 I made the structure for DSM visualization. Now, I should create script for each and make communications between them coherent.

11 years, 5 months

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 926 in moose-technology: Moose should offer ZeroConf support for quick installations

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: chisvasi...(a)gmail.com Labels: Type-Enhancement Priority-Medium Milestone-4.8 Maintainability New issue 926 by tu...(a)tudorgirba.com: Moose should offer ZeroConf support for quick installations http://code.google.com/p/moose-technology/issues/detail?id=926 Moose should offer the same support for quick installations as Pharo does. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

11 years, 5 months

Issue 931 in moose-technology: Moose Meta Browser - type and opposite values clipped on left

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 931 by alan.mcn...(a)gmail.com: Moose Meta Browser - type and opposite values clipped on left http://code.google.com/p/moose-technology/issues/detail?id=931 On selecing an Entity in the top left panel of the Moose Meta Browser, the Relation name/type/opposite are displayed. While the name is well displayed, the display of the type and opposite values are clipped on the left, and part of the first character cannot be seen. Similarly, if Property tab is selected, the type values are similarly clipped. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

11 years, 6 months

← Newer
1
2
3
4
5
6
7
8
9
...
20
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev May 2013