babelsberg/babelsberg-js

Babelsberg/JS

For more information, please visit our gh-pages

This work is licensed under 3-clause BSD

Created under a grant from Hasso Plattner Institute

babelsberg-js's Issues

Dynamic scope for functions

Dynamic scope is lost for functions in constraints. For example, fabric.js defines methods on fabric.Point, and uses only new Point in those, because it is in scope. But when we interpret it, it's not in scope. Maybe we need a whole program translation (like the original lively debugger)

bower package for babelsberg.mini.prototype.js

Would be nice to have a bower package released for browser stacks.

stronger/weaker stays

Sometimes certain variables should stay stronger on its value than others. Adding a notion of strength for stay constraints would allow the user to specify this.

unconstraint is not restoring the accessors properly

I noticed that when you unconstrain a Slider, it would no longer work afterwards. I have found out that the unconstrain function is not properly restoring the old accessors, probably due to a typo.

DeltaBlue throws no error

DeltaBlue throws currently no error, if some constraints are not satisfiable. Therefore, DeltaBlue does not support onError attributes.

Source Code Transformation for Unified Notation

I pushed the discussed notation on the unified-notation branch.

Constraints can now be specified using the predicate function followed by always, trigger or others. COP Layer also support this method and scope the respective constraints, e.g.:

layer.predicate(function() {
  return temperature.celsius * 1.8 == temperature.fahrenheit - 32;
}, {
  ctx: {
    temperature: temperature
  }
}).always({ solver: new ClSimplexSolver() });

We need a source code transformation to automatically generate the ctx object in the options as second parameter of the predicate function, if missing. The first argument should remain unchanged.

Any opinions?

Cassowary.js

Howdy, this is awesomely ambitious!

I'm the creator of http://gridstylesheets.org/ and a contributor to https://github.com/slightlyoff/cassowary.js, wondering if you guys considered that Cassowary port & reasons for / against?

Watch for function changes

Right now, when I recompile a function that was used in a constraint, that constraint is not recalculated

verbose flag

As the number of debug prints grows, a flag to hide them all would be preferable.

The question is, whether to assign this flag to every constraint, to each solver instance individually or to the single bbb instance.

fabric.js layout example question

The example works fine online. I tried to make work it on my computer without installing node.js/lively-kernel. I downloaded layout.html, fabric.js and layout.js. Prototype.js source is unchanged. I changed the source files for babelsberg and solvers to point to live-kernel.org as in the online version, but the example did not work. It looks it needed lively-kernel runtime to work.

Either there are restrictions to get data from lively-kernel.org as source or I do not understand exactly how it works?

More info about bundled z3.js

Hi,

I'm trying to compile z3 with emscripten to use it in another project.

I started with your version of z3.emscripten.js - and it worked fine. However, when I later tried to build my own version of z3 (that supports soft constraints) - it built fine but segfaults on certain queries :( Your original version (based on 4.3.1 as far as I can tell) works fine though, although it doesn't support assert-soft that was introduced in v4.4.1.

Do you mind providing more information on which upstream commit the bundled z3.js is based and which emscripten configuration was used to build it so I can have a starting point of a working build and see where things went wrong?