cavalion-blocks
Advanced tools
Comparing version 0.9.30 to 0.9.31
18
.md
@@ -17,5 +17,21 @@ * [CHANGELOG.md]() - [README.md]() | ||
* [bro](src/cavalion-blocks/:/) - [veldapps](src/cavalion-blocks/:/) - [veldoffice](src/cavalion-blocks/:/) - [lost+found](src/cavalion-blocks/:/) | ||
* [prototypes/](src/:) | ||
* **[prototypes/](src/:)** | ||
* [Container](src/prototypes/:.js) [.glassy](src/prototypes/Container:.js) [.dragable](src/prototypes/Container:.js) [.sizeable](src/prototypes/Container:.js) | ||
# `2022/04/17` Container.zoomy needs to emerge | ||
* Let's extract zoom-related code from `glassy` to another class: `zoomy` | ||
* Does `Container.glassy` get loaded for `devtools/Iframe.glassy` as well? | ||
# `2022/04/16` Container.glassy needs a wrapper | ||
So, since {header}, here's a question for-ya: How to override the default behaviour of a Container so that two DOM-node are maintained, a wrapper/border and a content? | ||
* The following methods have proven to be useful overriding: | ||
* [vcl/Control.prototype.getClientNode()](lib:) | ||
* [vcl/Control.prototype.initializeNodes()](lib:) | ||
## Vars | ||
* **zoomC** - zoom correction factor in order to correct for retina displays |
@@ -0,1 +1,5 @@ | ||
### 2022/04/17 - 0.9.31 | ||
* Introducing [Container.glassy](/Library/cavalion-blocks/prototypes/:.js) | ||
### 2022/04/15 - 0.9.30 | ||
@@ -2,0 +6,0 @@ |
{ | ||
"name": "cavalion-blocks", | ||
"version": "0.9.30", | ||
"version": "0.9.31", | ||
"description": "`blocks-dot-js` `[].js`", | ||
@@ -5,0 +5,0 @@ "main": "README.js", |
91944
51
2235