First I want to say that for the most part it is a pleasure to develop for Rhino! I’ve learned a lot with the examples you provide in the wiki and the Rhinocommon SDK is quite useful.
I would also like to see the SDK documentation completed as there are missing descriptions all over the place. Also, adding code examples as you have in the Rhinoscript help would be great. I know there are some in there, but would be great for this to exist in all documented elements.
I also noticed that the Event Model is pretty loose. For example, EndOpenDocument fires several times as the document is opening. Should this not fire once when the document is actually opened and finished loading any resources? I eventually got around the issue waiting for Rhino to become Idle, but I wonder if the EndOpenDocument event should be fired so many times for a reason?
Finally, I would like to request some information on licensing and the best practices, or options out there for plugin licensing. I know that this has implications beyond Rhino, but as tied to Rhino, it would be good to know what our options are (for those of us who have never touched upon the subject). What are the devices that facilitate licensing (Zoo vs license key vs license server?).
RhinoCommon has come a long way since the old SDK, and its fantastic. But I agree with @fraguada about completing the SDK documentation,
I also agree with @menno about creating two types of documentation, one for entry level, and one for advanced topics, in multiple languages (C#, .Net, Python, etc). Having it consolidated in one location will make it easy to search for solutions. I travel frequently and it would be nice for users to have the ability to download offline documentation as well.
a starting kit it’s a good thing but, because the language, I would prefer a proper course taken in person with real teacher. Maybe because I am a teacher…
I think with a teacher you could get more information, more “shade”.
I started the rpython 101 and never taken the end. I’m still missing lot of concept also if I read it more than 5 time. (maybe I need just an English course!?!?)
Ps: just asked to Steve how to organize a course in Italy
Starting with Rhino-Development, Pick the right environment:
I think many user out there would be happy to have an easy to understand comparison of rhinoscript, rhinophyton, .net, rhinocommon, developing grasshopper-plug-ins, c++ plug-ins, commandline-scripts…
maybe a simple table with: programming-pre-Knowledge-Level, Performance, complexity of user-interaction / possibility of GUI, lerning-curve, where to start, limitations (Windows, Mac, Rhino 4,5,32bit,64bit,visual studio express or 2010…)
examples examples examples, but nicely accessible:
the rhinoscript101 is great, the examples in the rhinoscript-documentation too. I think for rhinoCommon a nice collection of examples would be great. To start learning: maybe for 3 or 5 scenarios (create geometry, modify geometry, organise the document, handle attributes, user-interaction, export); for each scenarios 2 or 3 examples.
i really would love to have a better example-search, maybe by keywords (similar to scenarios, searchable by used classes/functions
a vice-versa connection between samples and documentation
And please improve the online-documentation search function, or provide a documentation on how to advance search. AND,NOR,*Placeholder. At the moment “userstring” will not find "GetUserStrings
to make this forum a solution-database, a more stackoverflow - mentality / function would be great, best answer, mark as solved, keywords
clean up all the different places where developer-information is distributed…
Some documentation on the coercing functions would be fantastic, there are still RS methods that behave differently in PY and GHPY. Guide for best practices would also be nice. And it would be great to have a future development direction insight. Like what is the future of the *.ghpy container? Only R6?