Gridifier was designed specially for use with Backbone/Angular/React. We were using Backbone for our apps, but we will definitely look how to sync it with Angular/React. It was too heavy BTW - so the most logical step was to rewrite it completely at first, and after that start creating tutorials+codepens.
React operates completely differently from Backbone and Angular. I've looked only briefly at your code, but it looks like it operates directly on the DOM, which is not going to work with React.
Hmmm, I haven't tried React yet. Yeah, now it operates directly on the DOM, but all functions for DOM manipulation are located in separate class, so maybe we will try hook them somehow. Looked at React docs really quickly, it seems they have been abstracted away DOM manipulation to prevent unnecessary browser reflow/recalc ops. So, I can't predict now how easily it will be to sync it with React.(we will try to do it)
Actually, the virtual DOM isn't to prevent unnecessary operations, it's to ensure consistency. State transitions cause a render, which builds the virtual DOM (for each component) from scratch, ensuring that the same state always results in the same rendering output. This is different from, say, Backbone, where you create or modify individual DOM elements, and this logic is typically spread out across many functions.
"Any use of Gridifier for a commercial purpose is subject to and requires a commercial license. With commercial license GPLv3 license terms are not used. Instead of that, terms described on developer license page are applyied."
That means, that if product is being used for commercial purposes, GPLv3 license rules are not applied.
> That means, that if product is being used for commercial purposes, GPLv3 license rules are not applied.
Except GPL section 7 says I can ignore your non-commercial restriction. If you want to restrict commercial use, you must pick a different license. GPL won't work.
