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 live synced view all the time #16

Closed
kltm opened this issue Feb 11, 2014 · 4 comments
Closed

Implement live synced view all the time #16

kltm opened this issue Feb 11, 2014 · 4 comments

Comments

@kltm
Copy link
Member

kltm commented Feb 11, 2014

Depends, is related to, #14

@kltm kltm added this to the Caltech 2014 milestone May 5, 2014
@cmungall cmungall modified the milestones: 2014-Q3, Caltech 2014 Jun 5, 2014
@kltm
Copy link
Member Author

kltm commented Aug 27, 2014

Any work here needs to sync with the eventual default layout solution in #80.

@kltm
Copy link
Member Author

kltm commented Oct 7, 2014

Current sub-items will be dealt with here:

  • for every model, there is a messaging "cubby" (hash) to store transient clobbering information
    • this should always be treated as an optional path needs to be in there
    • "layout" skimming can be passed as a function? do this internally to barista initially
  • all of cubby is passed to a client on model messaging connect; client does what it will (other uses besides layout); after update, the current message stream should keep things in sync

Cubby information will inevitably accumulate until forming a black hole, taking barista with it. Eventually, some important cubby (e.g. layout) information will need to be stored (and initially retrieved from) the server model on initialization.

kltm added a commit that referenced this issue Oct 8, 2014
@kltm kltm closed this as completed in 9934995 Oct 8, 2014
@kltm
Copy link
Member Author

kltm commented Oct 8, 2014

While layouts are syncing, merge and rebuild triggers are also needed.

@kltm kltm reopened this Oct 8, 2014
@kltm kltm closed this as completed in c1ea049 Oct 10, 2014
@kltm
Copy link
Member Author

kltm commented Oct 10, 2014

Messaging system can now intercept and read outgoing models from the api and pass them out; the client can now catch those messages on callback and hook them back into the minerva manager, updating the models.

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

2 participants