Moose-dev January 2011

moose-dev@list.inf.unibe.ch

23 participants
129 discussions

by Johan Fabry

Hi all, here we go again: I am looking for data to cite Glamour and Merlin. Any preferred papers? Thanks in advance! -- Johan Fabry jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile

14 years, 4 months

controbutors

by Tudor Girba

Hi, Please take a look at the list of contributors and let us know if we forgot someone: http://www.moosetechnology.org/about/halloffame It would be great to have the list up to date. Cheers, Doru -- www.tudorgirba.com "To lead is not to demand things, it is to make them happen."

14 years, 4 months

Re: Issue 479 in moose-technology: VerveineJ: next and previous values set for the associations

by moose-technology＠googlecode.com

Updates: Status: Fixed Owner: andrehoraa Comment #1 on issue 479 by andrehoraa: VerveineJ: next and previous values set for the associations http://code.google.com/p/moose-technology/issues/detail?id=479 (No comment was entered for this change.)

14 years, 4 months

Re: Issue 478 in moose-technology: In VerveineJ exports annotation instances and annotation types

by moose-technology＠googlecode.com

Updates: Status: Fixed Comment #1 on issue 478 by andrehoraa: In VerveineJ exports annotation instances and annotation types http://code.google.com/p/moose-technology/issues/detail?id=478 (No comment was entered for this change.)

14 years, 4 months

Issue 491 in moose-technology: VerveineJ: MSE is not exporting implemented interfaces

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 491 by andrehoraa: VerveineJ: MSE is not exporting implemented interfaces http://code.google.com/p/moose-technology/issues/detail?id=491 In VerveineJ the .mse file is not exporting the implemented interface(s) of a class. For example in LAN model the class XPrinter implements the interface that is not exported. Please fill in the labels with the following information: * Type-Defect * Component-Verveine

14 years, 4 months

FAMIXAnnotationInstance with SourceAnchor property?

by Andre Hora

Hello, Should not FAMIXAnnotationInstance have a SourceAnchor property? Regards, -- Andre Hora

14 years, 4 months

glamour, toolbars enable/disable items?

by Esteban Lorenzano

Hi, I wonder how can I enable/disable elements from toolbar, depending on selections in some presentations. I also wonder how can pass "arguments" to elements in toolbar: for example, I need an element in toolbar to know the selection of the list shown in the panel below. Cheers, Esteban

14 years, 4 months

.mse explanation/citation?

by Johan Fabry

Hi all, is there a paper that talks about / explains the .mse format that I can cite? A bibtex entry would be excellent ;-) Thanks in advance! -- Johan Fabry jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile

14 years, 4 months

Linear color normalizer

by Alexandre Bergel

Hi! I executed the following scripts: I would actually expect the same node colors. Apparently, the colors given by the normalizer are focused on 0. Is this what you would expect? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years, 4 months

Fwd: Re: xmlsupport conflict in pharo 1.2

by jaayer

============ Forwarded message ============ >From : jaayer To : "Alexandre Bergel" Date : Thu, 06 Jan 2011 07:27:20 -0800 Subject : Re: [Moose-dev] xmlsupport conflict in pharo 1.2 ============ Forwarded message ============ ---- On Wed, 05 Jan 2011 09:39:31 -0800 Alexandre Bergel wrote ---- >I had a quick look at it. >In Pharo 1.2, the XML-Parser parkage is clean (i.e.,not dirty). Loading XMLSupport turns the package dirty. The user is asked whether he is ready to lose his changes. I cannot determine why the packages turned dirty. > >Executing: >Gofer new > squeaksource: 'XMLSupport'; > package: 'ConfigurationOfXMLSupport'; > load. >(Smalltalk at: #ConfigurationOfXMLSupport) perform: #loadDefault. > >in a fresh image raises the popup. Without canceling or accepting, open a Monticello browser, you will see the package dirty. > >Jaaryer, can you have a look at it? There is something weird with the configuration. I sincerely hope we will have a better tool for managing configuration. I am currently working on it, but it is still too early for releasing it. > >Cheers, >Alexandre Is the package in Pharo 1.2 the most recent version? Reading the discussion from last month, it appeared they were opting for an older version. The only Pharo 1.2 image I can find on the website is a barren core without XMLSupport in it. Regardless, if you load any of the recent XMLSupport packages and run the test suite, it will dirty the XML-Tests-Parser package. To understand why, just browse the XMLParserElementFactoryTest class or read its comment; it generates a number of "dummy" subclasses of XMLElement for testing purposes in its #setUp message and removes those classes from the system in its #tearDown message. I have known about this for weeks but did not consider it to be a problem as other packages ("Tests", for example) always seem to have an asterisk beside them in the Monticello browser and nothing seems break as a result. I can easily change this to make those classes static (always present) rather than dynamically generated/removed, if this is a problem. >On 5 Jan 2011, at 11:41, Tudor Girba wrote: > >> Hi, >> >> XMLSupport is present in the latest Pharo 1.2. Loading a new version generates an exception apparently, so I removed for the moment XMLSupport from the default ConfigurationOfMoose. >> >> I think we should only load this conditionally. Or do you have another solution? >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> >> "Every thing should have the right to be different." >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > >-- >_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >Alexandre Bergel http://www.bergel.eu >^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > >

14 years, 4 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev January 2011