Moose-dev February 2011

moose-dev@list.inf.unibe.ch

23 participants
136 discussions

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 = "")

13 years, 10 months

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

13 years, 10 months

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.

13 years, 10 months

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.)

13 years, 10 months

Re: Issue 405 in moose-technology: Transpose columns and rows in the Practice Grid

by moose-technology＠googlecode.com

Updates: Status: WontFix Comment #1 on issue 405 by simon.de...(a)gmail.com: Transpose columns and rows in the Practice Grid http://code.google.com/p/moose-technology/issues/detail?id=405 Nobody working on Moqam for now

13 years, 10 months

Issue 520 in moose-technology: Integrate MooseChef

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: tudor.gi...(a)gmail.com, simon.de...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Famix Milestone-4.3 New issue 520 by tudor.gi...(a)gmail.com: Integrate MooseChef http://code.google.com/p/moose-technology/issues/detail?id=520 MooseChef should get integrated into Famix. Due to the traits, the only reasonable solution is to change directly the Famix definitions for now in a dedicated query method category. When Pharo will provide a better solution to extend a class with a trait, we can revisit the implementation and decouple it into a separate package.

13 years, 10 months

16 issues changed in moose-technology

by moose-technology＠googlecode.com

Updates: Labels: Milestone-4.3 Comment by tudor.gi...(a)gmail.com: (No comment was entered for this change.) Affected issues: issue 310: Make Glamour loadable without Mondrian and Magritte http://code.google.com/p/moose-technology/issues/detail?id=310 issue 394: Decouple MOGraphStructure from MOGraphAlgorithm http://code.google.com/p/moose-technology/issues/detail?id=394 issue 395: MooseAlgos classes should not have MO prefix http://code.google.com/p/moose-technology/issues/detail?id=395 issue 458: Query class in package blueprints http://code.google.com/p/moose-technology/issues/detail?id=458 issue 459: Package blueprints should show empty blueprints http://code.google.com/p/moose-technology/issues/detail?id=459 issue 461: Prefix all classes in Moose-Algos with Mal http://code.google.com/p/moose-technology/issues/detail?id=461 issue 462: the mooseModel is never set to a DudeSourceCodeFragment http://code.google.com/p/moose-technology/issues/detail?id=462 issue 466: PPMSEArrayParser does not take escaping $' characters into account http://code.google.com/p/moose-technology/issues/detail?id=466 issue 470: Automoose Script can't open image file when using Cog http://code.google.com/p/moose-technology/issues/detail?id=470 issue 471: Configuration of Glamour should load Shout http://code.google.com/p/moose-technology/issues/detail?id=471 issue 472: Moose Finder should react to announcements http://code.google.com/p/moose-technology/issues/detail?id=472 issue 473: Explicit port references in Glamour http://code.google.com/p/moose-technology/issues/detail?id=473 issue 481: add a helpMessage to the search-input-text of the MooseFinder http://code.google.com/p/moose-technology/issues/detail?id=481 issue 483: Have a wizard to import form VerveineJ http://code.google.com/p/moose-technology/issues/detail?id=483 issue 484: PetitParser debugger does not show nesting anymore http://code.google.com/p/moose-technology/issues/detail?id=484 issue 486: Presentation-wide actions should be displayed in a toolbar http://code.google.com/p/moose-technology/issues/detail?id=486 -- You received this message because you are listed in the owner or CC fields of these issues, or because you starred them. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

13 years, 10 months

Fwd: [squeak-dev] [ANN] JNIPort 2.0 for VisualWorks, Pharo and Squeak

by stephane ducasse

Cool news :) Stef Begin forwarded message: > From: Joachim Geidel <joachim.geidel(a)onlinehome.de> > Date: February 5, 2011 4:14:27 PM GMT+01:00 > To: VW NC <vwnc(a)cs.uiuc.edu>, "Pharo-project(a)lists.gforge.inria.fr" <Pharo-project(a)lists.gforge.inria.fr>, A friendly place where any question about pharo is welcome <pharo-users(a)lists.gforge.inria.fr>, The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org>, VWDEV list <vw-dev(a)parcplace.net> > Subject: [squeak-dev] [ANN] JNIPort 2.0 for VisualWorks, Pharo and Squeak > Reply-To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> > > JNIPort 2.0 for VisualWorks, Pharo and Squeak is now available! > > JNIPort is a Smalltalk library which allows Java code to be invoked from > Smalltalk. It acts as a bridge between the world of Smalltalk objects and a > Java Virtual Machine (JVM) where Java code is executing. For more > information see > > http://jniport.wikispaces.com > > JNIPort 2.0 for VisualWorks can be loaded from the Cincom Public Store > Repository and from the JNIPort wiki at > > http://jniport.wikispaces.com/Downloads > > JNIPort 2.0 for Pharo and Squeak is available from SqueakSource at > > http://www.squeaksource.com/JNIPort.html > > and from the JNIPort wiki. > > The changes from JNIPort 1.9 are: > > - JNIPort can now be used in Pharo and Squeak. > > - Packages have been renamed such that the can be shared between Store > and Monticello. > > - Platform specific code has been moved to separate packages to make the > core packages portable between VisualWorks, Pharo, and Squeak. > > - The much-critized _null postfix used for selectors of wrapper methods > which don't have arguments is gone. > > - A few bugs have been fixed. > > Installation instructions for VisualWorks are on the JNIPort wiki, > instructions for Pharo and Squeak are on the wiki of the JNIPort project > page of SqueakSource. I strongly encourage you to read the instructions > before installing and using JNIPort. > > JNIPort 2.0 has been tested with: > > - VisualWorks from 7.5 to 7.8 (trent dec10.3) on Mac OS X 10.6.6 and > Windows XP SP 3 > > - VisualWorks from 7.7 to 7.8 (trent dec10.3) on Ubuntu 10.04 (64bit) > with both the 32-bit and the 64-bit VisualWorks VMs > > - Squeak 4.2 on Mac OS X 10.6.6 and Windows XP SP 3 > > - Pharo 1.1.1 and 1.2 on Mac OS X 10.6.6 and Windows XP SP 3 > > Known issues: > > - In Pharo 1.1.1, you may encounter an error when JNIPort tries to register > a new Java object in an internal weak dictionary. This is a bug in Pharo's > implementation of this collection class. I can't do anything about it. If > you can't live with it, please upgrade to Pharo 1.2. > > - JNIPort for Pharo and Squeak currently cannot be used with the Cog VM. > > - Callbacks from foreign operating system threads cannot be used in Pharo > and Squeak. The Alien foreign function interface does not yet support > this feature. When you run the unit tests, three tests will fail because > of this restriction. These failures are expected and do not indicate bugs. > > Best regards, > Joachim Geidel > > >

13 years, 10 months

Re: Issue 16 in moose-technology: implicit importer is wrong: an implicit variable should be attached to a method not a class

by moose-technology＠googlecode.com

Comment #9 on issue 16 by cy.delaunay: implicit importer is wrong: an implicit variable should be attached to a method not a class http://code.google.com/p/moose-technology/issues/detail?id=16 after looking a bit more, I think we will have to change also the code about Invocations, which expect the parent of an ImplicitVariable to be a Class.

13 years, 10 months

Issue 521 in moose-technology: Meta Browser needs search capabilities

by moose-technology＠googlecode.com

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Enhancement Priority-Medium Component-Finder Milestone-4.3 New issue 521 by tudor.gi...(a)gmail.com: Meta Browser needs search capabilities http://code.google.com/p/moose-technology/issues/detail?id=521 It would be nice if we could search for an entity in the Meta Browser

13 years, 10 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev February 2011