We need a TSConstraint about roassal3 HOT 10 CLOSED

We should import RTAlignment from Roassal2, and maybe, define some utility methods, in the same spirit of TRConstraint

from roassal3.

There is a version of RTAligment and RTResize that works pretty well on Roassal3

from roassal3.

But we need RSLocate...

from roassal3.

We have RSLocate

	| v shape e1 e2 |
	v := RSView new.
	shape := RSShapeBuilder box
		@ RSDraggable;
		onElement;
		color: TSColorPalette sequential blues3;
		size: 100.
		
	e1 := shape element.
	"e1 @ RSDraggable."
	e2 := shape element.
	e2 size: 20.
	RSLocate new
		padding: 1;
		fix: e1;
		movable: e2;
		inner;
		bottom;
		left;
		stick.
	v addAll: {e1. e2}.
	v @ RSControlsView.
	v open

from roassal3.

Looks really good!
Do you think that RSLocate can be a subclass of RSAbstractElementHandling?

from roassal3.

I do not thing so, RSLocate do es not need any method of that class

from roassal3.

But RSAbstractElementHandling has fixedElement:, and you have it again in RSLocate

from roassal3.

example10Locate
	<script: 'self new example10Locate'>
	| v shape e1 e2 |
	v := RSView new.
	shape := RSShapeBuilder box
		@ RSDraggable;
		onElement;
		color: TSColorPalette sequential blues3;
		size: 100.
	e1 := shape element.
	"e1 @ RSDraggable."
	e2 := shape element.
	e2 size: 20.
	RSLocate new
		padding: 1;
		inner;
		bottom;
		left;
		stick: e2 on: e1.
	v addAll:{e1. e2}.
	v @ RSControlsView.
	v open

I have change the code of RSLocate, fixedElement and movableElement are not instance variables in RSLocate, instead they are arguments in methods stick:on: and move:on. The main reason to change that is because RSLocate can be use in a lot of elements and not only in a couple. This is useful for RSLabeled, because RSLabeled uses an instance of RSLotate, you can use the same instance for multiple elements

from roassal3.

I have added a new animated example of this

Click on buttons to modify RSLocate.
click on big box to modify the padding of RSLocate

from roassal3.

Well done!

from roassal3.