-
Notifications
You must be signed in to change notification settings - Fork 59
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
WIP: Model sync #128
Open
rksm
wants to merge
125
commits into
master
Choose a base branch
from
model-sync
base: master
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
WIP: Model sync #128
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@@ -145,6 +145,10 @@ Object.extend(lively.morphic, { | |||
} | |||
|
|||
}); | |||
Object.extend(lively, { | |||
show: lively.morphic.show, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this be called highlight
?
…stored in a local or remote data store. The interface for now includes: ## read - `#get` - `#subscribe` ## write - `#set` - `#commit` (transaction semantics) Thinks I'm working on: - (sub)handle access - reading tree changes - synchronization for collections
(internally now using an objectified path representation)
currently {type: 'identity', value: OBJECT}
…inally instead of last statement
…o prevent unnecessary double load
… own class indicateUpdate now also get information about all the morphs changed by an update
to indicate state, such as orange for changed and black for normal indicateUpdate now gets a list of changed (sub-)morphs
fixed old texts due to the intorduction of the author field
…, to allow for local DB again, for the tutorial
…owner bounds should be epi-morphs
…entations in the synchronized morph
… fail, and generated an unneccessary large amount of noise in log files
…ions pointing to an updateIndicator before copying
…ise, the original and replaced morphs behave differently for newly added inputs
…indicator with the updates list is sufficient.
… some smaller inconsistencies
…phs handle is available
… db and the ConsumingReferenceArea in the PartsBin
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
starting with an interface for syncing changes between objects stored in a local or remote data store. The interface for now includes:
ObjectHandle
read
#get
#subscribe
write
#set
#commit
(set ensuring no overwrites)Local Store
Thinks I'm working on: