Hi,
I'm Cyrille Delaunay, working in Stephane Ducasses team in Lille, France and
I will do a lot of things for moose during the next two years :)
The first thing I've made is an interface that enable the user to open a
moose finder by specifying:
- image packages that he want to import
- the importing context
- merging or not class and metaclass
I just save that in the moose squeaksource repository.
Two packages are concerned :
- Moose-Finder with three new classes
- MooseImportInterface : the main class (just evaluate
'MooseImportInterface new open')
- PackageSelector
- ContextFrame
- Moose-GenericImporter :
- Some missing methods added in the class ImportingContext
Hi Eduardo,
Great to hear that you are using Moose. I would suggest to send
technical questions to the moose-dev mailing list. You can subscribe
here:
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Which version of Moose are you using?
If you are using the VisualWorks version, then:
- to zoom, you have to click on the + button
- to export, you right click on the canvas and choose export to PNG
Also, I would be curious to learn more about the context in which you
use Moose. Could you tell us more details?
Cheers,
Doru
On 15 Oct 2009, at 16:07, Eduardo Guerra wrote:
> Hi!
>
> My name is Eduardo Guerra and in my PhD Thesis I'm using polimetric
> views to evaluate the design of applications that uses different kinds
> of framework.
>
> I read the book Object-oriented Metrics in Practice and I want to use
> Moose for the generation of the views.
>
> I had two questions:
>
> - I'm using small case studies and the generated views are too small.
> Can I zoom them?
> - I need to export the view to include in my papers and in my thesis.
> How can I export a generated view?
>
> Thanks a lot!
>
> Eduardo Guerra
> _______________________________________________
> Moose mailing list
> Moose(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose
--
www.tudorgirba.com
"Obvious things are difficult to teach."
Hi Doru,
In Glamour,
I would like to update a pane when I add new items in the entry
collection.
For example:
===
"self new test openOn: myCollection"
|browser |
browser := GLMTableLayoutBrowser new.
browser column: #one.
browser showOn: #one; using: [
browser list
display: [:x | x];
act: [:each | myCollection add: each] entitled: 'duplicate';
].
===
In the browser, I need an action which update display when I change
the input.
Here, I have an action which add an entity in "myCollection".
How can I update display ?
I tried to use update:on:entitled:with: but it does not work.
Have you a solution ?
Cheers
---
Jannik Laval
PhD Student - Rmod Team - INRIA
Certified Project Management Associate (IPMA)
http://www.jannik-laval.euhttp://rmod.lille.inria.fr
---
Hi!
Apparently, Moose cannot be loaded with the last version of Gofer.
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
Apparently, there is something not okay in the way isPublic and
isPrivate are computed.
The screenshot says everything.
Do I use the wrong method or something?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
A problem with IdentityDictionary.
Some references are not available.
I don't know why...
Cheers
---
Jannik Laval
PhD Student - Rmod Team - INRIA
Certified Project Management Associate (IPMA)
http://www.jannik-laval.euhttp://rmod.lille.inria.fr
---
A problem with IdentityDictionary.
Some references are not available.
I don't know why...
Cheers
---
Jannik Laval
PhD Student - Rmod Team - INRIA
Certified Project Management Associate (IPMA)
http://www.jannik-laval.euhttp://rmod.lille.inria.fr
---
Let's say I have three panes with three collection of data: A, B, and C
I want each pane to always display its full list of data.
But, data are also interconnected: data in A points to some data in B,
which points to data in C.
So that when I select some data in a pane (say A), I dont want the
other panes to filter their data, I just want them to update their
selection.
is that currently possible in Glamour?
Some ascii art to the rescue :)
When I select a1, I want b1 and b3 selected in B, and as a consequence
c2, c4, and c5 are also selected in C
A | B | C
a1* | b1* | c1
a2 | b2 | c2*
a3 | b3* | c3
| b4 | c4*
| | c5*
--
Simon
Begin forwarded message:
> From: Lukas Renggli <renggli(a)me.com>
> Date: September 30, 2009 9:10:32 PM GMT+02:00
> To: Stéphane Ducasse <stephane.ducasse(a)inria.fr>
> Cc: Simon Denier <simon.denier(a)inria.fr>
> Subject: Re: [Moose-dev] Re: MooseLoader load does not load Fame ?
>
> Please try again. There was something messed up dependencies. I
> think it should be fixed with the latest Gofer.
>
> It certainly is not an issue with Monticello itself. I am using
> Gofer also with some older projects on Squeak 3.9.1
>
> Lukas
>
>
> On Sep 30, 2009, at 21:08 , Stéphane Ducasse wrote:
>
>> I'm not sure that this is related to that.
>>
>> Stef
>>
>> Begin forwarded message:
>>
>>> From: Simon Denier <Simon.Denier(a)inria.fr>
>>> Date: September 30, 2009 4:36:40 PM GMT+02:00
>>> To: Simon Denier <Simon.Denier(a)inria.fr>
>>> Cc: Related to the development of Moose and other related tools <moose-dev(a)iam.unibe.ch
>>> >, Lukas Renggli <renggli(a)iam.unibe.ch>
>>> Subject: [Moose-dev] Re: MooseLoader load does not load Fame ?
>>> Reply-To: Related to the development of Moose and other related
>>> tools <moose-dev(a)iam.unibe.ch>
>>>
>>>
>>> On 30 sept. 2009, at 16:13, Simon Denier wrote:
>>>
>>>>
>>>> it could be related to last changes in gofer
>>>
>>> confirmed: works with gofer 48, not anymore with gofer 49 (fast
>>> multi package). Now there is a MC fix in the PharoInbox related to
>>> this so I guess that latest versions of gofer do not work without
>>> this fix.
>>>
>>>>
>>>>
>>>> On 30 sept. 2009, at 16:02, Alexandre Bergel wrote:
>>>>
>>>>> Squeaksource is up again. I tried, and I have the same problem
>>>>> than Jannik. I used a the last pharo-dev image available on the
>>>>> net. I used a 4.2.1 VM.
>>>>>
>>>>> Cheers,
>>>>> Alexandre
>>>>>
>>>>> On 30 Sep 2009, at 08:57, Tudor Girba wrote:
>>>>>
>>>>>> Hmm,
>>>>>>
>>>>>> I am using the 4.2.1 VM. I will try with the 4.2.2 later this
>>>>>> evening.
>>>>>>
>>>>>> Can anyone else reproduce the problem in the meantime?
>>>>>>
>>>>>> Cheers,
>>>>>> Doru
>>>>>>
>>>>>>
>>>>>> On 30 Sep 2009, at 14:53, Laval Jannik wrote:
>>>>>>
>>>>>>> I use a clean pharoCore 462 and a clean pharoDev 451.
>>>>>>> With the last VM (4.2.2)
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sep 30, 2009, at 14:38 , Tudor Girba wrote:
>>>>>>>
>>>>>>>> Hi Jannik,
>>>>>>>>
>>>>>>>> I again cannot reproduce this problem :). I just loaded
>>>>>>>> without a problem in pharo1.0-10451-BETAdev09.09.3.
>>>>>>>>
>>>>>>>> In which Pharo version did you try to load MooseLoader?
>>>>>>>>
>>>>>>>> Doru
>>>>>>>>
>>>>>>>>
>>>>>>>> On 30 Sep 2009, at 14:13, Laval Jannik wrote:
>>>>>>>>
>>>>>>>>> "MooseLoader load" does not work.
>>>>>>>>> It makes a warning:
>>>>>>>>> "
>>>>>>>>> This package depends on the following classes:
>>>>>>>>> FMImporter
>>>>>>>>> FMPragmaProcessor
>>>>>>>>> FM3PropertyDescription
>>>>>>>>> FM3MetaDescription
>>>>>>>>> FMDomainCodeGenerator
>>>>>>>>> MOViewRenderer
>>>>>>>>> You must resolve these dependencies before you will be able
>>>>>>>>> to load these definitions:
>>>>>>>>> FM3MetaDescription>>allComplexAttributes
>>>>>>>>> FM3MetaDescription>>allPrimitiveAttributes
>>>>>>>>> FM3MetaDescription>>complexAttributes
>>>>>>>>> FM3MetaDescription>>primitiveAttributes
>>>>>>>>> FM3PropertyDescription>>compiledMethod
>>>>>>>>> FameGetterGenerator
>>>>>>>>> FameGetterGenerator>>instvarNameFor:
>>>>>>>>> FameGetterGenerator>>methodNameFor:
>>>>>>>>> FameGetterGenerator>>oppositeNameFor:
>>>>>>>>> FameGetterGenerator>>visitClass:
>>>>>>>>> FameGetterGenerator>>visitDictionaryProperty:
>>>>>>>>> FameGetterGenerator>>visitManyProperty:
>>>>>>>>> FameGetterGenerator>>visitOneProperty:
>>>>>>>>> FameGetterGenerator>>visitOppositeDictionaryProperty:
>>>>>>>>> FameGetterGenerator>>visitOppositeManyProperty:
>>>>>>>>> FameGetterGenerator>>visitOppositeOneProperty:
>>>>>>>>> MOViewRenderer>>edgesDsm:from:to:
>>>>>>>>> MSEImporter
>>>>>>>>> MSEImporter>>endDocument
>>>>>>>>> MSEPragmaProcessor
>>>>>>>>> MSEPragmaProcessor>>processClass:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Select Proceed to continue, or close this window to cancel
>>>>>>>>> the operation.
>>>>>>>>> "
>>>>>>>>>
>>>>>>>>> So Fame is not loaded.
>>>>>>>>>
>>>>>>>>> Is there a bug in Flair/Gofer ?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---
>>>>>>>>> Jannik Laval
>>>>>>>>> PhD Student - Rmod Team - INRIA
>>>>>>>>> Certified Project Management Associate (IPMA)
>>>>>>>>> http://www.jannik-laval.eu
>>>>>>>>> http://rmod.lille.inria.fr
>>>>>>>>> ---
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Moose-dev mailing list
>>>>>>>>> Moose-dev(a)iam.unibe.ch
>>>>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>>>>
>>>>>>>> --
>>>>>>>> www.tudorgirba.com
>>>>>>>>
>>>>>>>> "Beauty is where we see it."
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Moose-dev mailing list
>>>>>>>> Moose-dev(a)iam.unibe.ch
>>>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>>>
>>>>>>> ---
>>>>>>> Jannik Laval
>>>>>>> PhD Student - Rmod Team - INRIA
>>>>>>> Certified Project Management Associate (IPMA)
>>>>>>> http://www.jannik-laval.eu
>>>>>>> http://rmod.lille.inria.fr
>>>>>>> ---
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Moose-dev mailing list
>>>>>>> Moose-dev(a)iam.unibe.ch
>>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>>
>>>>>> --
>>>>>> www.tudorgirba.com
>>>>>>
>>>>>> "Not knowing how to do something is not an argument for how it
>>>>>> cannot be done."
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Moose-dev mailing list
>>>>> Moose-dev(a)iam.unibe.ch
>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>
>>>> --
>>>> Simon
>>>>
>>>>
>>>>
>>>
>>> --
>>> Simon
>>>
>>>
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> Moose-dev(a)iam.unibe.ch
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
>
Hi,
Moose Suite 4.0 beta is now available:
http://moose.unibe.ch/download
We would need to test it a bit on different platforms. Feedback is
more than welcome :)
Cheers,
Doru
--
www.tudorgirba.com
"Some battles are better lost than fought."
"MooseLoader load" does not work.
It makes a warning:
"
This package depends on the following classes:
FMImporter
FMPragmaProcessor
FM3PropertyDescription
FM3MetaDescription
FMDomainCodeGenerator
MOViewRenderer
You must resolve these dependencies before you will be able to load
these definitions:
FM3MetaDescription>>allComplexAttributes
FM3MetaDescription>>allPrimitiveAttributes
FM3MetaDescription>>complexAttributes
FM3MetaDescription>>primitiveAttributes
FM3PropertyDescription>>compiledMethod
FameGetterGenerator
FameGetterGenerator>>instvarNameFor:
FameGetterGenerator>>methodNameFor:
FameGetterGenerator>>oppositeNameFor:
FameGetterGenerator>>visitClass:
FameGetterGenerator>>visitDictionaryProperty:
FameGetterGenerator>>visitManyProperty:
FameGetterGenerator>>visitOneProperty:
FameGetterGenerator>>visitOppositeDictionaryProperty:
FameGetterGenerator>>visitOppositeManyProperty:
FameGetterGenerator>>visitOppositeOneProperty:
MOViewRenderer>>edgesDsm:from:to:
MSEImporter
MSEImporter>>endDocument
MSEPragmaProcessor
MSEPragmaProcessor>>processClass:
Select Proceed to continue, or close this window to cancel the
operation.
"
So Fame is not loaded.
Is there a bug in Flair/Gofer ?
---
Jannik Laval
PhD Student - Rmod Team - INRIA
Certified Project Management Associate (IPMA)
http://www.jannik-laval.euhttp://rmod.lille.inria.fr
---
Hi all,
There are 56 failures in SmalltalkImporterTest.
No accesses and Invocations are imported.
Any Idea ?
Cheers
---
Jannik Laval
PhD Student - Rmod Team - INRIA
Certified Project Management Associate (IPMA)
http://www.jannik-laval.euhttp://rmod.lille.inria.fr
---
Running all tests from Moose spawns:
1007 run, 994 passes, 13 expected failures, 0 failures, 0 errors, 0
unexpected passes
Not bad :)
Doru
--
www.tudorgirba.com
"Don't give to get. Just give."
Dear List,
A number of improvements are available:
- the class MondrianHealth has been introduced. This class aims to
generate report about the general healt of Mondrian, including speed
and memory benchmarks, test coverage. It is a bit empty so far, but it
will grow over the time.
- Each node is now aware of incoming and outgoing edges. This is
necessary to fix the Google ISSUE #100. The version in Visualworks is
similar on this.
- Bug related to copyShapeAndDo: is fixed.
copyShapeWithoutUpdatingAndDo: has been added to avoid unnecessary
window update
- MOGraphElement>>isSelected takes the forwarding into account.
- MOGraphElement>>withAllSubnodes introduced, however its
implementation may be optimized
- expectedFailures are defined, which make all the test green!
- More test are added, the coverage is now at 60.41%
- Bug related to event forward is fixed. Nodes may be drag and drop in
the class blueprint.
- Dead code in MOViewRenderer has been removed.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi all,
I made a small fix of MooseLoader: it installed an old version of OB,
with the ScriptLoader.
So, I created a method loadOB which install the last version of OB and
O2
Cheers
---
Jannik Laval
PhD Student - Rmod Team - INRIA
Certified Project Management Associate (IPMA)
http://www.jannik-laval.euhttp://rmod.lille.inria.fr
---
Hi,
I went a bit over the nice Famix-Extensions.
I believe we still need to revise the vocabulary a tiny bit. Right now
we use "referenced/referencing" to denote invocations related
relationships. It should be "invoked/invoking".
I filed an issue and probably start to slowly rename the methods:
http://code.google.com/p/moose-technology/issues/detail?id=175
Cheers,
Doru
--
www.tudorgirba.com
"Sometimes the best solution is not the best solution."
Hi,
I tried on Windows.
After running ._moose.exe I get (translated from german):
The CPU has discovered an invalid instruction.
CS:0fb0 IP:010a OP:63 20 4f 53 20 ..etc.. Click "close" to terminate the application.
Regards
Pascal
Pascal Vollmer
Email: pascal.vollmer(a)ieee.org
Comedy-Battle! Jetzt ablachen und voten! Neue Comedians, Spontanhumoristen und Nachwuchs-Spaßmacher machen gute Laune - bestimmen Sie den Wochensieger!
http://comedy-battle.arcor.de/
Hi all
In the smalltalk importer for Famix 3, 'Smalltalk' is considered as a
namespace. As a consequence, any method which accesses Smalltalk is
tagged as making a FamixReference to the namespace.
Problem is, Cook assumes that any outgoing references made by a method
should be a FamixType.
So, what is right?
- 'Smalltalk' in a method should be considered as an access to a
global variable?
- or Cook should be more careful and select only references to
FamixType.
--
Simon
Hi,
This method sends message parentClass to a FamixMethod (inv accessor).
The method parentScope is not defined in FamixMethod.
Should we take the parentScope of FamixClass ?
FamixGlobalVariable>>isPublic
^ self incomingAccesses anySatisfy: [:inv |
inv accessor parentScope ~~ self parentScope]
Cheers
---
Jannik Laval
PhD Student - Rmod Team - INRIA
Certified Project Management Associate (IPMA)
http://www.jannik-laval.euhttp://rmod.lille.inria.fr
---
Hi Damien,
This is a known issue and it will be tackled:
http://code.google.com/p/moose-technology/issues/detail?id=111
Cheers,
Doru
On 4 Sep 2009, at 09:57, Damien Cassou wrote:
> Hi,
>
> imagine I want to merge the method categories and selectors panes in a
> single list for a code browser. I would like selectors to appear with
> their categories in parenthesis (as in NewSpeak if you had a look).
> For the class GLMSmalltalkExamples, that would be:
>
> metacello (others)
> messageTally (st examples)
> stCodeBrowser (st examples)
> ...
>
> To do that, I think the #format: option is too limited:
>
> browser
> showOn: #methods; from: #classes;
> using: [
> browser list
> when: [ :class | class notNil];
> format: [:selector | selector, ' (', (NEED-THE-CLASS-HERE
> organization categoryOfElement: selector),')'];
> display: [ :class | class selectors asSortedCollection ].
>
> how do I get the class as a #format: block argument?
>
> --
> Damien Cassou
> http://damiencassou.seasidehosting.st
>
> "Lambdas are relegated to relative obscurity until Java makes them
> popular by not having them." James Iry
--
www.tudorgirba.com
"When people care, great things can happen."
Hello:
How do I report a bug?
I'm usgin moose-suite-4_0-alpha-3 and when I click on the lower pane in the
class browser I get:
OBTextSelection>>doesNotUnderstand: #isClassNode
Thanks!