Hi
I was working on translating the center of the radial tree at the middle of the window and I faced a problem.
I had already faced it when working on the ForceBasedLayout.
How does the layout access to his view to get informations ? (Basically it could be very useful to access to the camera to have size informations...)
Regards
Mathieu
Yes we discussed with mathieu and this is important for a layout to know - the dimensions of the window so that the layout can be smart - the camera position - the size of the nodes so how a layout get such information?
Stef
On May 13, 2013, at 4:48 PM, mathieubmddehouck@mailoo.org wrote:
Hi
I was working on translating the center of the radial tree at the middle of the window and I faced a problem.
I had already faced it when working on the ForceBasedLayout.
How does the layout access to his view to get informations ? (Basically it could be very useful to access to the camera to have size informations...)
Regards
Mathieu
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
This is interesting request which can have some consequences. Majority of moose code I have seen is like that: -=-=- view := ROMondrianViewBuilder new. elements := view nodes: (1 to: 10). view gridLayout. view open. -=-=- The layout is applied before a window exists. So you can write: -=-=- view := ROMondrianViewBuilder new. elements := view nodes: (1 to: 10). view gridLayout. view open. elements any view camera windowSize inspect. "!!!!" -=-=- But you do not obtain expected data if you write: -=-=- view := ROMondrianViewBuilder new. elements := view nodes: (1 to: 10). elements any view camera windowSize inspect. "!!!!" view gridLayout. view open. -=-=-
2013/5/14 stephane ducasse stephane.ducasse@free.fr
Yes we discussed with mathieu and this is important for a layout to know
- the dimensions of the window
so that the layout can be smart
Example above.
- the camera position
Example above.
- the size of the nodes
anElement extent
so how a layout get such information?
Stef
Cheers, Jura
On May 13, 2013, at 4:48 PM, mathieubmddehouck@mailoo.org wrote:
Hi
I was working on translating the center of the radial tree at the middle of the window and I faced a problem.
I had already faced it when working on the ForceBasedLayout.
How does the layout access to his view to get informations ? (Basically it could be very useful to access to the camera to have size informations...)
Regards
Mathieu
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I have the impression the job of a layout is to locate nodes in a 2d space. Indeed, we should be able to parametrize it. But I am not convinced the layout should have a dependency to the class ROCamera.
Alexandre
On May 14, 2013, at 5:15 AM, stephane ducasse stephane.ducasse@free.fr wrote:
Yes we discussed with mathieu and this is important for a layout to know
- the dimensions of the window so that the layout can be smart
- the camera position
- the size of the nodes
so how a layout get such information?
Stef
On May 13, 2013, at 4:48 PM, mathieubmddehouck@mailoo.org wrote:
Hi
I was working on translating the center of the radial tree at the middle of the window and I faced a problem.
I had already faced it when working on the ForceBasedLayout.
How does the layout access to his view to get informations ? (Basically it could be very useful to access to the camera to have size informations...)
Regards
Mathieu
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi Mathieu,
I am back from a short break. Back to answering question, fixing bugs and addressing issues :-)
Well... the question is the layout should really know about the camera? I like to think that the job of a layout is to properly locate nodes. In the case that the window size matters, then it should be provided to the layout as a parameter.
To position the layout in the middle of a window, I have just added the necessary. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= view nodes: (Collection withAllSubclasses). view edgesFrom: #superclass. view radialTreeLayout. view center. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Look at the implementer of #center to see how ROFocusView class>>centerView: is called
Cheers, Alexandre
On May 13, 2013, at 10:48 AM, mathieubmddehouck@mailoo.org wrote:
Hi
I was working on translating the center of the radial tree at the middle of the window and I faced a problem.
I had already faced it when working on the ForceBasedLayout.
How does the layout access to his view to get informations ? (Basically it could be very useful to access to the camera to have size informations...)
Regards
Mathieu
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
How do you do it? Because I do not have the code of roassal at hand?
The layout needs to have all the information available: node location node size window / canvas size Now don't we need to know the level of details
Hi Mathieu,
I am back from a short break. Back to answering question, fixing bugs and addressing issues :-)
Well... the question is the layout should really know about the camera? I like to think that the job of a layout is to properly locate nodes. In the case that the window size matters, then it should be provided to the layout as a parameter.
To position the layout in the middle of a window, I have just added the necessary.
view nodes: (Collection withAllSubclasses). view edgesFrom: #superclass. view radialTreeLayout. view center. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Look at the implementer of #center to see how ROFocusView class>>centerView: is called
Cheers, Alexandre
On May 13, 2013, at 10:48 AM, mathieubmddehouck@mailoo.org wrote:
Hi
I was working on translating the center of the radial tree at the middle of the window and I faced a problem.
I had already faced it when working on the ForceBasedLayout.
How does the layout access to his view to get informations ? (Basically it could be very useful to access to the camera to have size informations...)
Regards
Mathieu
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
How do you do it? Because I do not have the code of roassal at hand?
The layout needs to have all the information available: node location node size window / canvas size
Now don't we need to know the level of details
the node location and size is easy: ROElement new position; extent
The window and canvas size can be accessed from the layout, however I discourage to do this. Instead, the window and canvas size should be provided as parameters to the layout. If you face a situation where this is not obvious, then we should see how to address this.
Cheers, Alexandre
Hi Mathieu,
I am back from a short break. Back to answering question, fixing bugs and addressing issues :-)
Well... the question is the layout should really know about the camera? I like to think that the job of a layout is to properly locate nodes. In the case that the window size matters, then it should be provided to the layout as a parameter.
To position the layout in the middle of a window, I have just added the necessary.
view nodes: (Collection withAllSubclasses). view edgesFrom: #superclass. view radialTreeLayout. view center. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Look at the implementer of #center to see how ROFocusView class>>centerView: is called
Cheers, Alexandre
On May 13, 2013, at 10:48 AM, mathieubmddehouck@mailoo.org wrote:
Hi
I was working on translating the center of the radial tree at the middle of the window and I faced a problem.
I had already faced it when working on the ForceBasedLayout.
How does the layout access to his view to get informations ? (Basically it could be very useful to access to the camera to have size informations...)
Regards
Mathieu
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On May 15, 2013, at 5:19 PM, Alexandre Bergel alexandre.bergel@me.com wrote:
How do you do it? Because I do not have the code of roassal at hand?
The layout needs to have all the information available: node location node size window / canvas size
Now don't we need to know the level of details
the node location and size is easy: ROElement new position; extent
The window and canvas size can be accessed from the layout, however I discourage to do this. Instead, the window and canvas size should be provided as parameters to the layout.
How ? because you do not want to force the enduser to write
treeLayout: window extent (Because the guy does not have the idea how to access the extent)
why if the layout know the nodes it cannot access the size of the area where it should position the nodes?
If you face a situation where this is not obvious, then we should see how to address this.
Cheers, Alexandre
Hi Mathieu,
I am back from a short break. Back to answering question, fixing bugs and addressing issues :-)
Well... the question is the layout should really know about the camera? I like to think that the job of a layout is to properly locate nodes. In the case that the window size matters, then it should be provided to the layout as a parameter.
To position the layout in the middle of a window, I have just added the necessary.
view nodes: (Collection withAllSubclasses). view edgesFrom: #superclass. view radialTreeLayout. view center. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Look at the implementer of #center to see how ROFocusView class>>centerView: is called
Cheers, Alexandre
On May 13, 2013, at 10:48 AM, mathieubmddehouck@mailoo.org wrote:
Hi
I was working on translating the center of the radial tree at the middle of the window and I faced a problem.
I had already faced it when working on the ForceBasedLayout.
How does the layout access to his view to get informations ? (Basically it could be very useful to access to the camera to have size informations...)
Regards
Mathieu
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
The layout needs to have all the information available: node location
ROElement>>position
node size
ROElement>>extent ROElement>>bounds
window / canvas size
ROCamera>>windowSize ROCamera>>extent "it counts scale" ROCamera>>realExtent ROCamera>>scale ROCamera>>position
ROLayout does not depends on an ROView or ROCamera. If you need it pass it as an argument to your layout.
Cheers, Jura
Now don't we need to know the level of details
Hi Mathieu,
I am back from a short break. Back to answering question, fixing bugs
and addressing issues :-)
Well... the question is the layout should really know about the camera?
I like to think that the job of a layout is to properly locate nodes. In the case that the window size matters, then it should be provided to the layout as a parameter.
To position the layout in the middle of a window, I have just added the
necessary.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= view nodes: (Collection withAllSubclasses). view edgesFrom: #superclass. view radialTreeLayout. view center. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Look at the implementer of #center to see how ROFocusView
class>>centerView: is called
Cheers, Alexandre
On May 13, 2013, at 10:48 AM, mathieubmddehouck@mailoo.org wrote:
Hi
I was working on translating the center of the radial tree at the
middle of the window and I faced a problem.
I had already faced it when working on the ForceBasedLayout.
How does the layout access to his view to get informations ? (Basically
it could be very useful to access to the camera to have size informations...)
Regards
Mathieu
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On May 15, 2013, at 5:21 PM, Juraj Kubelka Juraj.Kubelka@gmail.com wrote:
The layout needs to have all the information available: node location
ROElement>>position
node sizeROElement>>extent ROElement>>bounds
window / canvas sizeROCamera>>windowSize ROCamera>>extent "it counts scale" ROCamera>>realExtent ROCamera>>scale ROCamera>>position
ROLayout does not depends on an ROView or ROCamera. If you need it pass it as an argument to your layout.
but how? are you saying that the end user should write
self treeLayout: camera windowSize?
I imagine that the layout should not depend on the camera position but it should depend on the total canvas size. So how do we get it? realExtent?
Stef
Cheers, Jura
Now don't we need to know the level of details
Hi Mathieu,
I am back from a short break. Back to answering question, fixing bugs and addressing issues :-)
Well... the question is the layout should really know about the camera? I like to think that the job of a layout is to properly locate nodes. In the case that the window size matters, then it should be provided to the layout as a parameter.
To position the layout in the middle of a window, I have just added the necessary.
view nodes: (Collection withAllSubclasses). view edgesFrom: #superclass. view radialTreeLayout. view center. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Look at the implementer of #center to see how ROFocusView class>>centerView: is called
Cheers, Alexandre
On May 13, 2013, at 10:48 AM, mathieubmddehouck@mailoo.org wrote:
Hi
I was working on translating the center of the radial tree at the middle of the window and I faced a problem.
I had already faced it when working on the ForceBasedLayout.
How does the layout access to his view to get informations ? (Basically it could be very useful to access to the camera to have size informations...)
Regards
Mathieu
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi Stef,
On May 15, 2013, at 8:57 PM, stephane ducasse stephane.ducasse@free.fr wrote:
On May 15, 2013, at 5:21 PM, Juraj Kubelka Juraj.Kubelka@gmail.com wrote:
The layout needs to have all the information available: node location
ROElement>>position
node sizeROElement>>extent ROElement>>bounds
window / canvas sizeROCamera>>windowSize ROCamera>>extent "it counts scale" ROCamera>>realExtent ROCamera>>scale ROCamera>>position
ROLayout does not depends on an ROView or ROCamera. If you need it pass it as an argument to your layout.
but how? are you saying that the end user should write
self treeLayout: camera windowSize?
The passing of the camera should happen in the layout utility method. So, ROMondrianViewBuilder>>treeLayout which is the one that instantiates the layout, will be reponsible for passing the information.
Cheers, Doru
I imagine that the layout should not depend on the camera position but it should depend on the total canvas size. So how do we get it? realExtent?
Stef
Cheers, Jura
Now don't we need to know the level of details
Hi Mathieu,
I am back from a short break. Back to answering question, fixing bugs and addressing issues :-)
Well... the question is the layout should really know about the camera? I like to think that the job of a layout is to properly locate nodes. In the case that the window size matters, then it should be provided to the layout as a parameter.
To position the layout in the middle of a window, I have just added the necessary.
view nodes: (Collection withAllSubclasses). view edgesFrom: #superclass. view radialTreeLayout. view center. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Look at the implementer of #center to see how ROFocusView class>>centerView: is called
Cheers, Alexandre
On May 13, 2013, at 10:48 AM, mathieubmddehouck@mailoo.org wrote:
Hi
I was working on translating the center of the radial tree at the middle of the window and I faced a problem.
I had already faced it when working on the ForceBasedLayout.
How does the layout access to his view to get informations ? (Basically it could be very useful to access to the camera to have size informations...)
Regards
Mathieu
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Don't give to get. Just give."
We are discussing about redesigning the layout hierarchy I understand, not a particular layout. In that case, an area needs to be provided I imagine. Because you may want to have an infinite (both in x or y) of the space where you want to layout the nodes. The layout itself cannot be know this. For example, you may wish to do a grid layout where area can be infinite horizontally and/or vertically. The camera or window size do not know about this.
Not sure whether this is clear or not. Maybe we could have a skype session? Today? in 1 hour?
Alexandre
On May 15, 2013, at 2:57 PM, stephane ducasse stephane.ducasse@free.fr wrote:
On May 15, 2013, at 5:21 PM, Juraj Kubelka Juraj.Kubelka@gmail.com wrote:
The layout needs to have all the information available: node location
ROElement>>position
node sizeROElement>>extent ROElement>>bounds
window / canvas sizeROCamera>>windowSize ROCamera>>extent "it counts scale" ROCamera>>realExtent ROCamera>>scale ROCamera>>position
ROLayout does not depends on an ROView or ROCamera. If you need it pass it as an argument to your layout.
but how? are you saying that the end user should write
self treeLayout: camera windowSize?
I imagine that the layout should not depend on the camera position but it should depend on the total canvas size. So how do we get it? realExtent?
Stef
Cheers, Jura
Now don't we need to know the level of details
Hi Mathieu,
I am back from a short break. Back to answering question, fixing bugs and addressing issues :-)
Well... the question is the layout should really know about the camera? I like to think that the job of a layout is to properly locate nodes. In the case that the window size matters, then it should be provided to the layout as a parameter.
To position the layout in the middle of a window, I have just added the necessary.
view nodes: (Collection withAllSubclasses). view edgesFrom: #superclass. view radialTreeLayout. view center. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Look at the implementer of #center to see how ROFocusView class>>centerView: is called
Cheers, Alexandre
On May 13, 2013, at 10:48 AM, mathieubmddehouck@mailoo.org wrote:
Hi
I was working on translating the center of the radial tree at the middle of the window and I faced a problem.
I had already faced it when working on the ForceBasedLayout.
How does the layout access to his view to get informations ? (Basically it could be very useful to access to the camera to have size informations...)
Regards
Mathieu
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On May 15, 2013, at 9:09 PM, Alexandre Bergel alexandre.bergel@me.com wrote:
We are discussing about redesigning the layout hierarchy I understand, not a particular layout. In that case, an area needs to be provided I imagine. Because you may want to have an infinite (both in x or y) of the space where you want to layout the nodes. The layout itself cannot be know this. For example, you may wish to do a grid layout where area can be infinite horizontally and/or vertically. The camera or window size do not know about this.
ok I see. the problem is - I'm not sure that having infinity is useful. do you have real scenario where you need that. - the layout should know the extent where it can lay down nodes.
Stef
Not sure whether this is clear or not. Maybe we could have a skype session? Today? in 1 hour?
Alexandre
On May 15, 2013, at 2:57 PM, stephane ducasse stephane.ducasse@free.fr wrote:
On May 15, 2013, at 5:21 PM, Juraj Kubelka Juraj.Kubelka@gmail.com wrote:
The layout needs to have all the information available: node location
ROElement>>position
node sizeROElement>>extent ROElement>>bounds
window / canvas sizeROCamera>>windowSize ROCamera>>extent "it counts scale" ROCamera>>realExtent ROCamera>>scale ROCamera>>position
ROLayout does not depends on an ROView or ROCamera. If you need it pass it as an argument to your layout.
but how? are you saying that the end user should write
self treeLayout: camera windowSize?
I imagine that the layout should not depend on the camera position but it should depend on the total canvas size. So how do we get it? realExtent?
Stef
Cheers, Jura
Now don't we need to know the level of details
Hi Mathieu,
I am back from a short break. Back to answering question, fixing bugs and addressing issues :-)
Well... the question is the layout should really know about the camera? I like to think that the job of a layout is to properly locate nodes. In the case that the window size matters, then it should be provided to the layout as a parameter.
To position the layout in the middle of a window, I have just added the necessary.
view nodes: (Collection withAllSubclasses). view edgesFrom: #superclass. view radialTreeLayout. view center. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Look at the implementer of #center to see how ROFocusView class>>centerView: is called
Cheers, Alexandre
On May 13, 2013, at 10:48 AM, mathieubmddehouck@mailoo.org wrote:
Hi
I was working on translating the center of the radial tree at the middle of the window and I faced a problem.
I had already faced it when working on the ForceBasedLayout.
How does the layout access to his view to get informations ? (Basically it could be very useful to access to the camera to have size informations...)
Regards
Mathieu
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
the problem is
- I'm not sure that having infinity is useful. do you have real scenario where you need that.
- the layout should know the extent where it can lay down nodes.
This is the current behavior in for the horizontalLineLayout. If you do
view nodes: (1 to: 1000). view horizontalLineLayout.
then you have a very long line of nodes. The layout considers the space infinite.
When I mentioned infinite areas, I had in mind the grid layout. You can do:
view nodes: (1 to: 10000). view gridLayout.
The roassal window is not large enough to show all the nodes. So, where do you want to scroll? Vertically or horizontally? Where the layout has room to expand the area with the nodes. This is what I meant with infinite area
Alexandre
Hi,
Different layouts have different needs. Some want to expand the space, like in the example below, some want to be limited by the space, like in the example of a FillInFlowLayout (available in Mondrian).
The decision of what to do with the constraints should lie with the layout, but in general, the layout should have the freedom of choosing. Thus, the layout should have access by default to all view information.
Cheers, Doru
On May 15, 2013, at 11:13 PM, Alexandre Bergel alexandre.bergel@me.com wrote:
the problem is
- I'm not sure that having infinity is useful. do you have real scenario where you need that.
- the layout should know the extent where it can lay down nodes.
This is the current behavior in for the horizontalLineLayout. If you do
view nodes: (1 to: 1000). view horizontalLineLayout.
then you have a very long line of nodes. The layout considers the space infinite.
When I mentioned infinite areas, I had in mind the grid layout. You can do:
view nodes: (1 to: 10000). view gridLayout.
The roassal window is not large enough to show all the nodes. So, where do you want to scroll? Vertically or horizontally? Where the layout has room to expand the area with the nodes. This is what I meant with infinite area
Alexandre
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"No matter how many recipes we know, we still value a chef."
On May 16, 2013, at 7:19 AM, Tudor Girba tudor@tudorgirba.com wrote:
Hi,
Different layouts have different needs. Some want to expand the space, like in the example below, some want to be limited by the space, like in the example of a FillInFlowLayout (available in Mondrian).
The decision of what to do with the constraints should lie with the layout, but in general, the layout should have the freedom of choosing. Thus, the layout should have access by default to all view information.
yes this is my point
Cheers, Doru
On May 15, 2013, at 11:13 PM, Alexandre Bergel alexandre.bergel@me.com wrote:
the problem is
- I'm not sure that having infinity is useful. do you have real scenario where you need that.
- the layout should know the extent where it can lay down nodes.
This is the current behavior in for the horizontalLineLayout. If you do
view nodes: (1 to: 1000). view horizontalLineLayout.
then you have a very long line of nodes. The layout considers the space infinite.
When I mentioned infinite areas, I had in mind the grid layout. You can do:
view nodes: (1 to: 10000). view gridLayout.
The roassal window is not large enough to show all the nodes. So, where do you want to scroll? Vertically or horizontally? Where the layout has room to expand the area with the nodes. This is what I meant with infinite area
Alexandre
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"No matter how many recipes we know, we still value a chef."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On May 15, 2013, at 11:13 PM, Alexandre Bergel alexandre.bergel@me.com wrote:
the problem is
- I'm not sure that having infinity is useful. do you have real scenario where you need that.
- the layout should know the extent where it can lay down nodes.
This is the current behavior in for the horizontalLineLayout. If you do
view nodes: (1 to: 1000). view horizontalLineLayout.
then you have a very long line of nodes. The layout considers the space infinite.
When I mentioned infinite areas, I had in mind the grid layout. You can do:
view nodes: (1 to: 10000). view gridLayout.
The roassal window is not large enough to show all the nodes. So, where do you want to scroll? Vertically or horizontally? Where the layout has room to expand the area with the nodes. This is what I meant with infinite area
Ok this is just large. I thought that the use of the camera was just to make sure that you can have large area (different from the physical canvas size).
Alexandre
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On Wed, May 15, 2013 at 11:13 PM, Alexandre Bergel alexandre.bergel@me.comwrote:
the problem is - I'm not sure that having infinity is useful. do you have real
scenario where you need that.
- the layout should know the extent where it can lay down nodes.This is the current behavior in for the horizontalLineLayout. If you do
view nodes: (1 to: 1000). view horizontalLineLayout.
then you have a very long line of nodes. The layout considers the space infinite.
When I mentioned infinite areas, I had in mind the grid layout. You can do:
view nodes: (1 to: 10000). view gridLayout.
The roassal window is not large enough to show all the nodes. So, where do you want to scroll? Vertically or horizontally? Where the layout has room to expand the area with the nodes. This is what I meant with infinite area
Now that we are on it, can the layout optimize itself to the available display area (e.g. Roassal window) so that the information presented by the visualization be viewed/analyze/understood with least scrolling? Just a thought.
Usman
Alexandre
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Alexandre Bergel -
Juraj Kubelka -
mathieubmddehouck＠mailoo.org -
stephane ducasse -
Tudor Girba -
Usman Bhatti