Moose-dev February 2011

moose-dev@list.inf.unibe.ch

23 participants
136 discussions

Re: Issue 260 in moose-technology: Reify sure invocations queries in Cook
by moose-technology＠googlecode.com 05 Feb '11

05 Feb '11

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

1 1

Re: Issue 440 in moose-technology: FamixInvocation>>to should return candidates instead of receiver
by moose-technology＠googlecode.com 05 Feb '11

05 Feb '11

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

1 0

Re: Issue 438 in moose-technology: Cook issues noted in MooseChef
by moose-technology＠googlecode.com 05 Feb '11

05 Feb '11

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?

1 4

Issue 493 in moose-technology: ConfiguTation browser menu entry raises MNU
by moose-technology＠googlecode.com 05 Feb '11

05 Feb '11

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

1 2

behavior of flatten?
by Simon Denier 04 Feb '11

04 Feb '11

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

2 2

Issue 518 in moose-technology: DynamicPresenatation needs to be rendered explicitly so that it can be updated
by moose-technology＠googlecode.com 04 Feb '11

04 Feb '11

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.

1 1

Issue 517 in moose-technology: Glamour should support both text and icon in the label
by moose-technology＠googlecode.com 04 Feb '11

04 Feb '11

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.

1 0

PetitParser, same character multiple times
by Alberto Bacchelli 03 Feb '11

03 Feb '11

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

6 9

Issue 515 in moose-technology: Add actions triggered by transmissions
by moose-technology＠googlecode.com 03 Feb '11

03 Feb '11

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.

1 0

Re: PetitParser, same character multiple times
by Alberto Bacchelli 03 Feb '11

03 Feb '11

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

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev February 2011