Oleg Isonen
Oleg Isonen
same here, trying the workaround next
I like the idea to have a JSON DSL for constraints. Its actually mostly very readable (e.g. mongodb) and doesn't require expensive parsing! I think making layout constraints optional on...
All in all slalom is on a very good way to be a competitor to famo.us and I strongly believe this ideas will lead to a way better layout engine.
Even if building an editor it needs to produce some JSON dsl. Which can be parsed then. Also imperative API can still be required for more complex cases.
It would be cool to define some sort of plan/roadmap. Define crieria for physics engine and layout engine to fulfill most popular tasks. It should be someting like this 1....
This is a very big vision mate :)
What about actually more mongodb like JSON syntax: instead of ``` "xyz.left == 0" {'xyz.left': {$eq: 0}} "width == scaleBox.right - scaleBox.left" {width: {$eq: { $subtruct: ['scaleBox.right', 'scaleBox.left'] }}} ```...
Its like sql queries vs. mongodb queries. For me mongodb queries won.
Just looked at what pegjs has generated: 1900LOC 58KB ... with JSON DSL you will get it way way smaller and faster.
I think in mongo the win is because you a building the query using objects instead of strings, it makes it cleaner and less issues with escaping. But you might...