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.

Sign up for GitHub

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

Jump to bottom

Interoperability with noflo-three #14

Open
automata opened this issue May 3, 2014 · 1 comment
Open

Interoperability with noflo-three #14

automata opened this issue May 3, 2014 · 1 comment
Labels
enhancement question

Comments

@automata
Copy link
Member

automata commented May 3, 2014

We are supposed to create 2d shapes using a WebGL render: http://jabtunes.com/labs/3d/vector/

Is this a valid use case?

canvas/MakeRectangle RECTANGLE -> ITEMS canvas/Fill
canvas/Fill FILL -> COMMANDS three/Draw

Or should we choose between the desired 2d/3d render on canvas/Draw? In this way we can go for canvas/MakeCube, right?
@forresto
Copy link
Member

forresto commented May 4, 2014

I'd go for a totally new three/ library with similar semantics. Maybe with just the components that would be different: MakePoint3D, Draw3D.

@automata automata changed the title Interoperability with node-three Interoperability with noflo-three May 7, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@automata @forresto