Issue 904 in moose-technology: Roassal dragging subtrees (feature contribution)
by moose-technology＠googlecode.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 904 by benjamin...(a)gmail.com: Roassal dragging subtrees (feature
contribution)
http://code.google.com/p/moose-technology/issues/detail?id=904
With a tree layout, when dragging an element I needed to drag all the
children at the same time. I knocked up a solution sufficient to my needs
in about 40 minutes - see attached changeset. I might be a nice general
feature to add to Roassal but its a bit rough. It will likely need some
critical love to polish it before integration. Later it might be made to
work with ROSelection and multi-selected elements - but that is out of my
scope for the moment.
Attachments:
RODraggableWithOthers.2.cs 1.3 KB
9 years, 11 months
edges in 3D
by Usman Bhatti
Hello,
I am trying to create a new shape, an edge, in Roassal 3D between two
entities. My idea is to draw an edge from the position vector of a
source shape to the position vector of a target. The edge is created but
not at the correct position, it might be due to the fact that I need to set
the position of the edge shape or mismatch between position in Roassal and
OpenGL. Can you please have a look?
Attached with this mail my proposition for the shape that works with the
following script.
|el1 el2 els el3|
view := R3View new.
view camera translateLeft: -2; translateBackward:3.
el1 := (R3CubeShape new color: Color green) element.
el2 := (R3CubeShape new color: Color red) element.
el3 := (R3CubeShape new color: Color cyan) element.
els := { el1. el2. el3 }.
view add: (R3EdgeShape new from: el2; to: el3; size: 1; color: Color blue)
element.
view addAll: els.
R3XLineLayout on: els.
view addInteraction: R3MouseControl new.
view open.
9 years, 11 months
Issue 884 in moose-technology: The Roassal presentation should react to custom ports
by moose-technology＠googlecode.com
Status: New
Owner: tu...(a)tudorgirba.com
CC: chisvasi...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-Glamour
New issue 884 by tu...(a)tudorgirba.com: The Roassal presentation should
react to custom ports
http://code.google.com/p/moose-technology/issues/detail?id=884
The current implementation of the Roassal presentation relies only on the
original entity. However, given that Roassal can handle various animations,
we would benefit from an extra ability of the presentation to react to
other ports.
For example, the list presentation reacts to #selection. Similarly, Roassal
should be able to react to it or others as well. Only, given that Roassal
is generic, the reaction should be customisable, too.
Perhaps something like this:
a roassal
painting: [:view :entity | ... ]
on: #customPort do: [ :view :customValue | ... ]
9 years, 11 months
Re: Issue 987 in moose-technology: Roassal does not display edges when the source is not visible
by Alexandre Bergel
This is fixed in Roassal1.456. There was indeed a bug in the code.
Now, there is the following:
- A node is rendered if its bounds intersect with the bounds of the camera
- An edge is rendered if at least one of its extremity has its bounds intersect with the camera
As a consequence, an edge that has no extremity on screen is not displayed. Even if the line "go through" the camera bounds. Naturally, this is something that is easy to change. We can provide particular strategy to define what makes an edge visible or not.
Cheers
Alexandre
On Oct 19, 2013, at 3:41 AM, moose-technology(a)googlecode.com wrote:
>
> Comment #1 on issue 987 by tudor(a)tudorgirba.com: Roassal does not display edges when the source is not visible
> http://code.google.com/p/moose-technology/issues/detail?id=987
>
> Hmm. This problem seems to appear only when Roassal is embedded in Glamour. Try this:
>
> view := ROMondrianViewBuilder new.
> view nodes: { 1 . 2 }.
> view edgeFromAssociation: 2->1.
> view horizontalLineLayout horizontalGap: 3000.
> view open.
>
> vs.
>
> view := ROMondrianViewBuilder new.
> view nodes: { 1 . 2 }.
> view edgeFromAssociation: 2->1.
> view horizontalLineLayout horizontalGap: 3000.
> view openWithStatusbar.
>
> --
> You received this message because you were CC'd on the issue.
> You may adjust your notification preferences at:
> https://code.google.com/hosting/settings
>
> Reply to this email to add a comment or make updates.
>
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
9 years, 11 months
Build failed in Jenkins: moose-latest-dev-4.9 #1306
by admin＠moosetechnology.org
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.9/1306/>
------------------------------------------
Started by upstream project "petitjava" build number 283
originally caused by:
Started by upstream project "petitparser" build number 248
originally caused by:
Started by timer
Building remotely on moose-slave in workspace <https://ci.inria.fr/moose/job/moose-latest-dev-4.9/ws/>
Deleting project workspace... done
[moose-latest-dev-4.9] $ /bin/sh -xe /tmp/hudson5391896165167917732.sh
+ bash
+ wget --quiet -O - http://get.pharo.org/20+vmLatest
Downloading the latest 20 Image:
http://files.pharo.org/image/20/latest.zip
Pharo.image
Downloading the latest pharoVM:
http://files.pharo.org/vm/pharo/linux/latest.zip
pharo-vm/pharo
Downloading PharoV10.sources:
http://files.pharo.org/sources//PharoV10.sources.zip
Downloading PharoV20.sources:
http://files.pharo.org/sources//PharoV20.sources.zip
Creating starter scripts pharo and pharo-ui
+ ./pharo Pharo.image save moose-latest-dev-4.9
+ REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main
+ ./pharo moose-latest-dev-4.9.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development
[31m[33m
===============================================================================
Notice: Installing ConfigurationOfMoose development
===============================================================================
[0m[0m+ ./pharo moose-latest-dev-4.9.image mooseimagesetup --signature=https://ci.inria.fr/moose/job/moose-latest-dev-4.9/1306/
[31m==== Startup Error: ConnectionTimedOut: Data receive timed out.
[0mSocket>>waitForDataFor: in Block: [ConnectionTimedOut signal: 'Data receive timed ou...etc...
Socket>>waitForDataFor:ifClosed:ifTimedOut:
Socket>>waitForDataFor:
Socket>>receiveDataSignallingTimeout:into:startingAt:
SocketStream>>receiveData
SocketStream>>next
ZnLineReader>>processNext
ZnLineReader>>nextLine
ZnStatusLine>>readFrom:
ZnStatusLine class>>readFrom:
ZnResponse>>readHeaderFrom:
ZnResponse(ZnMessage)>>readFrom:
ZnResponse class(ZnMessage class)>>readFrom:
ZnClient>>executeRequestResponse
ZnClient>>getConnectionAndExecute in Block: [self executeRequestResponse]
BlockClosure>>ensure:
ZnClient>>getConnectionAndExecute
ZnClient>>executeWithRedirectsRemaining:
ZnClient>>executeWithRetriesRemaining: in Block: [self executeWithRedirectsRemaining: self maxNumbe...etc...
BlockClosure>>on:do:
ZnClient>>executeWithRetriesRemaining:
ZnClient>>executeWithRetriesRemaining: in Block: [:exception | retryCount > 0...
BlockClosure>>cull:
MethodContext(ContextPart)>>handleSignal: in Block: [self exceptionHandlerBlock cull: exception]
BlockClosure>>ensure:
MethodContext(ContextPart)>>handleSignal:
ConnectionTimedOut(Exception)>>signal
ConnectionTimedOut(Exception)>>signal:
ConnectionTimedOut class(Exception class)>>signal:
Socket>>waitForDataFor: in Block: [ConnectionTimedOut signal: 'Data receive timed ou...etc...
[0m[31mGot startup errors:
[0m[31m ConnectionTimedOut: Data receive timed out.
[0mBuild step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
9 years, 11 months
slice for 985
by Usman Bhatti
Hello,
Here is a slice for the bug 985 regarding splitters in glamour tables. It
should work with this script:
| wrapper |
wrapper := GLMWrapper new.
wrapper show: [:a |
a table
display: [ :x | 1 to: x ];
columnInset: 4;
splitterColor: Color red;
column: [:x | 'Numbers from 1 to ', x asString] evaluated: #asString;
column: 'Even' evaluated: [ :each | each even asString ];
column: 'Odd' evaluated: [ :each | each odd asString ] ].
wrapper openOn: 1000.
The idea is to provide the renderer with a columnInset number that acts as
a padding between splitters and the cell so that these both dont overlap.
we also tried to add the notion of splitter color but when embedding
widgets, the color of splitters is reset to transparent and that is beyond
the scope of this bug. we still retained the concept of splitter color
because it can be nice.
Drag and drop wont work with the slice as the mechanism is built to work
with Pharo inbox, instead import the slice with Monticello.
Usman & Rafael
9 years, 11 months
Build failed in Jenkins: moose-latest-dev-4.9 #1299
by admin＠moosetechnology.org
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.9/1299/>
------------------------------------------
Started by upstream project "glamour" build number 349
originally caused by:
[URLTrigger] A change within the response URL invocation (log)
Building remotely on moose-slave in workspace <https://ci.inria.fr/moose/job/moose-latest-dev-4.9/ws/>
Deleting project workspace... done
[moose-latest-dev-4.9] $ /bin/sh -xe /tmp/hudson4618962989300060370.sh
+ bash
+ wget --quiet -O - http://get.pharo.org/20+vmLatest
Downloading the latest 20 Image:
http://files.pharo.org/image/20/latest.zip
Pharo.image
Downloading the latest pharoVM:
http://files.pharo.org/vm/pharo/linux/latest.zip
pharo-vm/pharo
Downloading PharoV10.sources:
http://files.pharo.org/sources//PharoV10.sources.zip
Downloading PharoV20.sources:
http://files.pharo.org/sources//PharoV20.sources.zip
Creating starter scripts pharo and pharo-ui
+ ./pharo Pharo.image save moose-latest-dev-4.9
+ REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main
+ ./pharo moose-latest-dev-4.9.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development
[31m[33m
===============================================================================
Notice: Installing ConfigurationOfMoose development
===============================================================================
[0m[0m+ ./pharo moose-latest-dev-4.9.image mooseimagesetup --signature=https://ci.inria.fr/moose/job/moose-latest-dev-4.9/1299/
[31m==== Startup Error: ConnectionTimedOut: Data receive timed out.
[0mSocket>>waitForDataFor: in Block: [ConnectionTimedOut signal: 'Data receive timed ou...etc...
Socket>>waitForDataFor:ifClosed:ifTimedOut:
Socket>>waitForDataFor:
Socket>>receiveDataSignallingTimeout:into:startingAt:
SocketStream>>receiveData
SocketStream>>next
ZnLineReader>>processNext
ZnLineReader>>nextLine
ZnStatusLine>>readFrom:
ZnStatusLine class>>readFrom:
ZnResponse>>readHeaderFrom:
ZnResponse(ZnMessage)>>readFrom:
ZnResponse class(ZnMessage class)>>readFrom:
ZnClient>>executeRequestResponse
ZnClient>>getConnectionAndExecute in Block: [self executeRequestResponse]
BlockClosure>>ensure:
ZnClient>>getConnectionAndExecute
ZnClient>>executeWithRedirectsRemaining:
ZnClient>>executeWithRetriesRemaining: in Block: [self executeWithRedirectsRemaining: self maxNumbe...etc...
BlockClosure>>on:do:
ZnClient>>executeWithRetriesRemaining:
ZnClient>>executeWithRetriesRemaining: in Block: [:exception | retryCount > 0...
BlockClosure>>cull:
MethodContext(ContextPart)>>handleSignal: in Block: [self exceptionHandlerBlock cull: exception]
BlockClosure>>ensure:
MethodContext(ContextPart)>>handleSignal:
ConnectionTimedOut(Exception)>>signal
ConnectionTimedOut(Exception)>>signal:
ConnectionTimedOut class(Exception class)>>signal:
Socket>>waitForDataFor: in Block: [ConnectionTimedOut signal: 'Data receive timed ou...etc...
[0m[31mGot startup errors:
[0m[31m ConnectionTimedOut: Data receive timed out.
[0mBuild step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
9 years, 11 months
Build failed in Jenkins: moose-latest-dev-4.9 #1297
by admin＠moosetechnology.org
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.9/1297/>
------------------------------------------
[URLTrigger] A change within the response URL invocation (log)
[URLTrigger] A change within the response URL invocation (log)
Building remotely on moose-slave in workspace <https://ci.inria.fr/moose/job/moose-latest-dev-4.9/ws/>
Deleting project workspace... done
[moose-latest-dev-4.9] $ /bin/sh -xe /tmp/hudson8805368009257370614.sh
+ bash
+ wget --quiet -O - http://get.pharo.org/20+vmLatest
Downloading the latest 20 Image:
http://files.pharo.org/image/20/latest.zip
Pharo.image
Downloading the latest pharoVM:
http://files.pharo.org/vm/pharo/linux/latest.zip
pharo-vm/pharo
Downloading PharoV10.sources:
http://files.pharo.org/sources//PharoV10.sources.zip
Downloading PharoV20.sources:
http://files.pharo.org/sources//PharoV20.sources.zip
Creating starter scripts pharo and pharo-ui
+ ./pharo Pharo.image save moose-latest-dev-4.9
+ REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main
+ ./pharo moose-latest-dev-4.9.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development
[31m[33m
===============================================================================
Notice: Installing ConfigurationOfMoose development
===============================================================================
[0m[0m[31m[33m
*** Warning: Warning: This package depends on the following classes:
MOViewRenderer
You must resolve these dependencies before you will be able to load these definitions:
edgesDsm:from:to:
[0m[0m+ ./pharo moose-latest-dev-4.9.image mooseimagesetup --signature=https://ci.inria.fr/moose/job/moose-latest-dev-4.9/1297/
[31m==== Startup Error: ConnectionTimedOut: Data receive timed out.
[0mSocket>>waitForDataFor: in Block: [ConnectionTimedOut signal: 'Data receive timed ou...etc...
Socket>>waitForDataFor:ifClosed:ifTimedOut:
Socket>>waitForDataFor:
Socket>>receiveDataSignallingTimeout:into:startingAt:
SocketStream>>receiveData
SocketStream>>next
ZnLineReader>>processNext
ZnLineReader>>nextLine
ZnStatusLine>>readFrom:
ZnStatusLine class>>readFrom:
ZnResponse>>readHeaderFrom:
ZnResponse(ZnMessage)>>readFrom:
ZnResponse class(ZnMessage class)>>readFrom:
ZnClient>>executeRequestResponse
ZnClient>>getConnectionAndExecute in Block: [self executeRequestResponse]
BlockClosure>>ensure:
ZnClient>>getConnectionAndExecute
ZnClient>>executeWithRedirectsRemaining:
ZnClient>>executeWithRetriesRemaining: in Block: [self executeWithRedirectsRemaining: self maxNumbe...etc...
BlockClosure>>on:do:
ZnClient>>executeWithRetriesRemaining:
ZnClient>>executeWithRetriesRemaining: in Block: [:exception | retryCount > 0...
BlockClosure>>cull:
MethodContext(ContextPart)>>handleSignal: in Block: [self exceptionHandlerBlock cull: exception]
BlockClosure>>ensure:
MethodContext(ContextPart)>>handleSignal:
ConnectionTimedOut(Exception)>>signal
ConnectionTimedOut(Exception)>>signal:
ConnectionTimedOut class(Exception class)>>signal:
Socket>>waitForDataFor: in Block: [ConnectionTimedOut signal: 'Data receive timed ou...etc...
[0m[31mGot startup errors:
[0m[31m ConnectionTimedOut: Data receive timed out.
[0mBuild step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
9 years, 11 months
