- Moose-dev - INF Mailman

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

14 years, 5 months

1
0
0 0

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.

14 years, 5 months

1
8
0 0

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

14 years, 5 months

1
0
0 0

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

14 years, 5 months

1
0
0 0

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.

14 years, 5 months

1
6
0 0

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

14 years, 5 months

1
1
0 0

Re: Issue 260 in moose-technology: Reify sure invocations queries in Cook

by moose-technology＠googlecode.com

Updates: Labels: -Milestone-4.2 Milestone-4.3 Comment #3 on issue 260 by tudor.gi...(a)gmail.com: Reify sure invocations queries in Cook http://code.google.com/p/moose-technology/issues/detail?id=260 (No comment was entered for this change.)

14 years, 5 months

1
1
0 0

Re: Issue 440 in moose-technology: FamixInvocation>>to should return candidates instead of receiver

by moose-technology＠googlecode.com

Issue 440: FamixInvocation>>to should return candidates instead of receiver http://code.google.com/p/moose-technology/issues/detail?id=440 This issue is no longer blocking issue 438. See http://code.google.com/p/moose-technology/issues/detail?id=438 -- 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

14 years, 5 months

1
0
0 0

Re: Issue 438 in moose-technology: Cook issues noted in MooseChef

by moose-technology＠googlecode.com

Comment #4 on issue 438 by tudor.gi...(a)gmail.com: Cook issues noted in MooseChef http://code.google.com/p/moose-technology/issues/detail?id=438 Is this issue up to date?

14 years, 5 months

1
4
0 0

Issue 493 in moose-technology: ConfiguTation browser menu entry raises MNU

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 493 by jfa...(a)gmail.com: ConfiguTation browser menu entry raises MNU http://code.google.com/p/moose-technology/issues/detail?id=493 In the Hudson nightly build of 15 jan. MooseDevBrowser class>>menuCommandOn: aBuilder <worldMenu> (aBuilder item: #'MooseConfigutationBrowser') order: 6; parent: #Moose; label: 'Moose Configutation Browser'; action:[MooseDevBrowser open] Not only ConfiguTation -> ConfiguRation :-), but it also raises a MNU: reciever of "Project" is nil. Cause: "list selection" is nil in the following part of [MooseDevBrowser>>open] Smalltalk at: #OBCmdMetacello ifPresent: [ :x | projectList dynamicActions: [:list | (GLMOBCommandAdaptor new actionsFrom: (Smalltalk at: #OBCmdMetacello) subclasses on: list selection project configuration class for: nil ) do: [:each | each category: 'OB Commands'] ] ]

14 years, 5 months

1
2
0 0

behavior of flatten?

by Simon Denier

I'm a bit surpised... I want to flatten a collection with 'mixed' entries, like this one {{1. 2. 3}. 4} -> {1. 2. 3. 4} However it appears that #flatten does not work, because it expects that all elements in the collection are themselves collections. so {{1. 2. 3}. {4}} flatten -> {1. 2. 3. 4} works but {{1. 2. 3}. 4} flatten -> raises error because of a dnu on 4 Anyone knows the right method which would work for my case? -- Simon Denier

14 years, 5 months

2
2
0 0

Issue 518 in moose-technology: DynamicPresenatation needs to be rendered explicitly so that it can be updated

by moose-technology＠googlecode.com

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.3 New issue 518 by tudor.gi...(a)gmail.com: DynamicPresenatation needs to be rendered explicitly so that it can be updated http://code.google.com/p/moose-technology/issues/detail?id=518 We cannot update the rendering of a dynamic presentation because it delegates directly to the current presentation. It should have an explicit rendering that can take care of updating as well.

14 years, 5 months

1
1
0 0

Issue 517 in moose-technology: Glamour should support both text and icon in the label

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Glamour New issue 517 by tudor.gi...(a)gmail.com: Glamour should support both text and icon in the label http://code.google.com/p/moose-technology/issues/detail?id=517 Currently, if a presentation has titleIcon, the title is only shown as a balloon help. It should be possible to have both the icon and the title. So, we should have an extra explanation field in the presentation and display the title next to the icon.

14 years, 5 months

1
0
0 0

PetitParser, same character multiple times

by Alberto Bacchelli

Hi all, Is there an easy way to define the equivalent of the following regular expression in PetitParser? a{n,} which that the character 'a' must appear at least n times. Thank you! Cheers, Alberto

14 years, 5 months

6
9
0 0

Issue 515 in moose-technology: Add actions triggered by transmissions

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Glamour New issue 515 by tudor.gi...(a)gmail.com: Add actions triggered by transmissions http://code.google.com/p/moose-technology/issues/detail?id=515 It would be interesting to have actions that are triggered when a certain port is populated. Perhaps the simplest way would be to have a special ActionPort that is managed by the presentation and that results in executing the action associated with the port. Such a mechanism could be used to implement some smart behavior, such as automatic saving of content during editing, or it can be used to instrument transmissions for analysis purposes.

14 years, 5 months

1
0
0 0

Re: PetitParser, same character multiple times

by Alberto Bacchelli

PPRepeatingParser is indeed how the 'plus' method is implemented for example. The problem is that, by specifying #letter asParser I accept any kind of letter, thus #letter asParser plus accepts any number of any kind of letters. The problem is that I need to accept only multiple occurrences of the same letter :) I could do something like: $a asParser plus / $b asParser plus / ... but that's not really nice code :) Anyway, thanks for the help! On Feb 3, 2011, at 1:38 PM, Fabrizio Perin wrote: > Hi, > I did never use it but i found in PetitParser-Parsers this parser PPRepeatingParser that maybe can solve your problem. > > Cheers, > > Fabrizio > > On 3 Feb 2011, at 13:09, sback wrote: > >> >> To be more precise, >> I cannot use >> >> #letter plus >> >> because this would imply that I can both parse: >> >> 'aa', which is correct; but also: >> 'ab', which is not correct. >> >> I need a way to specify that I want the same letter, or character, to be >> repeated. >> >> Thank you, >> Alberto >> -- >> View this message in context: http://moose-dev.97923.n3.nabble.com/PetitParser-same-character-multiple-ti… >> Sent from the moose-dev mailing list archive at Nabble.com. >> _______________________________________________ >> 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

1
0
0 0

moose web license

by Tudor Girba

Hi, I noticed that the new MooseWeb repository is under BSD. Is that intentional? I am asking because all packages newly developed are under MIT. Cheers, Doru -- www.tudorgirba.com "Presenting is storytelling."

14 years, 5 months

1
0
0 0

what's the glamorous tookit?

by Esteban Lorenzano

Hi, Yeah, that... I wonder what's that :) Cheers, Esteban

14 years, 5 months

2
1
0 0

Re: Issue 175 in moose-technology: Rename in Famix-Extensions "referenced/referencing" to "invoked/invoking"

by moose-technology＠googlecode.com

Updates: Labels: -Milestone-4.2 Milestone-4.3 Comment #7 on issue 175 by tudor.gi...(a)gmail.com: Rename in Famix-Extensions "referenced/referencing" to "invoked/invoking" http://code.google.com/p/moose-technology/issues/detail?id=175 This should go away when MooseChef is integrated. I would close it for now.

14 years, 5 months

1
2
0 0

Re: Issue 57 in moose-technology: [FAMIX] code the LAN sample model in Java for reference and test

by moose-technology＠googlecode.com

Updates: Cc: anquetil.nicolas Comment #5 on issue 57 by jannik.l...(a)gmail.com: [FAMIX] code the LAN sample model in Java for reference and test http://code.google.com/p/moose-technology/issues/detail?id=57 (No comment was entered for this change.)

14 years, 5 months

3
4
0 0

[ANN] pharo focused sprint - bern, feb 26

by Tudor Girba

Hi, We would like to organize a Pharo Sprint on Saturday, February 26 at SCG, University of Berne, Switzerland (room 107): http://scg.unibe.ch/contact/maps Unlike other sprints, this would not be about fixing things from the tracker, but about building something new and reviewing the situation around one central topic. For this one, the main topic will be Morphic and the IDE. Why? Because it is time to rethink our day-to-day tools and bring them closer to this century (ok, maybe decade :)). It is Ok if you are not a specialist. It is more important to want to participate and learn. The rest will come in time. ***** Please let us know by mail if you plan to attend and what you would wish to work on (see below). Proposed tasks (other tasks are possible in the same area): - Enhancements of Morphic widgets: --- TabGroupMorph with lazy pages, closable tabs, overflow handling and toolbars (a start exists in Glamour) --- High level support for collapsable panes (based on the input of Gary) --- SearchMorph with multiple groups of items (like in Spotlight) --- MorphTreeMorph integrated with GeneralScrollPane to allow for space filling --- BreadcrumbMorph --- Hyperlinks in TextMorphs - Test and enhance the current IDE - Evaluate TextMorphs: NewTextMorph, PluggableTextMorph, SMxPluggableTextMorph etc - Prototype a new ToolSet solution - Enhancements of Glamour and of the Glamorous Toolkit --- Debugger --- Coder --- Multipage Workspace --- CodeBubbles - Develop WeakAnnouncement (start from the implementation of Lukas) - Evaluate the various keybinding implementations - Evaluate ToolBuilder - Evaluate the path to adopt SimpleMorphic A second working topic is getting Monticello faster, but this will only be tackled if there are enough people for the first one. Cheers, Adrian and Doru -- www.tudorgirba.com "Speaking louder won't make the point worthier."

14 years, 5 months

1
0
0 0

Issue 513 in moose-technology: The composite concerns should not offer the update action in Arki

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Arki New issue 513 by tudor.gi...(a)gmail.com: The composite concerns should not offer the update action in Arki http://code.google.com/p/moose-technology/issues/detail?id=513 Because of the update menu item, people add the concern in the specification and then expect that refreshing the composite to magically add the item.

14 years, 5 months

1
0
0 0

rpackage does not refresh on class rename

by Tudor Girba

Hi Cyrille, I noticed a case in which the RPackage did not seem to refresh after performing a class rename refactoring. I did not have a chance to write a test case for this, but I think it probably affects the importing as well. Cheers, Doru -- www.tudorgirba.com "No matter how many recipes we know, we still value a chef."

14 years, 5 months

2
1
0 0

Issue 512 in moose-technology: Implicit browsers should allow for extra transmissions

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Glamour New issue 512 by tudor.gi...(a)gmail.com: Implicit browsers should allow for extra transmissions http://code.google.com/p/moose-technology/issues/detail?id=512 Currently, there is no way to create custom transmissions in an implicit browser. For example, it might be needed to capture a specific port and export it to outside. Another application is in providing a custom output for the status bar.

14 years, 5 months

1
0
0 0

Re: Issue 315 in moose-technology: Moose Finder should be extensible by entities

by moose-technology＠googlecode.com

Updates: Labels: Milestone-4.3 Comment #2 on issue 315 by tudor.gi...(a)gmail.com: Moose Finder should be extensible by entities http://code.google.com/p/moose-technology/issues/detail?id=315 Currently, it is possible to extend the Moose Finder by defining extensions in the MooseFinder class. It's an Ok first solution but it will not really scale because we always have to test for the type. Instead, we should have a dynamic presentation computed by delegating to the objects.

14 years, 5 months

1
1
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev