I am creating a C# extractor for Moose. I am using Fame for java to access
Famix objects and populate their information (similar to VerveineJ). While
creating Famix.Class objects for C# classes, I need to set parent namespace
to represent the namespace that the class belongs to.
However, the Famix.Class only provides a single method to set the parent and
that take a Famix.Package as a parameter. So, the following expression is an
error for a Famix.Class object.
class.setParentPackage(Namespace)
Since, C# uses namespaces instead of Packages to organize classes, it would
be good to set a Famix.Namespace to be the parent of a class. Does
meta-model not provide a way that we can set Famix.Namespace as a parent of
a class. I can see another method in the Famix.Class and that is
SetContainer(ContainerEntity se). Can I use this method to set a Namespace
to be the parent of a Class and keeping the parentPackage relationship
empty?
thanks.
Usman
Hi all,
i did implement an SQL parser using Petit Parser. I toke the grammar specification from SQLite http://www.sqlite.org/lang.html . The grammar implemented is not complete, for now i did implement "just" the create table statement, it means that you should be able to parse at least a script for create the database.
The code is in squeaksource http://www.squeaksource.com/@09zbthA-fDDfyUNQ/_OIex3aA .
To download it you can evaluate this:
Gofer new
squeaksource: 'PetitSQLParser';
package: 'ConfigurationOfPetitSQLParser';
load.
(Smalltalk at: #ConfigurationOfPetitSQLParser) perform: #loadDefault
in the repository there are several packages: the core contains the parser for the grammar.
In the package parser there is a parser that instantiate some draft objects representing relational elements.
In the next future i will start to implement also other statements.
If you start to use it and you have some problem please let me know.
Cheers,
Fabrizio
Hi all,
I saw the tweet 'Preparing Moose suite 4.4'. Excellent news, I look forward to make a new version of AspectMaps to run on 4.4 :-)
I have one request though: as I dont have that much time to spend on AspectMaps, I cannot keep it 100% up to date with the fast pace that Moose is evolving. So for me, reproducibility of a given version is key. So I downloaded the 4.3 moose suite (one-click) release. This is for me the version in which AspectMaps loads, since it is an official *release*.
But this version *can* *not* be loaded using ConfigurationOfMoose. Hence AspectMaps cannot be loaded completely from source staring with a Pharo 1.2 image, which is a shame, really. (Of the different 4.3.x configurations a number of them break when loading, BTW.)
So my request: it would be cool if for 4.4 there is a version in ConfigurationOfMoose that produces an image identical to what is first released as the 4.4 one-click. For an official release I think this is a reasonable request and an effort worthwhile to consider. If later on, for 'intermediate versions' such configurations are made, this would be a nice extra but I understand that we all have limited time ;-)
--
Johan Fabry
jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry
PLEIAD Lab - Computer Science Department (DCC) - University of Chile
Hi,
Moose (http://moosetechnology.org) is a Smalltalk ambassador. Actually, I think it's the best ambassador we have right now to persuade professional developers to look into Smalltalk.
Let me tell you why.
Moose is a platform for software and data analysis and includes components like: Glamour, Mondrian or PetitParser. Moose solves a real and important problem that developers (both Smalltalkers and non-Smalltalkers) have: how to improve the productivity of the effort spent on assessment. Moose is an innovation in this domain because it enables a completely different approach through which developers craft their own tools fast (http://humane-assessment.com). The cool thing is that they build these tools by programming Smalltalk in Pharo, and thus they get to learn the language and the platform first.
Moose also comes with exposure. For example, this year I will be presenting Moose and humane assessment at some large industry oriented conferences:
- Jazoon (http://jazoon.com)
- GotoCon Aarhus (http://gotocon.com/aarhus-2011/)
- GotoCon Amsterdam (http://gotocon.com/amsterdam-2011/)
All in all, if you want to promote Smalltalk, and Pharo in particular, you might want to look into it. And you are always welcome to contribute, follow us and make noise:
- http://www.moosetechnology.org
- http://twitter.com/#!/moosetechnology
- http://www.facebook.com/pages/moosetechnologyorg/152851281427491
Cheers,
Doru
--
www.tudorgirba.com
"No matter how many recipes we know, we still value a chef."
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 612 by damien.c...(a)gmail.com: [Glamour] Tags do not play well
with trees
http://code.google.com/p/moose-technology/issues/detail?id=612
With the following browser:
1- Open the 'odd' root node
2- Click the 'odd' tag
3- Open the 'some' root node
4- You will see some nodes that don't have the 'odd' tag which may be a bug
5- Click the 'even' tag
6- You won't see anything anymore as they are no number which is
both 'even' and 'odd' ; there is no way to go back
treeWithTags
<glmBrowser: 'Tree withTags' input: '(1 to: 10)'>
"
self new treeWithTags openOn: #(1 2 3 4 5 6 7 8 9 10)
"
|browser model|
model := Dictionary new.
model at: #some put: #(1 2 3 4).
model at: #even put: #(2 6 8).
model at: #odd put: #(3 7 9).
browser := GLMTabulator new.
browser column: #one.
browser transmit to: #one; andShow: [ :a |
browser tree
display: [model keys];
children: [:key | key isNumber ifFalse: [model at: key] ];
tags: [:item | item isNumber ifTrue: [item even ifTrue: [#('even')]
ifFalse: [#('odd')]] ifFalse: [#()]]].
^ browser
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 626 by damien.c...(a)gmail.com: "Collection is empty when importing
AST packages"
http://code.google.com/p/moose-technology/issues/detail?id=626
To whom it may concern,
here are some steps to reproduce this "Collection is empty" error:
1- Download
http://ci.moosetechnology.org/job/moose-latest-dev/362/artifact/moose_suite…
2- Open it
3- Open the Moose Panel
4- Click the ST icon on the top right of the window
5- Select the AST-Core package
6- Press 'next>>'
7- Select the 'Compute type of attributes (using RoelTyper)
8- Press terminate
Stack trace attached
Attachments:
debug.log 33.8 KB
Status: New
Owner: ----
CC: georgega...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-ExternalTools
New issue 625 by tudor.gi...(a)gmail.com: inFusion should export implicit
variables
http://code.google.com/p/moose-technology/issues/detail?id=625
We need implicit variables to denote:
- self
- super
An example:
(FAMIX.ImplicitVariable (id: 39)
(name 'self')
(parentBehaviouralEntity (ref: 6)))
parentBehaviouralEntity should point to a FAMIX.Method
>
> Thanks Mariano for the pointer to Torch – it's new to me. I can see myself
> using
> it for some tasks in the future especially when dealing with big changes.
> Kudos
> also to the creator (Veronica?), the UI is quite pretty and functional.
>
> Incidentally, would it be possible to mention Torch in the Pharo Tools
> section
> of the Pharo CollaborActive Book
> <http://book.pharo-project.org/book/PharoTools>? That's usually
> where
> I (and I
> suspect other people) go to to find out about such useful tools.
>
>
Yes, this is a good idea. I can create her a user to edit the website if she
wants.
> Anyway, back to my question. I tried out Torch but I can't seem to find how
> to
> visualize the history of a repository - Torch visualizes changes. I
> didn't see anything about that on the Torch screenshot page either. Is it a
> hidden
> option somewhere?
>
I have no idea. Maybe the moose guys have something to share?
>
> Thanks!
>
> --
> Nick
>
> --
> View this message in context:
> http://forum.world.st/Monticello-How-to-visualize-history-tp3508002p3509668…
> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>
>
--
Mariano
http://marianopeck.wordpress.com
Status: New
Owner: ----
CC: georgega...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-ExternalTools
New issue 533 by tudor.gi...(a)gmail.com: inFusion should export the receiver
of invocation
http://code.google.com/p/moose-technology/issues/detail?id=533
The receiver should point to a named entity.
(FAMIX.Invocation
...
(receiver (ref:12))
)
Hi,
I think to have a bug with RPackage.
I used MooseScripts>>createModelForMoose.
This method works fine.
then I removed 3 methods useless for Moose (see issue 614)
When I rerun MooseScripts>>createModelForMoose, there is an error key not found.
The cache of RPackage is not updated.
Any solution ?
Jannik