Davide Della Casa
Davide Della Casa
...you could keep for example a list of the top n biggest opaque morphs (say, frames and rectangles) and check that case while you traverse the list. Note that in...
...so that it's not needed to fix them upon duplication in the updateReferences method. Maybe if the parent is passed in the arguments? Look of how that automatic fixing has...
the problem with buildAndConnectChildren: (@contents, @scrollBarSize, @sliderColor) -> @destroyAll() @children = [] is that you also kill wathever you attached afterwards such as handles… You need something like replaceChild().
choices = @target.colorSetters() The code for finding setters should be generic. It should look into the source code (and the source code of the superclasses) and it should be based...
I initially wanted to support menu duplication, as it seemed the right thing to do for orthogonality.I eventually also implemented draggability, pinnability, and cascading menus. Main commit changes here: https://github.com/davidedc/Zombie-Kernel-core/commit/e59cb53e996c716b4fa437091d5268436044bbc5...
morphic.js now counts 10471 lines and has passed the limit of what Github can handle to show diffs online. Also I found myself investigating a few times what the history...
in: `this.children.splice(0, null, aNode);` it seems like the spec-proper way to write it would be `this.children.splice(0, 0, aNode);` Now - it works just fine, but in all the specs I've...
This is correct, but I think it deserves a comment, because, say, it matters if one wants to implement a proper isEmpty routine (which I didn't, and costed me several...
looks like the current "destroy" implementations are non-recursive. One (or a few) nodes are severed from the tree. While this removes an entire branch from the world in terms of...
While in theory "turtles all the way down" systems should sort of self-test themselves with just basic usage, I found this not be true in practice (I don't know if...