I would like to try to set up a collab.net for tracking moose.
Do we give a try?
Stef
Begin forwarded message:
> From: Robert Krahn <robert.krahn(a)student.hpi.uni-potsdam.de>
> Date: June 23, 2008 9:36:37 PM CEDT
> To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org
> >
> Subject: Re: [squeak-dev] JSqueak, the erstwhile Potato, is out!
> Reply-To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org
> >
>
> Hi!
>
>> There is always google code, which is reasonably fast (inluding the
>> wiki)..
>
>
> ... or even better: open.collab.net. We used the Collabnet services
> intensively during our last project and they provide really good
> tooling for hosting and managing a project like JSqueak.
>
> Besides a reliable SVN repository open.collab.net provides tools for
> user stories, a bug tracking system, mailing lists, RSS'able
> announcements and more.
>
> Robert
>
>
Hi doru
allClasses
<navigation: 'All classes'>
^self allWithType: FAMIXClass asMetaDescription
I do not know how I can define asMetaDescription because I do not want
to import Meta in Squeak :(
So I still cannot run the tests of the importer.
So I will define my own methods to be able to query the model.
Do you know if FMSlot are available again because the only tests that
worked before just broke :(
Stef
Hi,
It's fine. MooseCore depends on nothing now.
Romain
-----Message d'origine-----
De : Stéphane Ducasse [mailto:stephane.ducasse@univ-savoie.fr]
Envoyé : dimanche 22 juin 2008 22:18
À : peirsro(a)ensieta.fr; Related to the development of Moose and other
related tools
Objet : Re: [Moose-dev] MooseCore depends on other packages
Hi romain
can you check because I fixed the problems you kindly reported :)
Stef
On Jun 19, 2008, at 11:57 AM, Romain PEIRS wrote:
> Hi,
>
> I would know why the package MooseCore depends on other packages :
> MooseUI
> and MooseFAMIXModel?
> Indeed, the methods defaultViewer in the classes Object and
> MooseElement
> make an access on the class MooseBrowserEntityUI which is defined in
> the
> package MooseUI.
> Moreover, the methods importClasses, importMethods and
> importNamespaces in
> the class MooseImporter make an access on the classes FAMIXClass,
> FAMIXMethod and FAMIXNamespace, respectively.
> Should we move these methods on an other place?
>
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi,
I would know why the package MooseCore depends on other packages : MooseUI
and MooseFAMIXModel?
Indeed, the methods defaultViewer in the classes Object and MooseElement
make an access on the class MooseBrowserEntityUI which is defined in the
package MooseUI.
Moreover, the methods importClasses, importMethods and importNamespaces in
the class MooseImporter make an access on the classes FAMIXClass,
FAMIXMethod and FAMIXNamespace, respectively.
Should we move these methods on an other place?
Hi doru
I'm working on the importer again and I found that groupedBy: was not
imported as extension of MooseCore.
So may be I will have to check all the extensions.
Now is it me that does not find tests for groupedBy: or it is correct?
Stef
Hi,
Today, Toon and me worked on Fame and FAMIX in Squeak. We regenerated
FAMIX and the results are:
- Added addTo* like methods (for example, FAMIXClass>>addToMethods:
aMethod). The reason why it's not just addMethod: is due to us being
unable tofind a simple and robust algorithm for producing English
singular. Also, just taking the type into account is not enough
because of cases like incomingInvocations and outgoingInvocations.
- Changed the names of parameters to reflect whether they are
collections or not.
- Made the Smalltalk superclass to be MooseEntity.
We also worked on creating the meta-repository for FAMIX and we also
have MSE files with FAMIX models loading. There still some work to be
done to populate the MooseModel.
I also fixed the loading error related to FMBookMock and fixed some .
I will continue with working on the Moose Finder over the next days.
Doru
--
www.tudorgirba.comwww.tudorgirba.com/blog
"Value is always contextual."
Hi doru
I tried to find where NOM was defined. I looked in the class
FamixClass and found methods but I could not see the
pragma.
can you help there?
Stef
Hi all
I would like to know all the methods in Moose that define a metric.
So I tried to look for the senders of
#numericalProperty:longName:description:
but there are none.
How do we get all the pragma definers in VW?
Stef
