Moose-dev May 2011

moose-dev@list.inf.unibe.ch

33 participants
186 discussions

by Alexandre Bergel

Since many of us are working on user interface, I found this one: http://www.ringbow.com/features/concept Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 7 months

Re: Issue 615 in moose-technology: cleaning package cycles: MooseScripts

by moose-technology＠googlecode.com

Updates: Summary: cleaning package cycles: MooseScripts Comment #3 on issue 615 by tudor.gi...(a)gmail.com: cleaning package cycles: MooseScripts http://code.google.com/p/moose-technology/issues/detail?id=615 (No comment was entered for this change.)

13 years, 7 months

Re: Issue 614 in moose-technology: cleaning package cycles: PackageBlueprint

by moose-technology＠googlecode.com

Updates: Summary: cleaning package cycles: PackageBlueprint Comment #5 on issue 614 by tudor.gi...(a)gmail.com: cleaning package cycles: PackageBlueprint http://code.google.com/p/moose-technology/issues/detail?id=614 (No comment was entered for this change.)

13 years, 7 months

Issue 614 in moose-technology: cleaning package cycles

by moose-technology＠googlecode.com

Status: Accepted Owner: ---- CC: cy.delau...(a)gmail.com Labels: Type-Defect Priority-Medium Difficulty-Easy Milestone-4.4 New issue 614 by jannik.l...(a)gmail.com: cleaning package cycles http://code.google.com/p/moose-technology/issues/detail?id=614 There are lots of cycle in Moose (run a dsm on moose). One of them can be cleaned simply: PackageBlueprint>>createMerlinMode PackageBlueprint>>openMerlinExperimentBrowser PackageBlueprint>>openMondrianExperimentBrowser PackageBlueprint>>openGlamourExperimentBrowser do not work, can I remove them ?

13 years, 7 months

Moose/Glamour is cool (and I have questions!)

by Mariano Martinez Peck

Hi guys. Since several months, I wanted to create a little browser for learning VM and related stuff. I never did anything because I was lazy. Last week, I took Glamour and without knowing almost anything about it, in less than 3 hours (that includes everything, downloading the image, browsing examples, searching for something similar to what I need, and code the browsers I needed) , I come up with what I want to share with you. Basically, I only have the browsers for the moment. My knowledge is very limited in the Slang to C translator, or machine code simulation. However, the "real VM hackers" will try to provide me such functionalities. Having said that, there are 3 browsers: 1) VMBrowserSlang: shows only packages and classes which are written in slang. When you select a method, you have 2 panels: smalltalk code and C translated code. Screenshot: http://img857.imageshack.us/i/vmbrowserslang.png/ 2) VMBrowserMethods: shows all packages and classes of the system and for every method, you have 3 panels: smalltalk code, bytecodes and machine code (using the simple mapping) Screenshot: http://img862.imageshack.us/i/vmbrowsermethods.png/ 3) VMBrowserMappings: this is for you Eliot!! Basically, it shows all packages and classes of the system and for every method, you have 5 panels: smalltalk code and one panel per strategy to map to machine code (simple cogit, sista, etc). Screenshot: http://img4.imageshack.us/f/vmbrowsermappings.png/ As you can see the idea is to see the different stages of our code at the same time: smalltalk code, bytecodes, machine code, etc. The idea is to easily learn. Now...the questions: 1) how can I put a title to the browsers ? In this case, they all are subclasses from GLMGlobalBrowserTemplate. 2) Is there a way to easily "close" and auto-adjust subpanes? For example, look this screenshot: http://img4.imageshack.us/f/vmbrowsermappings.png/ there are 5 panes that are rendered when a method is selected. I would love that somehow (which a little X in the tab title, or a checkbox somewhere with the available panes), one or more of those panes can be automatically removed (and if added again even better). And when I remove one of them, the others auto-adjust to ocupy the full container. It is really difficult to explain by email.. Thanks in advance -- Mariano http://marianopeck.wordpress.com

13 years, 7 months

Issue 615 in moose-technology: cleaning package cycles

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Difficulty-Easy Milestone-4.4 New issue 615 by jannik.l...(a)gmail.com: cleaning package cycles http://code.google.com/p/moose-technology/issues/detail?id=615 Move class MooseScripts in SmalltalkImporter

13 years, 7 months

Re: Hudson build is back to normal : moose-latest-dev #343

by Alexandre Bergel

Yahhooo!!!!!!!! Alexandre On 5 May 2011, at 08:10, admin(a)moosetechnology.org wrote: > See <http://hudson.moosetechnology.org/job/moose-latest-dev/343/> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 7 months

Using Candidate

by Alexandre Bergel

Hi! Having a proper list of candidates when importing Smalltalk code is crucial. Without this, it is not possible to seriously analyze Smalltalk code. How to use the Roel Typer? I guess I have to tick "Compute type of attributes" in the wizard. But which strategy to compute invocation candidates should I use? I tried when I get an error from the typer. We absolutely need to fix this. Cyrille, did you manage to get this to work? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 7 months

Issue 606 in moose-technology: FAMIXPackage>>methods is wrong

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Famix Milestone-4.4 New issue 606 by tudor.gi...(a)gmail.com: FAMIXPackage>>methods is wrong http://code.google.com/p/moose-technology/issues/detail?id=606 in FAMIXPackage, methods only returns the extended methods defined in the package: FAMIXPackage>>methods ^ self privateState cacheAt: #methods ifAbsentPut: [ childNamedEntities select: [ :child | child isKindOf: FAMIXBehaviouralEntity ]] This has a different semantics from the one defined in Namespace: FAMIXNamespace>>methods ^ self privateState cacheAt: #methods ifAbsentPut: [ self classes flatCollect: #methods ] So. I propose that FAMIXPackage>>methods is changed to extensionMethods and methods is computed like in Namespace + extensionMethods.

13 years, 7 months

FAMIXMethod>>parentPackage

by Laval Jannik

Hi, I changed the behavior of FAMIXMethod>>parentPackage. In fact, when a method is in the same package than its class, its parentPackage should be nil. So, to not break the behavior, I changed the accessor like this: === parentPackage ^ parentPackage ifNil:[ self belongsTo parentPackage] === But this breaks during importation of MSE files (it breaks some tests of smalldude and eyesee). The problem is due to the class that is not already defined during the importation. So I changed the source code like that. I am not convince of the efficiency of this code. Have you another idea ? === parentPackage ^ parentPackage ifNil:[ |cl| cl := self belongsTo. cl isNil ifTrue:[nil] ifFalse:[cl parentPackage] ] === --- Jannik Laval

13 years, 7 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev May 2011