Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

moving towards web components #21

Closed
forresto opened this issue May 23, 2013 · 3 comments
Closed

moving towards web components #21

forresto opened this issue May 23, 2013 · 3 comments

Comments

@forresto
Copy link
Member

Things to design:

  1. how to expose i/o ports to graphing ui?
  2. attributes: number, string, boolean types?
  3. on-demand element loading

@bergie

@forresto
Copy link
Member Author

@forresto
Copy link
Member Author

forresto commented Oct 1, 2013

Making forresto/dataflow-prototyping#1 in a day has me excited about rearchitecting Dataflow. Issues like noflo/noflo-ui#14 that are specific to noflo will be easier to build closer to noflo. We can build the visualization of the graph directly with Object.observe, which should alleviate syncing issues. Current cards will be easy to port.

So the question: if we are close enough to a usable Dataflow now, I think we should get it there to help us bootstrap this next version. Can we prioritize those issues?

@bergie
Copy link
Contributor

bergie commented Feb 7, 2014

The Web Components implementation is at https://github.com/the-grid/the-graph

@bergie bergie closed this as completed Feb 7, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants