Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Start a nNew thread

Re: Activity Diagram
by Stephan Eggermont 24 Dec '13

24 Dec '13

Did you take a look at the BabyMock (2) work by Attila Magyar (@zeroflag)? Stephan

2 1

MooseDay: mini report
by Alexandre Bergel 22 Dec '13

22 Dec '13

Hi! Yesterday we had the moose day. We were about 30 people, coming from Switzerland, Chile, Belgium and France. We had many presentations covering meta-modeling (Orion, FamixDiff), Evolution (ApiEvolutionMiner, VersionSigns of Caries), Visualization (Roassal & GraphET), testing parsing activities, Pharo launcher, use of GraphET for diseases tracking, chatting with Robots with Phratch. Some pictures are available from my tweet account: https://twitter.com/alexbergel Yeah, I should have used a different hashtag, but I realized that too late :-) Big big thanks to the organizers! Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

5 4

Issue 1033 in moose-technology: The result of loading a model from an MSE file is an OrderedCollection, not a MooseModel
by moose-technology＠googlecode.com 22 Dec '13

22 Dec '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1033 by wet...(a)gmail.com: The result of loading a model from an MSE file is an OrderedCollection, not a MooseModel http://code.google.com/p/moose-technology/issues/detail?id=1033 When loading a model from an MSE file, the result is not a MooseModel per se, but an OrderedCollection of various types (methods, invocations, accesses), and probably everything that should be inside, except that it is unstructured. Experienced this on a Windows platform, with the latest version of Moose (5.0 development on Pharo 3). -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 1

Issue 1035 in moose-technology: GTInspector should gray out special variables
by moose-technology＠googlecode.com 22 Dec '13

22 Dec '13

Status: New Owner: ---- CC: chisvasi...(a)gmail.com Labels: Type-Enhancement Priority-Medium Component-GlamorousToolkit Milestone-5.0 New issue 1035 by tu...(a)tudorgirba.com: GTInspector should gray out special variables http://code.google.com/p/moose-technology/issues/detail?id=1035 In the current implementation, self and other special variables appear with an underscore prefix. They should simply be grayed out. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 1

Error on http://www.themoosebook.org
by Juraj Kubelka 22 Dec '13

22 Dec '13

Hi! Whenever I try to search a text in search dialog, it says message below. Cheers, Jura Internal Error Error: subscript is out of bounds: 8218 ByteArray(Object)>>errorSubscriptBounds: ByteArray(Object)>>at: WideString(String)>>findSubstring:in:startingAt:matchTable: WideString(String)>>findString:startingAt:caseSensitive: WideString(String)>>includesSubstring:caseSensitive: [] in [] in PRFullTextSearch>>visitStructure: [] in Set(Collection)>>anySatisfy: Set>>do: Set(Collection)>>anySatisfy: [] in PRFullTextSearch>>visitStructure: SortedCollection(OrderedCollection)>>do: MAPriorityContainer(MAContainer)>>do: PRFullTextSearch>>visitStructure: PRFullTextSearch(PRVisitor)>>visitCase: PRFullTextSearch(PRVisitor)>>visitPublication: PRFullTextSearch(PRVisitor)>>visitPortion: BOPortion>>accept: BOPortion(Object)>>acceptDecorated: [] in BOPortion(PRDecorated)>>acceptDecorated: BOPortion(PRDecorated)>>decorationsDo:ownerDo:

2 1

Re: [Pharo-dev] gtinspector deconstructed
by Tudor Girba 21 Dec '13

21 Dec '13

Also, as you pointed out, it is indeed better for a SequenceableCollection to show the indexes for each item. So, now the inspector shows it as well. [image: Inline image 1] Cheers, Doru On Sat, Dec 21, 2013 at 11:45 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi Sven, > > Thanks for the suggestions. Integer and Float now have specific extensions > to the State presentation. > > [image: Inline image 3] > > [image: Inline image 1] > > You can see more details about how this works here: > > http://www.humane-assessment.com/blog/extending-variables-shown-in-gtinspec… > > Cheers, > Doru > > > -- www.tudorgirba.com "Every thing has its own flow"

1 0

gtinspector deconstructed
by Tudor Girba 20 Dec '13

20 Dec '13

Hi, I took a bit of time to describe how the GTInspector works, what makes it different, and to provide hints for several usage scenarios. http://www.humane-assessment.com/blog/the-moldable-gtinspector-deconstructed It's a long post, I know :), but please take a look. As you might know, this is the default inspector in the Moose image, but it can also be loaded in a fresh Pharo image. I am particularly interested in the following: - if you never used it, and tried it now, what don't you like? - if you used it, was there anything that you did not know? - and of course, what do you like about it? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

2 3

Color the runtime stack
by Alexandre Bergel 20 Dec '13

20 Dec '13

Hi! Andrei did an excellent job of what I think could be a big big plus of the debugger in Moose. Here is an example: The stack is colored according to what you click. I believe this will ease the navigation and browsing of the runtime stack. I suggest to not have a setting for this, but have it as a default, else nobody will use it. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

do not forget to tweet the #moosedojo (eof)
by Tudor Girba 20 Dec '13

20 Dec '13

1 0

PetitParser PPCompositeParser, Infinite loop ?
by Benjamin AREZKI 19 Dec '13

19 Dec '13

Hi, To explain my problem I will take this sample , my parser is a PPCompositeParser. ClassOrInterfaceType: ClassType / InterfaceType ClassType:TypeDeclSpecifier, TypeArgumentsopt InterfaceType: TypeDeclSpecifier, TypeArgumentsopt TypeDeclSpecifier: TypeName / ClassOrInterfaceType . Identifier TypeName: Identifier /TypeName . Identifier Ok, so Identifier works well, no problem but when I tested typeDeclSpecifier, I lost the contral of Pharo but I don't know why because I use a PPCompositeParser. For the moment I use some tricks but I would like it works normally. Thanks for your help.

10 19

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev