Experiment with draw2D about quickmockup HOT 5 OPEN

@jdittrich zooming to mouse cursor must be solved now in AlaaSarhan@571f965

you were correct about using setScrollArea but another thing was missing.. the canvas container needed to be absolute displayed too.

from quickmockup.

In current version (commit AlaaSarhan@a6e9c0c), I tried to implement a first version of quickMockup approach, in which an element would belong to the container it is dropped inside.

It works basically, but it seems to suffer from performance issues sometimes as well as some odd behavior in combination with toFront.

Gotta give it a third try, probably with Raft-like approach of calculating contained elements on relevant events only, but unlike Raft, it would add them as children and remove them eventually when event is over.

from quickmockup.

first iteration of adding elements by drag&drop AlaaSarhan#1

from quickmockup.

Some open questions around raft:

• What quickmockup is that elements that are visually within a rectangle are also children of that rectangle. The children are not prevented in moving. As long as you drag the parent/child structure remains the same. As soon as you drop, it is evaluated where you dropped and the element is assigned to a new (or the old) parent.
• It seems not to actually attach children, rather in calculates what is "onboard" and then moves these along.
• We might want to write to or own raft method, since mostly we want the onboard elements to behave like children.
  • Currently we have a overwrite to raft
  • We could make elements that are entirely enclosed children of the innermost, enclosing element
  • We could have an anchor point. If it is enclosed by other elements the element with the ancor point becomes child of the most innermost ("top") element that encloses the point. Which would allow for some comprehensible overlapping things, e.g. desktop-menus having the anchor on top so they can be grouped with a menu bar and overlap the rest.

from quickmockup.

Or we basically only have rectangles that are duplicated and then "decorated" with special types like "window", "button", "layouting rectangle" (e.g. by having an on-context button that offers "decorations" on click)…

I'm starting to like this idea a lot, at least in concept.. thinking about it technically for now, perhaps I'll attempt to implement it soon

from quickmockup.