Moose-dev July 2014

moose-dev@list.inf.unibe.ch

36 participants
143 discussions

by Stephan Eggermont

What's with spotlight2? Was that needed earlier and not anymore? Do we need a new baseline, or was it never needed? Stephan

9 years, 9 months

Re: [Pharo-dev] PetitParser in 3.0?

by Esteban Lorenzano

Hi, This is a question for the moosers :) Why there is no copy (with stable version) in metarepo of ll configurations that are under the moose umbrella? cheers, Esteban On 18 Jul 2014, at 10:00, phil(a)highoctane.be wrote: > I load it from the moose team on sth. Works for me, browser included. > > Le 18 juil. 2014 09:24, "Tudor Girba" <tudor(a)tudorgirba.com> a écrit : > In the case of Moose, #development and #bleedingEdge are the same. > > Doru > > > On Fri, Jul 18, 2014 at 9:18 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > I think what is loaded by CI is dependent on the workflow of the project. IMHO for most projects loading #bleedingEdge is the best thing to do. > > Norbert > > Am 18.07.2014 um 05:21 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > >> It loads #development as any CI job should do. >> >> Doru >> >> >> On Fri, Jul 18, 2014 at 1:40 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> Stephan Eggermont wrote >> > And there is a image build at >> > https://ci.inria.fr/pharo-contribution/job/PetitParser/ >> >> Interesting. I wonder what the ci is loading, because if I try to load the >> default group in Pharo 3.0, I get an error (hence I load 'Core' and have no >> problems) >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/PetitParser-in-3-0-tp4768398p4768407.html >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

9 years, 9 months

Roassal2 canvas extent in Glamour browsers

by Usman Bhatti

Hi, When using Roassal 2 in a glamour browser, the visualization gets clipped when too large. This appears to occur because the canvas does not adapt to the container morph (a TRMorph) dimensions and retains its default extent. To reproduce: |browser| browser := GLMTabulator new. browser title: 'Roassal 2 Visualization'. browser row: #visu. browser transmit to: #visu; andShow: [:a | a roassal2 title: 'Overview'; painting: [ :mondView :entity | view := mondView view. view addAll: ((RTEllipse new color: Color purple; size: 10) elementsOn: Collection withAllSubclasses) @ RTDraggable. RTEdge buildEdgesFromObjects: Collection withAllSubclasses from: #superclass to: #yourself inView: view. RTClusterLayout on: view elements edges: view edges. view edges do: [ :e | e trachelShape pushBack ]. "view canvas extent: (950 @ 550)." ]]. browser openOn: 1. Did someone notice similar behavior with spec? What would be good is that TRMorph should update the contained canvas extent when it is resized. usman [image: Inline image 2]

9 years, 9 months

Re: multiple source anchors

by Stephan Eggermont

Usman wrote: >Currently, we are still in prospective phase so having the relevant information is useful :). Macro's provide some interesting challenges here too. Stephan

9 years, 9 months

multiple source anchors

by Usman Bhatti

Hi, Do we have support for associating multiple file anchors to a single famix sourced entity? It would be useful when a module is composed of two or more source files (e.g. header/code files in C or partial classes in C#). tx, usman

9 years, 9 months

Issue 1082 in moose-technology: Inconsistent inspector variables values

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1082 by v.blonde...(a)gmail.com: Inconsistent inspector variables values http://code.google.com/p/moose-technology/issues/detail?id=1082 Describe the problem: what do you get? what do you expect? In the Moose Inpector, the value of a variable in the list is not equal to the printed value in the inspector evaluator part. See png attached. How to reproduce the problem: step by step if necessary create a class (Test) with a IV (test) and a initialize method ( initialize test := #test ) inspect : "Test new " In the evaluator of the inspector, Print it "test". The value should be nil which is not expected. Additional information: platform, context which may impact the problem Moose latest - W7 Please fill in the labels with the following information: * Type-Defect * Component-GTInspector -- 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

9 years, 9 months

[Moose Panel]With all (sub/super)classes

by Blondeau Vincent

Hello, In the moose panel, when I explore a class, I have the menu items : "with all superclasses" and "with all subclasses". I expect to have in theses collections respectively all the superclasses and all the subclasses but not the current class that I explore. I suggest either to remove the current class from theses collections or to rename "With all (sub/super)classes" to something else like "all (sub/super)classes hierarchy". What do you think about? Cheers, Vincent BLONDEAU ________________________________ Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

9 years, 9 months

Roassal2 - Window size

by Leo Perard

Hi, I have a bug in Roassal2 when I expand the Roassal2 window to fullscreen or if I open with the different size than default, the size of the view is too small view := RTView new. view @ RTDraggableView. el := (RTBox new size: 50; color: Color red) element. view add: el. view openInWindowSized: 1200 @ 720 With this example you have to drag the view to see the element -- Cheers, Leo Perard University of Lille 1

9 years, 9 months

NameCloud

by Alexandre Bergel

Hi! I have added a name cloud builder in Roassal. Maybe some of you will find it useful It is very primitive and does do much, but it does the primitive things :-) Here is an example: =-=-=-=-==-=-=-=-==-=-=-=-==-=-=-=-= RTNameCloud new addString: 'open | v shape | v := RTView new. shape := RTLabel new height: [ :assoc | assoc value ]; text: #key. v addAll: (shape elementsOn: table associations). RTFlowLayout on: v elements. v open'; open =-=-=-=-==-=-=-=-==-=-=-=-==-=-=-=-= It produces: A slightly more complicated example: =-=-=-=-==-=-=-=-==-=-=-=-==-=-=-=-= | b | b := RTNameCloud new. b addStrings: (RTNameCloud methods collect: #getSource). b open =-=-=-=-==-=-=-=-==-=-=-=-==-=-=-=-= produces: We did this name cloud builder because we had a need to process text extracted from StackExchange. We added a dictionary containing words that are not interesting. For example: =-=-=-=-==-=-=-=-==-=-=-=-==-=-=-=-= | b | b := RTNameCloud new. b minHeight: 20. b maxHeight: 30. b addString: 'I am not that tall but I speak many languages. But I have tall legs and big feet'. b open =-=-=-=-==-=-=-=-==-=-=-=-==-=-=-=-= It produces: Words such as ‘I’, ‘not’, ‘that’, ‘but’ are not shown. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 9 months

Metric normalizer

by Alexandre Bergel

Hi! I’ve just introduced a metric normalizer. This has been such a need! -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= v := RTView new. es := RTEllipse elementsOn: RTObject withAllSubclasses. es @ RTPopup. v addAll: es. RTMetricNormalizer new elements: es; normalizeColor: #numberOfLinesOfCode; alphaColor: 0.4; normalizeSize: #numberOfMethods min: 5 max: 15; normalizeX: #numberOfMethods min: 0 max: 300; normalizeY: #numberOfVariables min: 0 max: 300. v -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Here is the rendering: This will be a nice base when we will build GraphET3 Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 9 months

← Newer
1
...
7
8
9
10
11
12
13
14
15
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev July 2014