Github user corneadoug commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/27#issuecomment-90083040
I don't think that binding from angular to scala (angularWatch) is really
necessary, the binding would be most of the time the other way around, from
data to visualization.
Also saving the scope values on the Zeppelin context, is having multiple
unwanted effects (If I'm right): All of the Zeppelin context is sent back with
the angular interpreter result. Considering this also works cross-notebooks, we
can imagine the effect of doing a binding of a query result per notebook on all
angular interpreter response, also that result would be saved in the notebook.
This is a cool demo playing with scope and allowing data sharing between
interpreters, but without really working on allowing user to build angular
code, it is not doing much more than what could be achieved with a println that
would insert its data inside of html tags and add scripts tags for some
javascript code.
However it's nice to be able to show people what could be possible with the
idea of rich gui through angular
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
