Re: Issue 460 in moose-technology: scaleBy: should be in shapes, and not in MONode

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Issue 460 in moose-technology: scaleBy: should be in shapes, and not in MONode

moose-technology
Updates:
        Labels: Component-Mondrian

Comment #1 on issue 460 by [hidden email]: scaleBy: should be in  
shapes, and not in MONode
http://code.google.com/p/moose-technology/issues/detail?id=460

(No comment was entered for this change.)

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 460 in moose-technology: scaleBy: should be in shapes, and not in MONode

moose-technology
Updates:
        Labels: -Milestone-4.2 Milestone-4.3

Comment #2 on issue 460 by [hidden email]: scaleBy: should be in  
shapes, and not in MONode
http://code.google.com/p/moose-technology/issues/detail?id=460

(No comment was entered for this change.)

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 460 in moose-technology: scaleBy: should be in shapes, and not in MONode

moose-technology
Updates:
        Labels: -Milestone-4.3

Comment #3 on issue 460 by [hidden email]: scaleBy: should be in  
shapes, and not in MONode
http://code.google.com/p/moose-technology/issues/detail?id=460

(No comment was entered for this change.)

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 460 in moose-technology: scaleBy: should be in shapes, and not in MONode

moose-technology
Updates:
        Status: WontFix

Comment #4 on issue 460 by [hidden email]: scaleBy: should be in  
shapes, and not in MONode
http://code.google.com/p/moose-technology/issues/detail?id=460

I have doubt about it.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 460 in moose-technology: scaleBy: should be in shapes, and not in MONode

moose-technology

Comment #5 on issue 460 by [hidden email]: scaleBy: should be in  
shapes, and not in MONode
http://code.google.com/p/moose-technology/issues/detail?id=460

I believe this should be in the canvas.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 460 in moose-technology: scaleBy: should be in shapes, and not in MONode

moose-technology

Comment #6 on issue 460 by [hidden email]: scaleBy: should be in  
shapes, and not in MONode
http://code.google.com/p/moose-technology/issues/detail?id=460

It is currently in MORoot. But a node (or a shape) has to be able to scale  
itself. If it is solely defined on MOCanvas, then the canvas has to modify  
the bounds of the node, which is not nice.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 460 in moose-technology: scaleBy: should be in shapes, and not in MONode

moose-technology

Comment #7 on issue 460 by [hidden email]: scaleBy: should be in  
shapes, and not in MONode
http://code.google.com/p/moose-technology/issues/detail?id=460

No. I meant the real canvas. The node should not know about zooming. This  
should be handled transparently by the infrastructure.

In VW we had a wrapper that handled the zooming.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev