Moose-dev September 2012

moose-dev@list.inf.unibe.ch

25 participants
124 discussions

Maintaining Smalltalk code on multiple platforms
by Stephan Eggermont 27 Sep '12

27 Sep '12

Hi, The code for Roassal works on both vw and Pharo. How is that maintained? Is one version leading, and the other derived from that? I noticed that the VW version has a different package structure (much more flat), and classes have the RO prefix. Or are changes simply performed twice? Or is Roassal an early user of the github based approach advocated by Dale? Stephan

2 1

Re: PetitParser parsing (Windows) end-of-line
by Stephan Eggermont 27 Sep '12

27 Sep '12

>If anybody as a clue on what's happening ... ? Sounds like #newline asParser already matches on cr, and then has a remaining character lf. PPJavaLexicon>lineTerminator ^ (Character lf asParser) / (Character cr asParser , (Character lf asParser ) optional ) Stephan

2 1

PetitParser parsing (Windows) end-of-line
by Nicolas Anquetil 27 Sep '12

27 Sep '12

Trying to parse the 3 possible ends of line: Linux=lf ; MacOS=cr; Windows=crlf given the rule: newline ^ #newline asParser / (#cr asParser , #newline asParser optional) The linux and MacOs tests pass testNewline1 ^self parse: String lf rule: #newline. testNewline2 ^self parse: String cr rule: #newline. But the windows one fails !?!?!?! testNewline3 ^self parse: String crlf rule: #newline. Any clue why? nicolas

1 1

Roassal: ROTranslatingShape - label besides node
by Dennis Schenk 27 Sep '12

27 Sep '12

Hi all, I am trying to place a label besides nodes (and make them stick at their place when dragging them around). Then I saw the ongoing discussion related to RoTranslatingShape, which seems is exactly what I would need. I looked at all the examples and the discussion, but am not able to make it work correctly. What I would want is to create some node, then have a label right at its bottom left side (or top left, or bottom right). The node is not resizable (and its contents, or children, do not change), so that should not be a problem. What I would like to do is simply something like in this image: http://cl.ly/image/3c1e1s15433Q. The difference to the other examples is probably that I already have a node in the view, and then I try to attach the label afterwards. So I have something like this: *testNodeLabeling* * | view rawView nodes node label |* * rawView := ROView new.* * view := ROMondrianViewBuilder view: rawView. * * view shape rectangle size: 100.* * nodes := view nodes: (Array with: 1).* * node := nodes at: 1.* * node translateTo: 20@20. * * label := (ROElement on: 'test') + (ROTranslatingShape new offset: 0 @ 20 negated) + ROLabel.* * rawView add: label.* * view noLayout.* * view open.* How would I now 'attach' this label to the node? Or is this the wrong way to go on about this? Cheers, Dennis

6 8

ROTranslatingShape mouse hotspot mis-alignment
by Ben Coman 26 Sep '12

26 Sep '12

I was trying to apply ROTranslatingShape to produce a label sitting above the children nodes. To understand it better how to get what I need, I made ROExample>>nestingTranslate to show a permutation of the order the shapes can be applied. I have attached a screen snapshot and fileout for this. The case I am particularly interested in is el3. The 'el0' case is the reference without any ROTranslatingShape. When running the example hover near and over the inner elements to view the misalignment of the mouse hotspot. I have marked the approximate offset in green in the snapshot. I notice that the existing call chain goes... ROView>>localElementAt: ROElement>>elementAt: ROElement>>contains: ROElemenet>>bounds ROShape>>extentFor: (union of extent of each shape) It seems to me the hotspot misalignment is related to the translation being applied at the shape draw level whereas the #contains: checking is done at the element level. This relies on the union of the shape extents to set the element bounds, but I can't see how that extent union could be modified to account for the translation - particular in the case of a negative translation since extents throw away information about any negative offset. So I thought perhaps that the element #contains: checking needs might be better chained through the shaped, so that the translation could be applied similar to ROTranslatingShape>>chainedDrawOn:for: and that this would not cause any/much additional computation since all the shapes were being cycled through anyway for #extentFor: Something like... ROView>>localElementAt: ROElement>>elementAt: ROElement>>contains: ROShape>>chainedContains:For: (for each shape) cheers, Ben 'From Pharo1.4 of 18 April 2012 [Latest update: #14457] on 22 September 2012 at 9:41:20 pm'! !ROExample methodsFor: 'nesting' stamp: 'BenComan 9/22/2012 17:04'! nestingTranslate " self new nestingTranslate " | rawView outer el0 el1 el2 el3 el4 el5 el6 el7 el8 | rawView := ROView new @ RODraggable. el0 := (ROElement on: 'el0, border, label') + ROBorder + ROLabel @ RODraggable @ ROLightlyHighlightable. el0 extent: 50@50. 1 to: 4 do: [ :n | el0 add: (ROElement spriteOn: n) @ ROLightlyHighlightable ]. ROGridLayout on: el0 elements . el1 := (ROElement on: 'el1, border, positive translation, label') + ROBorder + (ROTranslatingShape new offset: 0 @ 20) + ROLabel @ RODraggable @ ROLightlyHighlightable. el1 extent: 50@50. 1 to: 4 do: [ :n | el1 add: (ROElement spriteOn: n) @ ROLightlyHighlightable ]. ROGridLayout on: el1 elements . el2 := (ROElement on: 'el2, border, label, positive translation') + ROBorder + ROLabel + (ROTranslatingShape new offset: 0 @ 20) @ RODraggable @ ROLightlyHighlightable. el2 extent: 50@50. 1 to: 4 do: [ :n | el2 add: (ROElement spriteOn: n) @ ROLightlyHighlightable ]. ROGridLayout on: el2 elements . el3 := (ROElement on: 'el3, border, negative translation, label') + ROBorder + (ROTranslatingShape new offset: 0 @ 20 negated) + ROLabel @ RODraggable @ ROLightlyHighlightable. el3 extent: 50@50. 1 to: 4 do: [ :n | el3 add: (ROElement spriteOn: n) @ ROLightlyHighlightable ]. ROGridLayout on: el3 elements . el4 := (ROElement on: 'el4, border, label, negative translation') + ROBorder + ROLabel + (ROTranslatingShape new offset: 0 @ 20 negated) @ RODraggable @ ROLightlyHighlightable. el4 extent: 50@50. 1 to: 4 do: [ :n | el4 add: (ROElement spriteOn: n) @ ROLightlyHighlightable ]. ROGridLayout on: el4 elements . el5 := (ROElement on: 'el5, positive translation, label, border') + (ROTranslatingShape new offset: 0 @ 20) + ROLabel + ROBorder @ RODraggable @ ROLightlyHighlightable. el5 extent: 50@50. 1 to: 4 do: [ :n | el5 add: (ROElement spriteOn: n) @ ROLightlyHighlightable ]. ROGridLayout on: el5 elements . el6 := (ROElement on: 'el6, label, positive translation, border,') + ROLabel + (ROTranslatingShape new offset: 0 @ 20) + ROBorder @ RODraggable @ ROLightlyHighlightable. el6 extent: 50@50. 1 to: 4 do: [ :n | el6 add: (ROElement spriteOn: n) @ ROLightlyHighlightable ]. ROGridLayout on: el6 elements . el7 := (ROElement on: 'el7, negative translation, label, border') + (ROTranslatingShape new offset: 0 @ 20 negated) + ROLabel + ROBorder @ RODraggable @ ROLightlyHighlightable. el7 extent: 50@50. 1 to: 4 do: [ :n | el7 add: (ROElement spriteOn: n) @ ROLightlyHighlightable ]. ROGridLayout on: el7 elements . el8 := (ROElement on: 'el8, label, negative translation, border') + ROLabel + (ROTranslatingShape new offset: 0 @ 20 negated) + ROBorder @ RODraggable @ ROLightlyHighlightable. el8 extent: 50@50. 1 to: 4 do: [ :n | el8 add: (ROElement spriteOn: n) @ ROLightlyHighlightable ]. ROGridLayout on: el8 elements . outer := (ROElement spriteOn: 'outer') addAll: { el0. el1. el2. el3. el4. el5. el6. el7. el8 }. rawView add: outer. ROHorizontalLineLayout on: outer elements. rawView open ! !

2 3

How to parse a set of Delphi files to .mse?
by Torben Knerr 25 Sep '12

25 Sep '12

Hi everybody, I'm currently trying to parse a Delphi project into an .mse model so that I can import it into Moose. So far I have found "Petit Delphi": http://ss3.gemstone.com/ss/PetitDelphi.html/Overview I managed to add the Monticello Repository and I can now see the "PPDelphiAssemblyParser" and "PPDelpiLexicon" when I open the Tools -> PetitParser GUI. But now I'm a bit stuck - how can I create an .mse file out of the Delphi files on my disk now? It seems now that I have the parser I don't know how to use it... P.S.: the whole Smalltalk and Pharo environment is totally new to me, so please forgive the beginner questions :-) Thank you very much and best regards, Torben

4 6

Issue 844 in moose-technology: Moose Finder should let one browse the implementing method of a navigation item
by moose-technology＠googlecode.com 24 Sep '12

24 Sep '12

Status: New Owner: tu...(a)tudorgirba.com Labels: Type-Enhancement Priority-Medium Component-Finder Milestone-4.7 New issue 844 by tu...(a)tudorgirba.com: Moose Finder should let one browse the implementing method of a navigation item http://code.google.com/p/moose-technology/issues/detail?id=844 When browsing one entity, the first tab shows the navigation items from this entity. Especially for newbies it is important to see how these navigation methods are implemented. Thus, the contextual menu should offer the possibility to browse the corresponding methods. For example, when browsing a class, selecting the invoked methods should offer a menu item that opens a browser on FAMIXType>>invokedMethods.

1 2

adding scroll bars to Roassal Visualization
by Usman Bhatti 24 Sep '12

24 Sep '12

Hello, How to we add horizontal and vertical scroll bars to a Roassal visualization. I browsed through some examples but could not find one with these. tx. usman

4 16

Re: adding scroll bars to Roassal Visualization
by Usman Bhatti 21 Sep '12

21 Sep '12

Hello Doru, As Alex suggested, Pharo scrollbars can be added to Roassal visualizations (see the script at the end). Similarly, we can change GLMRoassalRender>>render: to add scrollbars to roassal visualizations in Glamour. Here is a proposition: render: aRoassalPresentation | view scrollPane| view := aRoassalPresentation view. aRoassalPresentation renderOn: view. aRoassalPresentation on: GLMPresentationUpdated send: #actOnPresentationUpdate: to: self. myMorph := ROMorph on: view stack. myMorph extent: (view raw encompassingRectangle extent + (40 @ 40)). scrollPane := ScrollPane new. scrollPane scroller addMorph: (myMorph). ^ scrollPane Indeed, that means that roassal visualizations are strongly-tied to Morphic. Do you want me to push my changes to Glamour so that we have morphic-based scrollbars unless there is a practical roassal-based solution? regards, Usman Alex's script: > > > =-=-=-=-=-= =-=-=-=-=-= =-=-=-=-=-= =-=-=-=-=-= =-=-=-=-=-= > | view roView roMorph pane window stack rawView nodes | > "Preparing" > window := StandardWindow labelled: 'windowLabel'. > window model: self. > window extent: 340 @ 480. > stack := ROViewStack new. > rawView := ROView new. > stack addView: rawView. > > view := ROMondrianViewBuilder initializedView: rawView. > view stack: stack. > view shape rectangle width: [ :c | c numberOfVariables * 5 ]; > height: #numberOfMethods. > nodes := view nodes: Collection withAllSubclasses. > view edgesFrom: #superclass. > view treeLayout. > view applyLayout. > > roMorph := ROMorph on: stack. > pane := ScrollPane new. > roMorph extent: ( view raw encompassingRectangle extent + (40 @ > 40)) . > pane scroller addMorph: (roMorph). > window > addMorph: pane > frame: (0@0 corner: 1@1). > window openInWorld. > =-=-=-=-=-= =-=-=-=-=-= =-=-=-=-=-= =-=-=-=-=-= =-=-=-=-=-= > >

1 0

Roassal: Lines and Arrows
by Dennis Schenk 20 Sep '12

20 Sep '12

Hi all, I'd like to customize lines with arrows a little bit more than seems to be possible out of the box at the moment and am looking for some pointers. I have attached a screenshot to explain what I'd like to achieve. I'd like to be able to: 1. Define a certain distance from the arrows beginning and end to the objects they are attached to - so they are not directly 'glued' to the objects. 2. Make lines wider, without just affecting the width of the line (and in the same extend the line the arrow is made up), but instead it should scale to nice looking arrows. 3. To place lines besides each other from and to the same object. Are some of these points already possible but I missed them? How would I best go on about modifying, extending Roassal to allow for edge styling in this way? Cheers, Dennis

4 5

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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev September 2012