January 2011 - Moose-dev

Issue 490 in moose-technology: check generic-types handling

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 490 by andrehoraa: check generic-types handling http://code.google.com/p/moose-technology/issues/detail?id=490 It seems verveineJ does not handle generic types at all. For example if a method has a return type with generic, the return type is not processed correctly, and the method might not be created correctly. Check whether this is the case and solve the problem if it is the case ...

12 years, 10 months

1
3
0 / 0

Issue 485 in moose-technology: Add MOImageShape

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Mondrian New issue 485 by alexandre.bergel: Add MOImageShape http://code.google.com/p/moose-technology/issues/detail?id=485 Having a picture as a shape.

12 years, 10 months

1
2
0 / 0

Issue 497 in moose-technology: LocalVariables without ParentBehaviouralEntity

by moose-technology＠googlecode.com

Status: New Owner: andreho...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Verveine New issue 497 by andreho...(a)gmail.com: LocalVariables without ParentBehaviouralEntity http://code.google.com/p/moose-technology/issues/detail?id=497 It seems that some Local Variables don't have ParentBehaviouralEntity. It might be related to binding problem in the AST.

12 years, 10 months

1
2
0 / 0

Re: Issue 445 in moose-technology: [Glamour] wrong behavior when embedding a browser

by moose-technology＠googlecode.com

Updates: Labels: Component-Glamour Comment #1 on issue 445 by tudor.gi...(a)gmail.com: [Glamour] wrong behavior when embedding a browser http://code.google.com/p/moose-technology/issues/detail?id=445 (No comment was entered for this change.)

12 years, 10 months

1
0
0 / 0

Re: Issue 467 in moose-technology: Testing Case Package Polymorph?

by moose-technology＠googlecode.com

Updates: Status: Invalid Comment #2 on issue 467 by tudor.gi...(a)gmail.com: Testing Case Package Polymorph? http://code.google.com/p/moose-technology/issues/detail?id=467 This is not a Moose issue

12 years, 10 months

1
0
0 / 0

happy new ... focus

by Tudor Girba

First of all, a long overdue: Happy New Year! :) I would like to start the new year with a call to focus and collaboration. The idea is simple: I would like us to work together more explicitly around defined projects. So, let me start. Here are some projects I would propose: - Enhanced Glamour rendering - I need help here, especially in the Morphic rendering part - Editor for Fame meta-models - FameDB - database persistency for fame meta-described objects (Alberto is already interested in this) - Editor for Mondrian graphs - Strong JNIPort connection to Eclipse and VerveineJ - Cyrille already has a project in this area - More Petit parsers - Fabrizio started one for SQL and JSP, and Alberto started one for Java - Tight integration of Moose analyses in the PharoIDE - I already started the Glamorous Toolkit project and I would like to continue - PetitParser-based text editor to support fine-grained control over different tokens - Meta-annotations (Metanool) - Charting engine (EyeSee) - Mondrian interaction based on Glamour What are your projects? Let's share them and identify collaborations. Cheers, Doru -- www.tudorgirba.com "No matter how many recipes we know, we still value a chef."

12 years, 10 months

5
14
0 / 0

Re: moosejee hudson build

by Tudor Girba

Hi Fabrizio, Ahh, indeed. The problem is that XMLSupport comes with PharoDev, and we stopped loading a new version because it breaks the loading. We still have to find a solution for this. Cheers, Doru On 18 Jan 2011, at 11:59, Fabrizio Perin wrote: > Hi Doru, > i see htanks a lot it is actually very very cool :) > > i will try to go through them this evening the main problem seems to be OPAX. Anyway in the last Moose you are loading a very old version of XMLSupport aren't you? Should not we wait for a fix? Or More, shouldn't we move to petitXMLParser? Is a way more effort i'm sure but we need something stable or a release of XMLSupport that we can use (possibly not from jan 2010). > > Cheers, > > Fabrizio > > > 2011/1/18 Tudor Girba <tudor.girba(a)gmail.com> > Hi Fabrizio, > > There are still 11 tests failing :) > > Cheers, > Doru > > > On 15 Jan 2011, at 16:08, Tudor Girba wrote: > > > Hi Fabrizio, > > > > I created a hudson build specific for MooseJEE. There are only 11 failing tests :) > > > > Cheers, > > Doru > > > > > > -- > > www.tudorgirba.com > > > > "Presenting is storytelling." > > > > -- > www.tudorgirba.com > > "From an abstract enough point of view, any two things are similar." > > > > -- www.tudorgirba.com "What we can governs what we wish."

12 years, 10 months

2
1
0 / 0

Re: Issue 279 in moose-technology: Highlight in the Listing Presentation

by moose-technology＠googlecode.com

Issue 279: Highlight in the Listing Presentation http://code.google.com/p/moose-technology/issues/detail?id=279 This issue is no longer blocking issue 233. See http://code.google.com/p/moose-technology/issues/detail?id=233 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

12 years, 10 months

1
0
0 / 0

Re: Issue 233 in moose-technology: Make browseMeta package-aware

by moose-technology＠googlecode.com

Updates: Status: Fixed Labels: Milestone-4.3 Blockedon: -279 Comment #6 on issue 233 by tudor.gi...(a)gmail.com: Make browseMeta package-aware http://code.google.com/p/moose-technology/issues/detail?id=233 I do not know what to do here, so I will just close the issue now.

12 years, 10 months

1
0
0 / 0

bug when opening system complexity : MOTreeLayout(Object)>>doesNotUnderstand: #topGap:

by Cyrille Delaunay

In the latest moose dev image: http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuil... If you create a model and try to visualize system complexity from all classes, an error will be thrown: MOTreeLayout(Object)>>doesNotUnderstand: #topGap: I guess it is due to some modifications in mondrian and that the code of system complexity has not been updated. I opened and issue: http://code.google.com/p/moose-technology/issues/detail?id=496

12 years, 10 months

2
1
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev January 2011