April 2014 - Moose-dev

Issue 1067 in moose-technology: MoosePanel panes showing group should be sorted

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1067 by james.fo...(a)gemtalksystems.com: MoosePanel panes showing group should be sorted http://code.google.com/p/moose-technology/issues/detail?id=1067 I can resort them by executing a Smalltalk expression, but the default order should be meaningful rather than random. * Type-Enhancement * Component-MoosePanel -- 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

8 years, 8 months

1
3
0 / 0

Issue 1069 in moose-technology: Use self notExistentMetricValue instead of -1 in some metrics of MooseEntities

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1069 by v.blonde...(a)gmail.com: Use self notExistentMetricValue instead of -1 in some metrics of MooseEntities http://code.google.com/p/moose-technology/issues/detail?id=1069 Describe the problem: what do you get? what do you expect? FAMIXBehaviouralEntity, FAMIXType, FAMIXFileAnchor and FAMIXSourceTextAnchor define metrics where -1 is used instead of self notExistentMetricValue. Additional information: platform, context which may impact the problem Moose 5.0 Please fill in the labels with the following information: * Type-Enhancement * Component-Moose-Core -- 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

8 years, 8 months

1
2
0 / 0

Issue 1039 in moose-technology: Glamour layout clipping bug

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1039 by ssadams....(a)gmail.com: Glamour layout clipping bug http://code.google.com/p/moose-technology/issues/detail?id=1039 When sizing a presentation row, I noticed the bottom pane extends below the top window bounds and is clipped. browser := GLMTabulator new. browser row:#textField size:30; row: #listField. browser transmit to:#textField; andShow:[:a| a text display:[:x| 'Hello Doru!']]. browser transmit to:#listField; andShow:[:a| a list display:[:x| 1to:200]]. browser openOn: 123 Additional information: platform, context which may impact the problem Pharo 2.0 ConfigurationOfGlamour-TudorGirba.123 * Type-Defect * Component-Glamour -- 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

8 years, 8 months

1
3
0 / 0

Issue 757 in moose-technology: Smalltalk completion appears at absolute coordinates, instead of relative ones in Finder

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Glamour New issue 757 by tudor.gi...(a)gmail.com: Smalltalk completion appears at absolute coordinates, instead of relative ones in Finder http://code.google.com/p/moose-technology/issues/detail?id=757 Try this: GLMFinder new show: [:a | a smalltalkCode ]; openOn: ''. and then type "1 as". You will see that the completion appears in the top right of the world, instead of the top right of the text pane. This only happens in the finder, and it is likely due to some problems of transforming coordinates.

8 years, 8 months

2
3
0 / 0

Issue 1037 in moose-technology: Missing context menu in GTDebugger code editor

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium New issue 1037 by kurs....(a)gmail.com: Missing context menu in GTDebugger code editor http://code.google.com/p/moose-technology/issues/detail?id=1037 I really miss the context menu in the gt debugger code editor. It is not consistent with standard editor menu it is not consistent with the browse/inspect context menu in the bottom part of the debugger. -- 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

8 years, 9 months

1
4
0 / 0

working towards initial LEKtrek 0.1 release

by Ben Coman

For the past few months I've been distracted by working on Issues for Pharo 3.0 Beta. Now that it is almost released, its time for me to return to packaging my masters project for release (it was good to have the break after handing everything in). I wrote my project on top of Moose 4.7-Development and I have modification against some of the packages. Some of these are not worth merging into the current HEAD since I'll be migrating to GraphET and Roassal2. However it would be good to have them somewhere I can reference them for a Configuration of a working system before I do that migration. It would be useful for them to be in their main repositories rather than trying to work out something else. Can I get access to upload to the EyeSee, Glamour, Magritte and Roassal repositories? Here is a summary of what I would upload, compared to Moose47 and latest versions: * EyeSee had extension Dictionary class >> keys:values: that hardcoded a reference to 'Dictionary' preventing use by subclasses that I had. So I change that reference to 'self'. Latest EyeSee-Core-VincentBlondeau.110 Moose47 EyeSee-Core-AndreHora.100 LEKtrek01 EyeSee-Core-BenComan.101 * I added two features to Magritte: * MADropDownListMorph * MASeparatorMorph Latest Magritte-Morph-SeanDeNigris.86 Moose47 Magritte-Morph-NickAger.63 LEKtrek01 Magritte-Morph-BenComan.66 * I introduced #newView: to Glamour-Roassal so that #painting: could receive a raw ROView rather than only ROMondrianBuilder. I believe similar functionality ended up being integrated into the mainline later on, but there are too many other changes for me to catch up for the 0.1 release. Latest Glamour-Morphic-Renderer-AndreiChis.239 Moose47 Glamour-Morphic-Renderer -TudorGirba.183 LEKtrek01 Glamour-Morphic-Renderer -BenComan.181 Latest Glamour-Roassal-Presentations-TudorGirba.20 Moose47 Glamour-Roassal-Presentations-TudorGirba.8 LEKtrek01 Glamour-Roassal-Presentations-BenComan.10 Latest Glamour-Tests-Roassal-TudorGirba.6 Moose47 Glamour-Tests-Roassal-TudorGirba.4 LEKtrek01 Glamour-Tests-Roassal-BenComan.5 * I ended up a long way behind with Roassal. I added several features that I think some made their way into the mainline, but I just didn't keep up: * adjust popup position * added selections * drag multiple items at a time * work with ROView in Glamour * keypress modifiers shift/control/alt Latest Roassal-AlexandreBergel.757 Moose47 Roassal-AlexandreBergel.476 LEKtrek01 Roassal-BenComan.396 Latest RoassalMorphic-AlexandreBergel.170 Moose47 RoassalMorphic-VanessaPena.111 LEKtrek01 RoassalMorphic-BenComan.81 cheers -ben

8 years, 10 months

2
2
0 / 0

how to get a redbox

by Stéphane Ducasse

Take latest moose click on Freetype to deselect it/ click to reselect it execute in workspace TRExample new label -> Boum. Can you confirm that behavior? Now I can reproduce it so I will see if I have the time to fix it. Stef

8 years, 10 months

6
7
0 / 0

Issue 1038 in moose-technology: Debugger Shortcuts Problems

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-GlamorousToolkit New issue 1038 by kurs....(a)gmail.com: Debugger Shortcuts Problems http://code.google.com/p/moose-technology/issues/detail?id=1038 While using shortcuts in debugger, e.g. alt+t for step over, once upon a time the focus is moved from the stack window to the code window and alt+t starts modifying the text. One has to click back to the stack window... How to reproduce the problem: Just use debugger with alt+t for some time. Additional information: Ubuntu x64 -- 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

8 years, 10 months

1
2
0 / 0

Issue 1051 in moose-technology: MessageNotUnderstood: GLMTextMorphForEditView>>textMorph

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1051 by info.lan...(a)gmail.com: MessageNotUnderstood: GLMTextMorphForEditView>>textMorph http://code.google.com/p/moose-technology/issues/detail?id=1051 I've been trying to execute a script in the new workspace. This script needed a temporary variable so I clicked on : Declare new ... And the error occurred MessageNotUnderstood: GLMTextMorphForEditView>>textMorph -- 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

8 years, 10 months

1
4
0 / 0

Issue 1032 in moose-technology: GLMPresentation>>dynamicActionsOnSelection does not work for text presentations

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Glamour New issue 1032 by chisvasi...(a)gmail.com: GLMPresentation>>dynamicActionsOnSelection does not work for text presentations http://code.google.com/p/moose-technology/issues/detail?id=1032 Text presentations have the selection in the port 'selectedText'. GLMPresentation>>dynamicActionsOnSelection only computes the actions if the 'selection' port is populated. Thus, it does not work for text presentations. -- 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

8 years, 10 months

1
1
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev April 2014