Todo (zeffii)

[zeffii]

I'm drawing up this list to keep track of things I want to complete before other random stuff.

• [x] Node to turn (verts+edgpol) into dashed edges, creating new verts+edges (dropping polys)
  • [x] exists as 'dashed_edges.py' in node_scripts/zeffii/
  • [ ] use a string representation, or pick from dropdown.
  • [ ] use slider for scale (scale is relative to world)
  • 
• [ ] Script Node (Text Editor addon) to generate clone of current as current_file_CLONE_HHMM
  • This would enable something like a versioning system, especially useful for code experiments which may span several similar files sequentially or parallel.

(low priority)

• [ ] profile node implement even spread on bezier spline using vector interpolation, this makes the node dependent on numpy. decide.
• [x] update Intersect Edges
  • [x] add tolerance setting to Intersect Edges
  • [ ] add "touching" boolean (currently intersections are limited to X and not T )

(on hold, partially implemented or implemented but not committed)

• [ ] 3d cursor node
• [x] Grease Pencil In node
  • [x] select from all available grease pencil layers / strokes in the current .blend
  • [ ] After selection cache immediately?
• [x] Empty Node https://github.com/nortikin/sverchok/issues/188
• [x] finish 'inset specials' node (now a branch)
  • [x] inset amount (relative, but absolute should be possible in some sense)
  • [x] inner face (keep / remove)
  • [ ] axis vector + distance scalar to push inset vertices long term
• [x] 3d L-system Node (I implemented this as a nodescript, elfnor also introduced an alternative implementation as a proper Node)
• [ ] plot stuff like http://stackoverflow.com/a/4687582/1243487

done, presently in beta

• [x] dump current node_tree to json, and generate from json.
• [x] Viewer Draw Extended
• [x] rounded rect using phymec's 0.3 code
• [x] Instancer Node https://github.com/nortikin/sverchok/issues/208
• [x] barely beta stethoscope This node shouldn't go on as beta for too long. The main reason it's not on the fast-track to node-proper is because I'm not sure how to format the data usefully. With DebugPrint node it's easy: "just spit out the data". But with BGL render it needs to be formatted and rounded so as not to overwhelm user or processor. The problem is not displaying the data, it's how to display the data in an abbreviated form in a meaningful way.
• [x] Eval Node
  • [x] add =eval_text (function, internal file, update)
  • [x] add =read_text (internal_file)

done

• [x] Simple 2pt bezier node (single segment)
• [x] Simple 3pt arc node (single segment)
• [x] Vector Math 2 Node, add Scalar vector * x and vector * 1/x .
  • this node is essentially finished, but I will be tested for another while before it replaces the original vector math node.
  • this node is also getting performance boosts.
• [x] SN should have an example about how to refresh imports I didn't figure out until a few minutes ago that scripted node could load my own local python modules. This means i can offload some work to code written in my favourite Text Editor (Sublime) https://github.com/nortikin/sverchok/issues/85#issuecomment-44269679
• [x] make ui_operator example that deals with incoming socket data
• [x] Bmesh view revisit
  • [x] ....pick new random mesh name
  • [x] ....select all generated meshes
  • [x] ....pick base material
• [x] Gtext node https://gist.github.com/zeffii/063763a6b5fc64544f4f
  • [x] create bounds dict to map the width of each glyph
  • [x] use spacing param to space relative to this.
  • [x] prelim typeface
  • [x] prelim drawing code
  • [ ] tokenizer for symbols (maybe \d = degree, \D = diameter, \r = radius ..etc)
  • [x] transplant code into a donor node
  • [x] make latin+cyrillic+extras remap.
  • [x] build primary latin+cyrillic+extras font face
• [x] intersect edges node doesn't remove original edges, it should
• [x] fix generic node_script input, right now nested listed are not handled appropriately
• [x] debug print node ( printing incoming sockets directly to stdout, like viewer Text but without expectations of incoming data formatting ) done by @ly29 not commited yet
• [x] fix default node values for ScriptNode
• [x] update index viewer
  • add edges + faces to index viewer
• [x] make kb shortcut for TextEditor to convert sv_main defaults to a new in_scokets declaration def sv_main(verts=[], dist=1.1, strength=1.0): can easily be parsed and turned into in_sockets list.
• [x] ScriptNode to get regular import styles, ie: place imports before def sv_main(). having a new import per iteration was a bad idea from the start
• [x] ScriptNode to allow 'faux' operator buttons, to action functions.
• [x] Implement user defined background+vert+edge+face colours in the N panel (6 colours is too clunky for node UI)

[zeffii]

http://blenderpython.tumblr.com/post/85306987769/sverchok-examples-based-on-geometrydaily

[nortikin]

who is author of blog? I seee, it is you, thanks!!!!!! ))

[zeffii]

@nortikin, maybe you would like to contribute a few geomtrydaily Node-ifications? I see now that I have to make a vertex-color node. http://blenderscripting.blogspot.com/search?q=vertex+colors

[nortikin]

now i some busy, making interiors design and exterior + one album finished just now. I have todo, that i must do, and want prepare video teaser.

I'll make materials socket first (or implement just popup property in bakery and viewer nodes) to make materials... and vertex color too.

[ly29]

Color+material socket. I would like generic socket for input

[nortikin]

strings - is generic i think. at least, i made it as universal.

[zeffii]

it might be time to think about other datatypes, structs even..

[nortikin]

datatype aside list? what should contain new type? name of data? maybe information of data structure to stop seeking of levelsoflists and stop checking for correction of data? or to leave it as is, only give new sockets for materials? we could out any data from material and vertex color to vertex group and armature binding. and splines and nurbs. that all will take so huge diversity of sockets, that we realy needs to rethink sockets type and consider smart solution on this. It have to be united somehow. would it be bpy_collectin_property or just dictionary? dictionary easy to manage, i think. never worked with collection propertyes and don't know how they manage lists-dicts. realy, maybe next socket should have alltogather ertices info about vertices? so we could create dictionary that will give corresponding values - dicts in dict or dicts in list or list in dicts how to manage materials to assign materials to vertices, to assign vertex colors to vertices?

{ 'materials': {'Glass': [1,2,3,6,7,8],... }, 'vertexcolors': {[254,254,0]:[...],...} } or something like that? it is for one object. before baking all data go to standart view in 3 levels, so it have to work [{{'':[]}}]

for vertices nothing have to be changed, as it is main socket type. And for matrices But for edges/pols there can be such: [{'curve':[1,2,0],'mesh':[0,1]}] etc

from curve and mesh values are the same as now - nasty list [[[]]] and more nested than {'curve':[],'curve_structure':{120:3}} where 120:3 is 120 length of curves count, and 3 - length of each curve. that way object contains all the data in dictionary...

[zeffii]

maybe information of data structure to stop seeking of levelsoflists and stop checking for correction of data?

exactly, this would allow us to provide the information that the reading node needs to process the input. All good questions.

I would like to experiment with specialized containers, instead of the general python lists/dicts -- but because I have no experience with this yet I don't have anything to show at the moment.

[nortikin]

we seeked in bpy.props - there is no solution for us. maybe we could create own bpy.props.Sverchok somehow... But it is hard, i guess and need C#

[ly29]

A class structure for more complex data types like curves would be a good idea I think, which doesn't make sense to manipulate on an atomic level like mesh data does. For meshes bmesh is the right solution. This would be good because the data atoms would become molecules. Which supports some general things for them like make a line for draw drawing, converting to mesh etc. But as long as we stay in python using list, tuple and dict etc makes sense because they are very quick and flexible.

Line
Polyline
Spline
Bezier

Long term the backend should move into c code inside of blender or something for speed. But right now I think an addon in python is a good idea.

[ly29]

Debug print node https://gist.github.com/ly29/accb020195c4de266f3d

[zeffii]

nifty little node @ly29 ! will have a look at this later!

[ly29]

Updated to use draw button ext for individual sockets

[zeffii]

http://www.cs.cmu.edu/~quake/triangle.demo.html

[zeffii]

ideally mathutils would have something like

mathutils.triangulate_polygon(vertlist, edgelist):
    # magic in C
    return vertlist, edgelist

[zeffii]

oh... it does! http://www.blender.org/documentation/blender_python_api_2_70_release/mathutils.geometry.html?highlight=mathutils#mathutils.geometry.tessellate_polygon

[ly29]

It does kind of what you want. If we sorted the faces for rendering we could to that for all faces with length larger than 4. #157

                if len(pol)>4:
                    glBegin(GL_TRIANGLES)
                    v=[data_vector[k][i] for i in pol]
                    tess_poly=mathutils.geometry.tessellate_polygon([v])
                    for a,b,c in tess_poly:
                        glVertex3f(*(data_matrix[i]*v[a]))
                        glVertex3f(*(data_matrix[i]*v[b]))
                        glVertex3f(*(data_matrix[i]*v[c]))

[ly29]

What is cool is that it takes many lists at the same time so it could be quite efficient I think.

[ly29]

We dont have to sort, just filter make vert lists based on index and now we support concave polygons.

[zeffii]

perhaps for mkII I'll surpress the inner triangle edge drawing, or make it optional but that may slow things down.

[ly29]

Added the debug node but not in the menu yet.

[zeffii]

updated todo, node_Script doesn't deal with nested lists.

[zeffii]

a little experiment

[enzyme69]

what a PRO! instant sexy = Grease in Sverchok :)

[zeffii]

I've opened it to all grease pencil layers in the .blend

I think for now I will just allow cache-ing, not update per frame (as each grease pencil layer can have as many frames as you'd want -- And I don't want to prevent any crazy user from doing that, but it won't be implemented yet).

with options

• normalize. (not added to ui )
• simplify (optimize)

Where it makes sense to normalize first, then simplify (for 'optimal' verts to shape ratio )

[zeffii]

https://gist.github.com/zeffii/9b8ff420afad133e874d

[zeffii]

i'm not sure it makes sense to add normalize and simplify as internal options, as separate nodes they could be used for a lot of other things. Time for a geometry_util.py so we can at least use shared code for these things.

[zeffii]

this might benefit from a 'close strokes where first and last point are within a certain distance from eachother` --

[zeffii]

@enzyme69 GreasePencil node is probably not as useful as it first seemed -- at least I am now less convinced of its usefulness after prototyping it. The main reason is that it seems GP strokes usually need to be cleaned up manually before you import them. I've seen you do it in the video and i've found myself doing it while testing.

On the other hand, it does provide geometry quickly. Useful for testing Simplify, Smoothing and Normalize code. The exercise hasn't been entirely pointless for that reason.

[enzyme69]

Let's just add it with Beta tag :)

[zeffii]

I updated the gist a few times, the caching doesn't really work. If a grease pencil stroke is removed from the blend, and you reload the blend the cache is invalidated.

[enzyme69]

Grease seems needs always to have the backup Curve created.

[zeffii]

found and narrowing down spline normalize bug, using greasepencil to fake data.

[enzyme69]

Zeff, I just found out this option for Grease Pencil to Smooth and Simplify each stroke automatically.

If there is SV Grease Pencil node, we can probably have this Smooth and Simplify ON at all time.

[zeffii]

Even if I added the greasepencil in node to trunk it would provide no functionality that object _ in doesn't already allow. I learned a few things by coding it so it's not a total waste of my time

[enzyme69]

It might ... say if I erase the Grease, it will auto update.

At the moment, I always need to convert Grease to Curve then to Mesh.

[zeffii]

Then it makes more sense to implement Curve reading in Objects_in, or dedicated Curve In node

[enzyme69]

I still think Grease has something special about it. Easy to erase.

However, Curve In node will be interesting. Mesh convert on the fly.

[zeffii]

I already have Curve to mesh code, written by Brecht http://blender.stackexchange.com/questions/688/getting-the-list-of-points-that-describe-a-curve-without-converting-to-mesh

[enzyme69]

What... You should have told me earlier. Been requesting such feature for years. I will try tomorrow morning... zzz

SN please or SV node please :)

[nortikin]

object in could handle it. i implemented group input there. and think of adaptive sockets out for different objects. And that is why we need continue conversation on data in sverchok. {curves_knots:[], curves_handlersL=[], curves_handlersR=[]} where curve defined by first list, than if there no automatic handle type, it defines it coordinates as tangent.

[zeffii]

i'm in favour or starting a curve_utils.py to store these functions, to take a curve object inspect it and return edgs, vers, pols, mtrx -- great for Object_in node I agree.

[nortikin]

yes, we can make functions for lofting? without nurbs. there is looptools where loft realised, and i guess, we could make couple of functions -

1. to devide curves on equal parts - node to manipulate curves or even to make curves from vertices. i.e. we have some line, that is only knots for curve. but this takes vertices, interpolate them as they are knots of curve and output finally series of vertices defined by user count of subdivision. We can start from handles type 'automatic' to avoid defining handles and to left it for next release with inner sverchok data modifications
2. to connect (line connections, but with subdivisions and smoothing) with polygons or without them (in my todo list this modification)

[zeffii]

I think so. Started a different thread for this https://github.com/nortikin/sverchok/issues/198

[zeffii]

http://bl.ocks.org/mbostock/dbb02448b0f93e4c82c3

this is one reason I wanted to get node.js in scripted node

[enzyme69]

I really like that kind of step by step interactive visualization of programming! It's like running the program in slow motion that our brain can understand.

[zeffii]

I have a massive backlog of scripts written to test stuff (this list will grow as I remember where to find them)

• vertex_colour_from_polygon_size.py

[zeffii]

    # works on shaded
    vectorlight = bpy.context.user_preferences.system.solid_lights[0].direction

[nortikin]

that is right