snap/store.js, branch developmentUnnamed repository; edit this file 'description' to name the repository.http://git.schneefux.xyz/schneefux/snap/atom/store.js?h=development2015-07-23T12:26:06Zmerge upstream2015-07-23T12:26:06ZGubolingubolin@fantasymail.de2015-07-23T12:26:06Zurn:sha1:5aec52889d79a8257971095719195fabcbc33559Revert to "new" for object creation2015-06-25T13:11:51Zjmoenigjens@moenig.org2015-06-25T13:11:51Zurn:sha1:4c21c9f187033172fa58a1bd3100d7c494617f10
and prepare for new release
Fix missing initialization call in SnapSerializer()2015-06-17T21:26:56ZNathan Dinsmorenathan@users.noreply.github.com2015-06-17T21:26:56Zurn:sha1:013e2740d853b660fbc48cda247b6fe711aecce9Use Object.create(…) instead of new …() for inheritance (faster)2015-06-17T21:11:40ZNathan Dinsmorenathan@users.noreply.github.com2015-06-17T21:11:40Zurn:sha1:87c2503571bd7f5e753bc16a05bd198fc58d7d7cfixed #7842015-04-27T02:47:37ZJens Mönigjens@moenig.org2015-04-27T02:47:37Zurn:sha1:9385e4b57c88c382c1758e54c258ac237d238679merge branch OOP2015-03-24T17:29:54ZGubolingubolin@fantasymail.de2015-03-24T17:29:54Zurn:sha1:bdd780e0030507626c947f85880a9eaa36e24194tweak inherited variable watcher slider deserialization2015-03-24T16:16:00ZJens Mönigjens@moenig.org2015-03-24T16:16:00Zurn:sha1:457224dd620eea4f20f24ebc62391363333cd00fPrototypal inheritance of sprite-local variables2015-03-21T10:12:43ZJens Mönigjens@moenig.org2015-03-21T10:12:43Zurn:sha1:4acf1896bd9fa57d3dbe3f4721b6790c6f3b0d56
(experimental) slotwise inheritance à la Henry Lieberman for
sprite-local variables.
see
http://web.media.mit.edu/~lieber/Lieberary/OOP/Delegation/Delegation.htm
l
Let a sprite inherit another sprite’s local variables by making it the
“parent” in the sprite-icon’s context menu (the button icon in the
sprite corral underneath the stage). The child not only inherits the
variable slot but also - dynamically - the parent variable’s value.
Changing the parent’s variable value also changes it for every child.
If a child uses SET or CHANGE on an inherited variable it automatically
“shadows” it with its own value, thereby stopping dynamic participation
in the parent slot’s value (in effect dis-inheriting that slot).
Deleting a shadowed variable slot once again reinstates its inheritance
status.
inherited variables are shown as “ghosted” both in the child’s
variables palette and in such stage watchers. “Shadowing” them
un-ghosts both the variable blob template in the palette and the
watcher onstage (if any). Deleting a shadowed variable once again
ghosts the watcher and the palette block template.
Delete a (shadowed) variable either via the “Delete a variable” button
in the IDE or using the new “Delete” block in the variables category
Merge branch 'master' into development2015-03-20T19:18:12ZGubolingubolin@fantasymail.de2015-03-20T19:18:12Zurn:sha1:c8de6a00e38e52bfc4b9b3a095cbcad1861687defixed #7432015-03-15T13:55:37ZJens Mönigjens@moenig.org2015-03-15T13:55:37Zurn:sha1:7f9fe78c56dbe26ccdcd8f6fd33cbb9766add474