Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Issue 492 in moose-technology: Glamour browsers do not release all subscriptions to announcer objects

by moose-technology＠googlecode.com

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-High Component-Glamour Milestone-4.3 New issue 492 by tudor.gi...(a)gmail.com: Glamour browsers do not release all subscriptions to announcer objects http://code.google.com/p/moose-technology/issues/detail?id=492 I noticed that in some complex updating between panels, using an external announcer, some of the update subscriptions were not removed when the browser is closed. I debugged a little and I founded that this implementation: GLMUpdateAction>>unregisterFromAllAnnouncements announcerObjects ifNotNil: [ announcerObjects do: [:each | each unsubscribe: self ] ] is bugged, because if announcerObjects are not previously computed (and in some cases that's what happens), the subscription is not removed. This implementation (just using the accessor instead the direct object), solves the problem (but I don't know is it's a right fix, and it should be a fix in other place) GLMUpdateAction>>unregisterFromAllAnnouncements self announcerObjects ifNotNil: [ :objects | objects do: [:each | each unsubscribe: self ] ] Cheers, Esteban

13 years, 9 months

color for seaside

by Tudor Girba

Hi Cyrille, I saw that you added a GLMColor to provide an abstract representation of a Color both for Morphic and for CSS. It's good that you are tackling this problem, but this is not the way to go. The problem is that it is confusing to have to provide a new GLMColor class for every special color. Color is already a full and quite powerful description of a color. What we need is a convertor. There already are a few: - Color>>printHtmlString (in the base image) - Color>>asJavascript (in the Seaside image) The only thing that is currently missing is a proper translation of "Color transparent", but this can be done easily in a Color>>glmAsHtmlColor. Cheers, Doru -- www.tudorgirba.com "Not knowing how to do something is not an argument for how it cannot be done."

13 years, 9 months

Issue 630 in moose-technology: Glamour: #sendTo:from:with: does not refresh selection in lists

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 630 by vuqui...(a)vub.ac.be: Glamour: #sendTo:from:with: does not refresh selection in lists http://code.google.com/p/moose-technology/issues/detail?id=630 Describe the problem: what do you get? what do you expect? When I use #sendTo:from:with: the panel update is not refreshing the selected item in a list. How to reproduce the problem: step by step if necessary Escenario (example attached): A GLMStacker with two panes working as an inner browser. - when I send a external value to the inner browser the value is assigned but the item does not appear as selected. - when I select a value in one of the panes of the inner browser it sends nil to the selected value in the other pane... The same: the value changes to nil but if it was a selected item it remains selected. Additional information: platform, context which may impact the problem Please fill in the labels with the following information: * Type-Defect * Component-Glamour Attachments: Example.st 1.3 KB

13 years, 9 months

Issue 678 in moose-technology: Shortcuts do not work in Text morphs anymore

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.6 New issue 678 by tu...(a)tudorgirba.com: Shortcuts do not work in Text morphs anymore http://code.google.com/p/moose-technology/issues/detail?id=678 Open an evaluator pane in the MoosePanel, select something and press cmd+/. The text gets replaced by '/'.

13 years, 9 months

magritte forms for elements in a collection

by Tudor Girba

Hi, I have the following use case that I want to solve using Magritte. I have entities that have Magritte descriptions. If I have one entity, I can nicely edit its description, and when I press Save, it changes the values from the entities. Now, I also have collections of entities that have the same descriptions I would like to use the rendering of Magritte to edit the values for all entities in the collection and when I press Save it should change the values for all entities. Is there any direct support for something like that? Cheers, Doru -- www.tudorgirba.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

13 years, 10 months

Class naming cohesion demo

by Simon Denier

Hi Doru I just took a look at your last demo there and while trying to reproduce, I got some errors in Moose 4.5 due to unknown messages http://www.humane-assessment.com/blog/exploring-class-naming-cohesion Namely #identityFillColorOf: and #pairsDistanceFrom Also it seems like the shortcuts cmd+o cmd+/ do not work anymore in the evaluator pane. -- Simon Denier

13 years, 10 months

Moose at GotoCon Aarhus / registration discount

by Tudor Girba

Hi, This fall I will give a talk at GotoCon Aarhus (Oct 9-14) on "Humane assessment with Moose": http://gotocon.com/aarhus-2011/speaker/Tudor+Girba GotoCon used to be named JAOO. It is a large industrial software development conference that might of interest to some of you. As part the speaker package I have the possibility to offer discounts to interested participants. So, if you want to go to GotoCon Aarhus and are interested in a discount of about 170 EUR, please send me an email and I will provide the promotion code. Cheers, Doru -- www.tudorgirba.com "One cannot do more than one can do."

13 years, 10 months

petit gui in pharo 1.3?

by Norbert Hartl

I'm in the progress to change all my working images to pharo 1.3. Now I encounter that the PetitGUI is not working in pharo 1.3 for me. I've built the image from pharo 1.3 core. I loaded PetitGui via ConfigurationOfPetitParser which gives me the same package revisions that I have in my 1.2 image. I fixed a missing super initialize in GLMLoggedObject and that enables me to open the petit gui. I can see an the left side all parser classes to chose from. But clicking on any of them does not give the rule selection in the right side (and of course no pane at the bottom). Are there any known issues? Are there hints how to fix it or where to look at? thanks, Norbert

13 years, 10 months

Issue 665 in moose-technology: MooseMenu - package wise system complexity

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 665 by jannik.l...(a)gmail.com: MooseMenu - package wise system complexity http://code.google.com/p/moose-technology/issues/detail?id=665 In the menu on a packageGroup package wise system complexity has a Zero Divide

13 years, 10 months

Issue 662 in moose-technology: MooseMenu - distributionMap for these elements - DNU

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 662 by jannik.l...(a)gmail.com: MooseMenu - distributionMap for these elements - DNU http://code.google.com/p/moose-technology/issues/detail?id=662 I just did "next", "finish" without configuring anything, I have a DNU === You have to think a bit about what the distribution map is supposed to show and make sensible choices. Default choices may not work since they are computed from the metamodel without regards. --> Maybe the wizard should be configurable with default (sensible) choices so that you don't get the DNU.

13 years, 10 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev