Smalltalk › Frameworks & Tools › Moose

New features on MooseQuery

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Anne Etien

New features on MooseQuery

Hi,

Yesterday we developed two new features in MooseQuery:
- the toScope: method to go down in the containment tree. It is the opposite of atScope: that goes up. Both methods work the same way: ((classA queryIncoming: FAMIXInvocation) atScope: FAMIXClass) toScope: FAMIXMethod. This query uses the new API and returns the methods of the classes containing the methods sources of the incoming FAMIXInvocation of classA.
- the ability to query the MooseGroups. Thanks to this new feature, it is possible to query directly the model or any MooseGroup resulting from a selection or an operation (union, intersection, difference…) of several MooseGroups.

A full documentation’s coming, but certainly not before the end of the summer.

Cheers,
Jean-Christophe and Anne
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Tudor Girba-2

Re: New features on MooseQuery

Hi,

Sounds great. I am really interested in the group querying.

About naming, toScope: is a bit too similar to atScope: and I think the user will have a hard time understanding the difference. Last night I thought a bit about the names spawned by a remark of why the methods are called like atClassScope. Indeed, if we think about it, atClassScope is more of an implementation issue. The user wants to know what he gets. So, one possibility would be to call the same thing #classes or #justClasses or #onlyClasses or #collectClasses. Like this:

m queryAllOutgoingAssociations opposite classes

m queryAllOutgoingAssociations opposite justClasses

If we revamp the whole thing, we can also take the opportunity to rethink the API. What do you think?

Cheers,

Doru

On Fri, Jul 31, 2015 at 8:48 AM, Anne Etien <[hidden email]> wrote:

Hi,

Yesterday we developed two new features in MooseQuery:
- the toScope: method to go down in the containment tree. It is the opposite of atScope: that goes up. Both methods work the same way: ((classA queryIncoming: FAMIXInvocation) atScope: FAMIXClass) toScope: FAMIXMethod. This query uses the new API and returns the methods of the classes containing the methods sources of the incoming FAMIXInvocation of classA.
- the ability to query the MooseGroups. Thanks to this new feature, it is possible to query directly the model or any MooseGroup resulting from a selection or an operation (union, intersection, difference…) of several MooseGroups.

A full documentation’s coming, but certainly not before the end of the summer.

Cheers,
Jean-Christophe and Anne
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

www.tudorgirba.com

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Anne Etien

Re: New features on MooseQuery

Hi,

First of all, sorry, for answering so late, I was on holidays.

Glad to see that you are interested in the work.

I understand the naming problem and I fully agree. I can rename the already existing atTypeScope, atPackageScope… to types or packages. Nevertheless, the idea of the new API is to be generic so we get only atScope: and toScope: in order for example to do in the case of SQL atScope: FAMIXTable. So we need a name for atScope: and toScope:. Moreover, the idea is also to differentiate the up to down (toScope:) or bottom up (atScope:) direction.

Cheers,

Anne

Le 1 août 2015 à 23:09, Tudor Girba <[hidden email]> a écrit :

Hi,

Sounds great. I am really interested in the group querying.

About naming, toScope: is a bit too similar to atScope: and I think the user will have a hard time understanding the difference. Last night I thought a bit about the names spawned by a remark of why the methods are called like atClassScope. Indeed, if we think about it, atClassScope is more of an implementation issue. The user wants to know what he gets. So, one possibility would be to call the same thing #classes or #justClasses or #onlyClasses or #collectClasses. Like this:

m queryAllOutgoingAssociations opposite classes
m queryAllOutgoingAssociations opposite justClasses

If we revamp the whole thing, we can also take the opportunity to rethink the API. What do you think?

Cheers,
Doru

On Fri, Jul 31, 2015 at 8:48 AM, Anne Etien <[hidden email]> wrote:
Hi,

Yesterday we developed two new features in MooseQuery:
- the toScope: method to go down in the containment tree. It is the opposite of atScope: that goes up. Both methods work the same way: ((classA queryIncoming: FAMIXInvocation) atScope: FAMIXClass) toScope: FAMIXMethod. This query uses the new API and returns the methods of the classes containing the methods sources of the incoming FAMIXInvocation of classA.
- the ability to query the MooseGroups. Thanks to this new feature, it is possible to query directly the model or any MooseGroup resulting from a selection or an operation (union, intersection, difference…) of several MooseGroups.

A full documentation’s coming, but certainly not before the end of the summer.

Cheers,
Jean-Christophe and Anne
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev