- Moose-dev - INF Mailman

Re: Issue 423 in moose-technology: Presentation does not update title

by moose-technology＠googlecode.com

Updates: Labels: -Milestone-4.2 Milestone-4.3 Comment #3 on issue 423 by tudor.gi...(a)gmail.com: Presentation does not update title http://code.google.com/p/moose-technology/issues/detail?id=423 (No comment was entered for this change.)

14 years, 4 months

1
1
0 0

Issue 495 in moose-technology: Parametrized Types - Generics

by moose-technology＠googlecode.com

Status: New Owner: andreho...(a)gmail.com Labels: Type-Enhancement Priority-Medium Component-Famix New issue 495 by andreho...(a)gmail.com: Parametrized Types - Generics http://code.google.com/p/moose-technology/issues/detail?id=495 Use Parametrized Types (i.e., a parameterTypes property in FAMIXClass) in Moose to deal with (Java) code like this: ClassFoo<A,B,C>, where A, B and C are parameters of ClassFoo. VerveineJ must export this property in its .mse files.

14 years, 4 months

3
21
0 0

Hudson for Mondrian

by Alexandre Bergel

Hi! http://hudson.moosetechnology.org/job/mondrian-latest-dev-on-pharo-1.2/ uses PharoCore-1.2-12251. Could this be updated to a more recent version of PharoCore? It can be downloaded from https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%20Core%201.2/ Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years, 4 months

2
3
0 0

[OT] Map of scientific collaboration between researchers

by Alexandre Bergel

http://flowingdata.com/2011/01/27/map-of-scientific-collaboration-between-r… Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years, 4 months

1
0
0 0

releasing the configuration

by Tudor Girba

Hi Alex, I know that you worked on the tool support for versioning Metacello configurations. Could you describe it a bit? Does it support nested configurations as well? We would need this mechanism at least for the release. It would be great to get your help on this :) Cheers, Doru -- www.tudorgirba.com "Speaking louder won't make the point worthier."

14 years, 4 months

2
1
0 0

FAMIXMethod>>sureInvokedMethods in a inFusion model doesn't work

by Andre Hora

Hello, I tried to use the method FAMIXMethod>>sureInvokedMethods in a Java model generated by inFusion, but, for what I checked, it doesn't work. Is it a known bug? regards, -- Andre Hora

14 years, 4 months

2
2
0 0

do we need famix* in the name of the column of the moose models

by Stéphane Ducasse

Hi guys Why do we have famix* in in the name of the column of the moose models? Stef

14 years, 4 months

2
2
0 0

new java support in famix

by Tudor Girba

Hi, As you might have noticed, we have new additions to Famix-Java: - ParameterizableClass and ParameterizedType (to model generics and templates - thanks Andre :)) - Enum and EnumValue (to model Java Enums) - AnnotationTypeProperty and AnnotationInstanceProperty (to have detailed information about AnnotationType and AnnotationInstance) I am currently working with the inFusion guys to get the exporter working with these new additions. It would be great to have also VerveineJ up to date on this. There are still open issues, and it would also be great to get help on them: - How to model the parameters of a ParameterizableClass as a Type that can be used as declaredType. We should add some sort of a local scope to a type. See: http://code.google.com/p/moose-technology/issues/detail?id=495 - I would like to have an explicit FAMIXInterface, but it is slightly more difficult now that we have ParameterizableClass. See: http://code.google.com/p/moose-technology/issues/detail?id=526 Cheers, Doru -- www.tudorgirba.com "Be rather willing to give than demanding to get."

14 years, 4 months

4
10
0 0

Spy, Hapao, and MooseChef

by Simon Denier

Hi Alex I would be interested to see what we can learn from test coverage in MooseChef with Hapao. Another cool project would be to build a dependency analysis tool on top of Spy, which would take care of dynamic dependencies (especially invocations, perhaps also types). My guess is that it would be pretty easy to push MooseChef on top of that (write some primitive queries) and even perhaps build mixed tool for analysis of static vs dynamic dependencies. -- Simon Denier

14 years, 4 months

4
21
0 0

Basic visualization queries

by Usman Bhatti

Hi, While brainstorming the project Moose-on-the-Web (providing a moose interface on the web), we thought about putting a few basic/common visualization queries on the web. These queries will allow users to have an understanding of their system without trying different combinations of elements (packages, class, methods, etc.) and different combinations of visualizations (UML diagram, class blue-print, etc.). So, we thought to take a feedback from the people on this list regarding the common visualizations they find useful for a potential user of the system. Can you please provide a list of three visualizations that you think can be useful for a user for his/her system? thanx Usman Post-Doc at RMoD Team

14 years, 4 months

6
9
0 0

category importer broken

by Tudor Girba

Hi, It looks like the category importer is broken. Does anyone have time to take a look? Cheers, Doru -- www.tudorgirba.com "Value is always contextual."

14 years, 4 months

3
8
0 0

container of FAMIXImplicitVariable

by Andre Hora

Hello, I would like to know what is the container of a FAMIXImplicitVariable? In meta-model I see a FAMIXType as the container of a FAMIXImplicitVariable, but when I load a Smalltalk model I see a FAMIXMethod as container of a FAMIXImplicitVariable. -- Andre Hora

14 years, 4 months

2
2
0 0

Weird Behavior

by Langone Daniel

Hello you all, Just wanted to ask a question. When I¹m using Moose it displays, in the list of entities, twice the entry ³famixclasses (x)² (Have a look at the attached printscreen). Is this normal, or am I doing something wrong. Using version 4.1, tried it on mac and on windows pc, same behavior.... Just imported some arbitrary smalltalk project. Cheers, Daniel

14 years, 4 months

2
1
0 0

Importing from Monticello is not working

by Andre Hora

Hello, The Importing from Monticello is not working in the last version of moose-latest-dev: http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/… -- Andre Hora

14 years, 4 months

2
2
0 0

colors for syntax highlighting

by Tudor Girba

Hi, I am trying to find studies regarding the choice of colors for syntax highlighting. Does anyone know any publications in this area? Cheers, Doru -- www.tudorgirba.com "It's not what we do that matters most, it's how we do it."

14 years, 4 months

3
3
0 0

Issue 523 in moose-technology: Selection actions should disable the shortcut when no selection exists

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Glamour New issue 523 by tudor.gi...(a)gmail.com: Selection actions should disable the shortcut when no selection exists http://code.google.com/p/moose-technology/issues/detail?id=523 The morphic renderer does not disable the shortcut for an action when no selection exists.

14 years, 4 months

1
0
0 0

Mondrian: MOEdge - draggable

by Veronica Isabel Uquillas Gomez

Hi Alexandre, Some of my visualizations that are using #draggable are raising the error: MOEdge does not understand #translateBy:bounded: Did #draggable and #nodraggable change? Regards, Veronica

14 years, 4 months

2
1
0 0

Moose Chef

by Simon Denier

Moose Chef is now part of Famix Core. A page describing the library and its usage is available at http://www.moosetechnology.org/docs/famix/MooseChef (basically the same stuff that was described in my mails a few days ago) -- Simon Denier

14 years, 5 months

2
1
0 0

Issue 522 in moose-technology: Add Enum and EnumValue to FAMIX

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Famix Milestone-4.3 New issue 522 by tudor.gi...(a)gmail.com: Add Enum and EnumValue to FAMIX http://code.google.com/p/moose-technology/issues/detail?id=522 The following Java snippet should be modeled with an Enum and 7 EnumValues. The Enum should be a type and the EnumValue should have a parentEnum pointing to the Enum. public enum Day { SUNDAY, MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY }

14 years, 5 months

1
1
0 0

Re: Issue notifications in the mailing lists

by Alberto Bacchelli

Alexandre and Doru, I see your point, and I see many other open source projects mixing issue notifications with the real development mails, thus corroborating it. However, I would say that the best setup would be using two different mailing lists, because many of the issue notifications are not informative at all (e.g., "Issue #x fixed.") and you get a wrong idea of how much "real" discussion is going on the list. Other projects, such as ArgoUML adopt the multi lists approach. For example Argo has these lists: org.tigris.argouml.announce org.tigris.argouml.commits org.tigris.argouml.dev org.tigris.argouml.issues org.tigris.argouml.modules-dev org.tigris.argouml.users I've seen development mailing lists without discussions but with 2000 emails per month generated only by the issue tracking system. If this will be the case with moose-dev, (and many of the emails are really generated by the issue tracker) I would try to consider something different from mailing lists to coordinate. In any case, this is my opinion, and it's up to you to decide. Of course, I can always filter emails out ;) Thanks for reading. Cheers, Alberto On 7 February 2011 14:20, Alexandre Bergel <alexandre(a)bergel.eu> wrote: > I personally like the current setting. You can always filter out the mails you do not want to see > > Alexandre > > > > Le 7 févr. 2011 à 06:35, Alberto Bacchelli <alberto.bacchelli(a)usi.ch> a écrit : > >> Hi all, >> >> Why is the issue tracking system sending messages to this mailing list? >> >> Wouldn't it be better to have a second mailing list for issue notifications, >> so that moose-dev does not receive so many messages? >> >> We can always discuss here the issues that are worth-discussing, >> just by forwarding emails from the "issue notifications" mailing list to here. >> >> Just in my humble opinion. >> >> Alberto >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >

14 years, 5 months

2
1
0 0

Issue notifications in the mailing lists

by Alberto Bacchelli

Hi all, Why is the issue tracking system sending messages to this mailing list? Wouldn't it be better to have a second mailing list for issue notifications, so that moose-dev does not receive so many messages? We can always discuss here the issues that are worth-discussing, just by forwarding emails from the "issue notifications" mailing list to here. Just in my humble opinion. Alberto

14 years, 5 months

3
2
0 0

Issue 519 in moose-technology: Add AnnotationTypeProperty and AnnotationInstanceProperty

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Famix Milestone-4.3 New issue 519 by tudor.gi...(a)gmail.com: Add AnnotationTypeProperty and AnnotationInstanceProperty http://code.google.com/p/moose-technology/issues/detail?id=519 The AnnotationType should hold a collection of AnnotationTypeProperty. For example, below we would have 4 such properties attached to the MyAnno AnnotationType. public @interface MyAnno { int id(); String synopsis(); String engineer() default "[unassigned]"; String date() default "[unimplemented]"; } The AnnotationInstance should point to the AnnotationTypeProperty and hold a value. For example, below, the AnnotationInstance would have four AnnotationPropertyInstance, each pointing to the property type and having the value stored as string. @MyAnno(id = 0, synopsis = "")

14 years, 5 months

1
1
0 0

Re: Issue 390 in moose-technology: MoqamBrowser does not need to put module marks in a dictionary

by moose-technology＠googlecode.com

Updates: Status: WontFix Comment #1 on issue 390 by simon.de...(a)gmail.com: MoqamBrowser does not need to put module marks in a dictionary http://code.google.com/p/moose-technology/issues/detail?id=390 Nobody working on Moqam for now

14 years, 5 months

1
1
0 0

Issue 502 in moose-technology: Glamour rendering should offer closable tabs

by moose-technology＠googlecode.com

Status: Accepted Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Glamour Milestone-4.3 New issue 502 by tudor.gi...(a)gmail.com: Glamour rendering should offer closable tabs http://code.google.com/p/moose-technology/issues/detail?id=502 Currently, the rendering does not allow us to close tabs. This should be enabled for Accumulator.

14 years, 5 months

3
6
0 0

Re: Issue 345 in moose-technology: Close single tab / close all tab feature for Moose browser

by moose-technology＠googlecode.com

Updates: Status: Duplicate Mergedinto: 502 Comment #2 on issue 345 by simon.de...(a)gmail.com: Close single tab / close all tab feature for Moose browser http://code.google.com/p/moose-technology/issues/detail?id=345 (No comment was entered for this change.)

14 years, 5 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev