Hello!
I'm in trouble (attached) to run the script below:
Gofer new
squeaksource: 'FameImportExportEx';
package: 'Fame-ImportExport-Extensions';
load.
I’m using Windows-OS and Moose Suite 4.5. I need help to export metrics to .CSV.
Where should I run the script? I’m running the workspace Moose Suite
4.5, correct?
Thank you.
--
PROF. PALOMA MAIRA DE OLIVEIRA
__________________________________________________________
IFMG - Campus Formiga
Doutoranda em Ciência da Computação - DCC/UFMG
Mestra em Modelagem Matemática e Computacional - CEFET/MG
Bacharel em Ciência da Computação - UNIFOR/MG
Hi,
I'm wondering if there is a way to obtain all the model classes from a
HismoModel
I know that the statement "*hismoModel allClassHistories*" return all the
FAMIX classes histories but I can't find the method to get only the model
classes histories.
Cheers
--
Santiago Vidal
Hi!
In Merlin, the class MerlinMultiSelectionItemsSelectorWidget has the method:
newMultiSelectionListFor: aModel list: listSelector primarySelection: primarySelectionSelector changePrimarySelection: changePrimarySelectionSelector listSelection: listSelectionSelector changeListSelection: changeListSelectionSelector
which reference PluggableListMorphOfMany. This class does not exist in Pharo 1.4 and is marked as deprecated in Pharo 1.3.
It would be cool to fix this. I am currently porting Spy to Pharo 1.4, but I am kind of stuck.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
There is not enough communication and coordination around Moose these days. Perhaps it is just the holidays, but I feel a bit lonely working on Moose.
I would be interested in knowing who is working on what these days. Or at least, who would like to work on what.
Cheers,
Doru
--
www.tudorgirba.com
"In a world where everything is moving ever faster,
one might have better chances to win by moving slower."
Hi!
I was pretty tired of not being able to load Glamour in different images, so
I've created a new stable #version for pharo 1.3 and, by now, saved that
configuration in the dbxtalk repo squeaksource.com/dbxtalk.
Maybe someone want to integrate it in the glamour repo :).
Cheers,
Guille
I created the configuration with last Ben improvement.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
I just remember that when I merged MooseElement and MooseEntity, I did not take into account the comments of the class.
If someone want to copy and paste them :)
Else I will do it tomorrow.
Cheers,
---
Jannik Laval
We get
------
FAMIXSourceLanguage
This represents the programming language in which an entity is written. It is used for dispatching entity actions for specific languages. For example, formatting a source text will be performed according to the language.
We can get
---------
I represent the programming language in which an entity is written. I'm used for dispatching entity actions for specific languages. For example, formatting a source text will be performed according to the language.
API:
format: aSourceString from: anEntity
isAttached
@@no idea what it is.@@
sourcedEntities
References to the entities saying explicitly that are written in this language
@@But it does not help me at all@@
Now I do not get why we have sourceEntities added to the source language.
Hi
I was looking for the package (FM3 one) for FAMIX or Core and Java and I could not find them.
Do you know if they got created?
I have the impression that this is another sign that pharo need manifestoClass per packages so that we
can annotate them and Moose would use them to declare them.
Now imagine that we get that (we can just start adding a FAMIXJavaManifest class in the package FAMIX-Java)
how do we annotate that this is a FM3Package because
<package: > is used to annotate properties
And I have the impression that having the distinction between definition and specialisation of annotation is better.
We have
FMPackage:
FMClass: superclass:
but we could have
FMClassDefinition: superclass
FMPackageDefinition:
FMPackaged:
Stef
Em 27 de setembro de 2011 13:42, Jùlio <jleandro.martins(a)gmail.com>escreveu:
> Ah! I understood what was happening. I really needed select all code to
> execute, but I didn't know is needed to open the Trascript browser to
> exhibit the result. Other thing was I had not selected completely code.
> Sometimes some part of the code don't was selected properly.
>
> :-)
>
> Em 26 de setembro de 2011 16:30, Alexandre Bergel-7 [via Smalltalk] <
> ml-node+s1294792n3845025h64(a)n4.nabble.com> escreveu:
>
> Of course, you should have the transcript open (cmd-t)
>>
>> Alexandre
>>
>>
>> On 26 Sep 2011, at 15:34, Stéphane Ducasse wrote:
>>
>> > just copy and paste it in workspace
>> > select everything and do it.
>> > And it should work
>> > Moose has nothing special to do with a possible bug.
>> >
>> > It works also when putting spaces
>> >
>> > |i|
>> > i := 5.
>> > [ i >0 ] whileTrue:[
>> > Transcript show: ((i*2) asString) ; cr.
>> > i := i - 1.
>> > ].
>>
>
>
--
View this message in context: http://forum.world.st/Re-Sytax-or-what-tp3848136p3848136.html
Sent from the Moose mailing list archive at Nabble.com.
Well, so I will go change the form of my code
|i|
i:=5.
[i >0] whileTrue:[
Transcript show: ((i*2) asString) ; cr.
i:=i-1.
].
Why this doesn't work too? I only receive a "Nothing more expected" when I
try to execute it.
Em 24 de setembro de 2011 02:58, Stéphane Ducasse [via Smalltalk] <
ml-node+s1294792n3838776h45(a)n4.nabble.com> escreveu:
> There is a bug in Beeper and the default sound primitive
>
> stef
>
> On Sep 24, 2011, at 2:49 AM, Júlio Martins wrote:
>
> > I don't know why this simple code don't work in Moose/Smaltalk version
> 4.5
> >
> > | counter |
> > counter := 0.
> > [ counter < 100 ] whileTrue:
> > [ counter := counter + 1.
> > Beeper beep ]
> >
> > I believe the sytax is correct, but when I try to excute this an error
> message is sent.
> > Doesn't exist while loop?
> >
> > I don't undesrtand what's happening.
> >
> > View this message in context: Sytax or what?
> > Sent from the Moose mailing list archive at Nabble.com.
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email] <http://user/SendEmail.jtp?type=node&node=3838776&i=0>
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email] <http://user/SendEmail.jtp?type=node&node=3838776&i=1>
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://forum.world.st/Sytax-or-what-tp3838424p3838776.html
> To start a new topic under Moose, email
> ml-node+s1294792n1310756h25(a)n4.nabble.com
> To unsubscribe from Moose, click here<http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&no…>.
>
>
--
View this message in context: http://forum.world.st/Re-Sytax-or-what-tp3843592p3843592.html
Sent from the Moose mailing list archive at Nabble.com.
We have
-------
FAMIXCustomSourceLanguage has not been documented yet. The class comment should describe the purpose of the class, its collaborations and its variables.
Instance Variables:
name <ProtoObject | PseudoContext>
We can get
---------
@@I represent specific source language that is not a language supported by default by moose?@@
Then the comment of name is unclear to me?
what is a language that is not explicitly modeled?
name
<MSEProperty: #name type: #String>
<MSEComment: 'The name of a custom language that is not modeled explicitly.'>
We have
-------
I'm an abstract class, root of the hierarchy modeling source code entities.
Any of my subclasses must define the meaning of the belongsTo, an abstract property that provides polymorphic traversal. For example, FAMIXClass defines belongsTo as being the container, while the FAMIXMethod defines belongsTo to point to the parentType.
I propose
--------
I'm an abstract class, root of the hierarchy modeling source code entities.
Any of my subclasses must define the meaning of the belongsTo property, an abstract property that provides polymorphic traversal. For example, FAMIXClass defines belongsTo as being the container, while the FAMIXMethod defines belongsTo to point to the parentType.
I support the tagging of entity as stub. Marking an entity as a stub means that the
Stubs should only be marked by importers and extractors. Stubbed entities represent the border of the modeled world as extracted. Stub tagging should not be recursive. Use other tags for such a purpose: a class may have an instance variable tagged as a stub because an importer got a memory leak or a bug. Still the class is not a stub, but extra analysis can mark it as incomplete.
When applicable, I also point to my containing package accessible via parentPackage and modifiers.
I also can return the list of invocations performed on this entity (considered as the receiver) (receivingInvocations).
Finally, I provide simple name for the entity I represent. The pattern is that name returns the local name of the entity.
Hi all,
I'm a developer that needs to produce (starting from a java project) and
import moose data analysis into a own program (written into java or c++).
Exists a api moose library (a .dll or somethings of equivalent) that can be
linked to my program or can the moose data analysis exported into a xml or
equivalent file format ? Can the moose be launched as a command with an
stdout without use a user interface or gui ?
Thanks,
Michele
--
View this message in context: http://moose-dev.97923.n3.nabble.com/moose-data-analysis-exporter-xml-or-ot…
Sent from the moose-dev mailing list archive at Nabble.com.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 713 by alexandr...(a)gmail.com: Smart analyzer for the MSE reader
http://code.google.com/p/moose-technology/issues/detail?id=713
it would be nice to have some information in MSE, but until now at least,
we did not find an easy solution.
One thing we can do easily though is to build a smart analyzer that does
not build the meta-model, only traverses the header of entities to recover
the types. Anyone would like to take a shot at this? We should create an
issue.
I suggest that we add to FM3 something like that
packagePragma
^ Pragma inMethod:
(self mmClass implementingClass >>self implementingSelector)
named: #package:
package
^ look for FM3Package...
if we agree I will write some tests soon.
Stef
Hi,
When I load MSE files, I would like to know which kind of information is inside the file. I think we should think about a solution.
Here is the problem:
- I can generate a mse file with a generic FAMIX model.
- I can generate a mse file with a model containing FAMIXEclipsePlugin entities
- I can also generate a mse file with mensana informations
When I use a new image, few weeks after, I do not remember the plugins I used. And it is not possible to load the file. The problem is when the time of loading is more than 10 minutes and crash after 9 minutes, I am frustrated :)
I propose a solution and I would like to discuss about this problem.
I think that we could have a meta information that lists all type of entities in the mse file (for example: (FAMIXClass, FAMIXMethod, FAMIXPackage...)). This information would be checked before the importation and inform the developer if some classes are not present in the system.
After that, we can imagine that the developer has the choice between installing the classes or loading a partial model.
What are your opinions ?
---
Jannik Laval
Hi,
Moose On Moose is a report about Moose based on Arki.
At the moment we have only a few issues already in the report:
http://ci.moosetechnology.org/job/moose-on-moose/
Just a note: this is not a set of generic detections, but a dedicated set of checks super specific to Moose. These kind of checks are at the essence of humane assessment and I would like to see them grow and used for our development.
If you want to contribute, the smallest thing you can do is to raise an issue, and then we build it into a rule. To get an idea of the process to get it in the report, you can see my latest blog post:
http://www.humane-assessment.com/blog/detecting-wrong-values-in-annotations
Cheers,
Doru
--
www.tudorgirba.com
"Quality cannot be an afterthought."
Hi guys
Is there a reason why we get
#Attribute and not FAMIXAttribute
and/or
super: #FAMIXStructuredEntity
instead of
super: 'FAMIX.StructuredEntity'
So I would prefer to have something regular
either
#'FAMIX.Attribute' super: #'FAMIX.StructuredEntity'
or
#Attribute super: #StructuredEntity
In fact I would prefer
#'FAMIXAttribute' super: #'FAMIXStructuredEntity'
Stef
Doru
I would like to compile a set of actions/decisions for FAME.
So can you compile one based on the discussions we got else this will stay the same.
Once we agree I will implement the changes.
Stef
I imagine that I cannot ask an FAME attribute the methods that defined it.
Am I correct?
So this means that if I want to know that an attribute got tagged with a package pragma: I have to query that at the smalltalk level.
But this means that I also have to check that this is the correct attributes I got
<MSEProperty: #annotationInstances type: #FAMIXAnnotationInstance opposite: #annotatedEntity> <multivalued> <derived>
<package: #Java>
Stef