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

Implement method of storing a "default" layout of nodes (as moved/saved by editors) #80

Closed
kltm opened this issue Aug 27, 2014 · 2 comments

Comments

@kltm
Copy link
Member

kltm commented Aug 27, 2014

Related to #16, we need to have a method of saving the manual layout of nodes that does not rely on the participation of Barista.

After talking to Heiko a little and trying different thought experiments, we decided that the best method would be to essentially have a user option in a menu to save/snapshot the current layout ("Are you really sure you want to do this?"). The layout is bulk sent back to Minerva, where is is saved as your standard instance property. During initial layout:

algorithm < model instance hint < barista current location
@kltm
Copy link
Member Author

kltm commented Oct 8, 2014

Out of a discussion of #16, while this could be done in a "clever" way of having Barista inject this information during certain operations, there would be trouble with complete and up-to-date information. This is best done by a special op on the client that first scans the current locations.

@kltm kltm added the duplicate label May 7, 2015
@kltm
Copy link
Member Author

kltm commented May 7, 2015

Essentially a dupe of #113.

@kltm kltm closed this as completed May 7, 2015
@kltm kltm modified the milestone: wishlist Jul 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant