vizorvr / patches Goto Github PK

Subtasks:
• Script

1. upload graph json
2. filebrowser highlights it
3. open it
4. gridfs blob url used instead of model url
5. reload
6. uses correct url

Make an Array plugin with dynamic number of ANY datatype inputs, and an index input that changes the current output value of the plugin.

inputs: index, 0, 1, 2, 3, ... 
outputs: output

Eg. feed in 8 images, and alternate between the images with index

It obviously can be done by "or", "equal" and "less than" plugins but than, why there are "and", "or" and "not" plugins while they can be assembled from "nand"s ?

Missing logic plugins:

• less than or equal
• more than or equal
• unequal
• almost equal/unequal with definable proximity

Make a way for debugging texture outputs in the graph

They used to be colored #c6ffc8 ... as noted in less.css:

.register {
background: #c6ffc8 !important;
}

For some reason this doesn't work at the moment.

Try publishing this graph for an example: http://create.vizor.io/fthr/webpage_2/edit

Refactor the structure and style for the menu bar (logo, file, play, user, and help buttons).

• Fix button heights
• Remove forced navbar and user-pulldown styling
  and fix Login and Signup button heights.

see example:
http://create.vizor.io/uucidl/draw_scaled_image/edit

In this sketch I have a texture fed into a graph that will render it to the framebuffer

After you load the sketch for the first time in your browser, and you press play, nothing is shown.
Press edit into the draw_image subgraph. You will see the texture resolution is read as 0x0
Now press stop and play again, the texture resolution is now 512x512 and the picture shows.

Uploads automatically and inserts (them into) the appropriate preset

Like Photoshop, Ableton Live, etc.

Highlight a group of nodes and make a subgraph out of them.

Allow "cables" to be selected with the mouse.

• Register plugins error because Node.deserialize() uses the guid as parent_graph (why?) given by Application.onPaste()
• (Sub)Graph plugin "Cannot read property 'node_uid' of undefined" on graph.js:249

Change the presets that use those plugins that use the viewport size (eg. Shadertoy preset) away from things like hardcoded viewport sizes (eg. Shadertoy preset)

for float it returns null

Reproduce:

1. press 8 to get a new image displayed, press play
2. cut the "load image from URL" from the root and paste it inside the image subgraph
3. connect the "load image from URL" instead of the input proxy
4. go to root, observe missing image.

no errors in the console.

When working on some graphs or tools for a certain amount of time, it is useful to keep track of assumptions and missing features. One way to do that already is to simply create annotations.
Vizor could help us out further by harvesting these special TODO annotations so they are listed in a project management box.
A format I have seen used is the following:

TODO(<name of collaborator>) we don't do this necessary feature for now because <this / that but> let's not forget about it when <something> happen

Having the name of the person tagged in this way allows to group these TODOs according to their owner.
It's easy to extend this system to other kind of tags like NOTEs with another prefix.
It would also be quite useful for these to be harvested from shader code as well, so as not to treat them like second class citizen.
With this feature, vizor would immediately gain a small yet pragmatic way of dealing with project management.

Allow these things to be activated in the URL itself.

• add way of addressing any node by path
• a way for Plugin's UI to report and react to changes in state/model
• a way for Graph and NodeUI to report changes in graph shape
• record changes into stack
• rollback changes from stack -> change graph structure, state by address, and notify UI

Build a number of test cases that can be executed quickly, as an intermediate step between unit tests and full-fledged browser integration tests.

• method of executing graphs headlessly (mock gl?)
• method of testing graph outputs (via parameterListeners?)
• implement test case graphs and expect results (a few fundamental system assertions)
• add as part of npm test

Allow filtering the file dialog contents with a search input

Apparent on this graph:

http://create.vizor.io/fthr/twisty-gradient-robots-3/edit

Load that, press play, and you're supposed to see a bunch of robots. Instead you only see the backround cube. Navigate to "Root" of the graph, and the robots appear.

This graph uses loops, and is quite CPU/GPU heavy. On graphs that are less heavy the problem isn't present, for example: http://create.vizor.io/kschzt/robot-in-a-castle/edit

These are the three most common plugins that are inserted into graphs, so they should have hotkeys for faster workflows.

Suggestions:
I for input proxy
O for output proxy
G for subgraph

Use case:
Hit G and the "Name new graph" dialog is opened. User puts in a name and the subgraph is created.
Hit I and a new input proxy with the default name (input-n) is created in the graph.
Hit O and a new output proxy with the default name is created in the graph.

This would be a useful feature to have to more easily make graphs more aligned, and more beautiful.

“Load More”-style

To reproduce:

1. new graph, press play
2. load the preset: mesh with camera material and light and transforms
3. go inside the mesh subgraph
4. load a plugin using the search box: mesh/null
5. disconnect the existing "cube" mesh from the mesh slot in "mesh" subgraph
6. connect the "null" plugin to that mesh slot
7. use a marquee to select the 3 orbit camera sliders
8. blue marquee square should now freeze on the edit canvas

Screenshots attached.

Most calls to XHR assume synchronous XHR is available, which causes load-time/initialization issues when it is not. Get rid of the ancient synchronous XHR calls.

After some mysterious combination on web browser window resizing create.vizor.io renders wider than web browser window causing horizontal scroll bar to be displayed.

Google Chrome version 39.0.2171.95 m

• replace msg() with a proper logging system (Tattletale.js?)
• report error stack traces somewhere (Papertrail?)
• send server logs too (winston + Papertrail?)

Signup isn't visible in Firefox

Just like proxies/registers/subgraphs. Since they are kind of special case. I'd use this color: #ffc6ee ...

Show mine, show all, newest first, oldest first

Editable in the node, instead of opening the modal

Two functions:

• marquee-select connections
• shift-marquee to add to selection

See this graph for replication: http://create.vizor.io/fthr/mousebutton/edit

Clicking mouse should give true bools.