Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce more specific abstract tool classes #390

Open
michael opened this issue Jul 14, 2015 · 0 comments
Open

Introduce more specific abstract tool classes #390

michael opened this issue Jul 14, 2015 · 0 comments
Assignees

Comments

@michael
Copy link
Member

michael commented Jul 14, 2015

Currently we have Tool (which is always bound to a surface). Those were interacting with the selection and on app level we called tool.update() on each tool every time a selection:changed event occured.

Let's define more specific abstract types:

Tool (only has name property for registration, everything else is custom)

SurfaceTool (a tool that is bound to the currently active surface)

Has an ' update(surface, sel) method that is called from the surface manager whenever the selection changes.

DocumentTool (a tool that operates on a document)

Takes a document in the constructor

@michael michael self-assigned this Jul 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant