{"action":"created","issue":{"url":"https://api.github.com/repos/Sverchok/SverchokRedux/issues/5","labels_url":"https://api.github.com/repos/Sverchok/SverchokRedux/issues/5/labels{/name}","comments_url":"https://api.github.com/repos/Sverchok/SverchokRedux/issues/5/comments","events_url":"https://api.github.com/repos/Sverchok/SverchokRedux/issues/5/events","html_url":"https://github.com/Sverchok/SverchokRedux/issues/5","id":90064323,"number":5,"title":"Introspection for all nodes from day 1","user":{"login":"zeffii","id":619340,"avatar_url":"https://avatars.githubusercontent.com/u/619340?v=3","gravatar_id":"","url":"https://api.github.com/users/zeffii","html_url":"https://github.com/zeffii","followers_url":"https://api.github.com/users/zeffii/followers","following_url":"https://api.github.com/users/zeffii/following{/other_user}","gists_url":"https://api.github.com/users/zeffii/gists{/gist_id}","starred_url":"https://api.github.com/users/zeffii/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zeffii/subscriptions","organizations_url":"https://api.github.com/users/zeffii/orgs","repos_url":"https://api.github.com/users/zeffii/repos","events_url":"https://api.github.com/users/zeffii/events{/privacy}","received_events_url":"https://api.github.com/users/zeffii/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":14,"created_at":"2015-06-22T10:33:11Z","updated_at":"2015-06-24T06:20:54Z","closed_at":null,"body":"I think this has been mentioned, but i'd like to develop the idea to be positive it is a first class piece of the new puzzle.\r\n\r\nPart of the problem with serializing the node tree to json was due to inconsistencies in how we described nodes, but also down to a slightly 'sparse' pyNodes api. Prior to writing the .json I/O we didn't know or worry about being able to query all params easily, and didn't need to enforce strict param conventions. We realized that the pyNodes API does not by default give a handy representation of the Node or the Tree. (if it does... we didn't find it)\r\n\r\nThis means the .json IO was/is a bit convoluted and more verbose than the concept requires, it can be simpler and I think we know how to approach it now.\r\n\r\nBecause some nodes have multiple states and dynamic sockets, we should be able to easily ask the node its _state_ and sockets and get a descriptor back (json?). We should also be able to set the entire state (sockets, values, enums...location..whatever) from the same json.\r\n\r\nThis would shift the clumsy code out of the IO and make it part of the node superclass.\r\n"},"comment":{"url":"https://api.github.com/repos/Sverchok/SverchokRedux/issues/comments/114744714","html_url":"https://github.com/Sverchok/SverchokRedux/issues/5#issuecomment-114744714","issue_url":"https://api.github.com/repos/Sverchok/SverchokRedux/issues/5","id":114744714,"user":{"login":"zeffii","id":619340,"avatar_url":"https://avatars.githubusercontent.com/u/619340?v=3","gravatar_id":"","url":"https://api.github.com/users/zeffii","html_url":"https://github.com/zeffii","followers_url":"https://api.github.com/users/zeffii/followers","following_url":"https://api.github.com/users/zeffii/following{/other_user}","gists_url":"https://api.github.com/users/zeffii/gists{/gist_id}","starred_url":"https://api.github.com/users/zeffii/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zeffii/subscriptions","organizations_url":"https://api.github.com/users/zeffii/orgs","repos_url":"https://api.github.com/users/zeffii/repos","events_url":"https://api.github.com/users/zeffii/events{/privacy}","received_events_url":"https://api.github.com/users/zeffii/received_events","type":"User","site_admin":false},"created_at":"2015-06-24T06:20:54Z","updated_at":"2015-06-24T06:20:54Z","body":"Additional reasons for Introspection, the SvStethoscope, or print debugger all need to be able to acquire node data and be able to show selections of it (another good reason to have something like np_Mesh with the ability to describe how a mesh in a flat or partially nested way)"}}