{"issue":{"title":"Documentation is Unclear","user":{"login":"blacatena","id":508059,"url":"https://api.github.com/users/blacatena","avatar_url":"https://secure.gravatar.com/avatar/d80f076f472772657ca5618727778ca2?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"d80f076f472772657ca5618727778ca2"},"created_at":"2011-12-29T16:55:25Z","milestone":null,"labels":[],"state":"open","updated_at":"2011-12-29T16:55:25Z","id":2680810,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"closed_at":null,"html_url":"https://github.com/vakata/jstree/issues/157","body":"I'm a wiz at everything who's been programming computers for 32 years, and I am struggling with jstree, only because the documentation is horrific.  It looks good at first, but a million things are implied without either being spelled out, or providing easy-to-sort-out examples.  This is further complicated by the older version of jstree that seems to have had major differences, so examples with that only lend more confusion.\r\n\r\nFor example, in the Types plugin you explain how to define the types, but not how to assign a type to a node (which I got working by setting an attr.rel attribute to the type).\r\n\r\nIn the JSON plugin you give two completely different examples with the same data distributed among different attributes (metadata, attr, title, id) with no rhyme, reason, or explanation.\r\n\r\nIn the UI plugin you demonstrate how to do things like the \"create\" operation, but that name is not the same as the create_node function, yet I can nowhere find a mapping of operation names to function names, or even a list of the valid operations.\r\n\r\nThe most obvious things one would want to do are to programmatically create and select nodes, and yet it's taken me hours to figure this all out.\r\n\r\nI would strongly suggest:\r\n\r\n1) A clearly defined list of all options (e.g. data elements and what they actually mean) for everything\r\n\r\n2) Consistency among simple examples (don't load the tree in the HTML in the page itself for one plugin, then JSON in the tree creation for another, etc.).  It's good to have a variety of things, but when there are too many all intermixed it's impossible for a beginner to sort out the reasons for the differences (i.e .what is relevant and what is not).\r\n\r\n3) A \"recipes\" page with the things people might most often do -- but isolated to just the subject under discussion, without complicating it with other techniques at the same time","number":157,"url":"https://api.github.com/repos/vakata/jstree/issues/157","comments":0,"assignee":null},"action":"opened"}