- last edited on by
Daniel Kassai
Where is the place that I can propose the editing for manuals ?
For instance, right now, when revising COOR, COOR{2}, COOR{3} GDL commands, there was no mentioning that the these take effect after defining a specific body.
For instance, right now, when revising COOR, COOR{2}, COOR{3} GDL commands, there was no mentioning that the these take effect after defining a specific body.
@Ralph Wessel
Just make a comparison between McNeels Rhino's API and that of ArchiCAD.
There is a more people and companies that already are using McNeel's Rhino API than that of ArchiCAD's, and by this way you may encourage more people to adopt it, it's something like throwing the ball over their wall.
And about the size, don't forget that the size of ArchiCAD's user manual is 600+ pages
Just make a comparison between McNeels Rhino's API and that of ArchiCAD.
There is a more people and companies that already are using McNeel's Rhino API than that of ArchiCAD's, and by this way you may encourage more people to adopt it, it's something like throwing the ball over their wall.
And about the size, don't forget that the size of ArchiCAD's user manual is 600+ pages
I don't prefer pdfs over current approach, but at least users will interpret this move as an invitation to use it
@Joe Putnam
I would like to thank you for explaining the part of the API in relation to Rhino users, you have just expressed my idea in words that I didn't know how to express. And about the part on whether or not to embrace C#, well I don't know what to think about since I don't have the tools nor the means to form an objective opinion.
Anyway I want to add my point of view about that matter from a different perspective:
It was my owe of Grasshopper that have pushed me to get interested in Python and C#, and it's Rhino's API that have convinced me to invest in learning the use C# and Python, and it was the tutorials made by experts/not-that-experts that talked in a language I can understand that have maintained me on the track of the learning curve, not just some info stacking on a web-page.
But most important Graphisoft, just don't recreate past error in new ways and in new dates, for example, are you aware that until today the most important information source to learn GDL, is "The GDL Cookbook" written by David Nicolson-Cole, a 20 years old book ????!!!! and until today I see novice and expert advice who want to learn to read that book in many forums and groups .... and you know why, because it was written in a language a normal non-tech savy can read and understand, and it successfully lay down a foundation for users to self improvement.
By the way, GDL should be defended as the excellent BIM object creation tool, not that of Revit Families.
I would like to thank you for explaining the part of the API in relation to Rhino users, you have just expressed my idea in words that I didn't know how to express. And about the part on whether or not to embrace C#, well I don't know what to think about since I don't have the tools nor the means to form an objective opinion.
Anyway I want to add my point of view about that matter from a different perspective:
It was my owe of Grasshopper that have pushed me to get interested in Python and C#, and it's Rhino's API that have convinced me to invest in learning the use C# and Python, and it was the tutorials made by experts/not-that-experts that talked in a language I can understand that have maintained me on the track of the learning curve, not just some info stacking on a web-page.
But most important Graphisoft, just don't recreate past error in new ways and in new dates, for example, are you aware that until today the most important information source to learn GDL, is "The GDL Cookbook" written by David Nicolson-Cole, a 20 years old book ????!!!! and until today I see novice and expert advice who want to learn to read that book in many forums and groups .... and you know why, because it was written in a language a normal non-tech savy can read and understand, and it successfully lay down a foundation for users to self improvement.
By the way, GDL should be defended as the excellent BIM object creation tool, not that of Revit Families.
@Joe Putnam
By the way @Joe, I was thinking in another way, except for MEP capabilities that Revit families have, GDL lacks nothing but few notches, like the ability to save textures/shaders, IFC data, etc, and that the end user would think about nothing who ever s/he, or what ever was his/er job.
Need a nice super 3D model for rendering, same GDL, only a 2D representation you got that, in other words, GDL must be seen as the standard BIM object exchange container, unless GS have already made the next generation that we know nothing about !!
But most important Graphisoft, just don't recreate past error in new ways and in new dates, for example, are you aware that until today the most important information source to learn GDL, is "The GDL Cookbook" written by David Nicolson-Cole, a 20 years old book ????!!!!The first GDL manual I have ever read was that of ArchiCAD 6 in 2000, and after few year I got my hands on that of David, but what I meant with that quote is that these two manuals were made to encourage people to use/learn GDL, by using simple language that they can understand and with ever bit they raised the bar a little bit, so wen you finish reading them, you already know enough not only to create new stuff but also to know when/where/how you ask the question you need even if that means you raise the bar quiet high for your capacity at the time.
By the way @Joe, I was thinking in another way, except for MEP capabilities that Revit families have, GDL lacks nothing but few notches, like the ability to save textures/shaders, IFC data, etc, and that the end user would think about nothing who ever s/he, or what ever was his/er job.
Need a nice super 3D model for rendering, same GDL, only a 2D representation you got that, in other words, GDL must be seen as the standard BIM object exchange container, unless GS have already made the next generation that we know nothing about !!
By the way Graphisoft,
I also must mention that I feel puzzled for finding in Rhino's Discourse forums, some ArchiCAD users asking questions about problems they face when working with ArchiCAD-Grasshopper connection, that is more related to ArchiCAD than that of Grasshopper ... I think you should make someone pay those users a visit from time to time to answer their questions and create a presence in the Rhino community.
I also must mention that I feel puzzled for finding in Rhino's Discourse forums, some ArchiCAD users asking questions about problems they face when working with ArchiCAD-Grasshopper connection, that is more related to ArchiCAD than that of Grasshopper ... I think you should make someone pay those users a visit from time to time to answer their questions and create a presence in the Rhino community.
This statement about "LIBRARYGLOBAL" should be included:
LIBRARYGLOBAL is a function that should be used in 2d and 3d to reach the parameter values of an MVO dialog, and change the object’s behaviour based on that. It should not be used in parameter script, and it does not make any effect on parameter values of placed objects.Source:
Didn't find the answer?
Check other topics in this Forum
Back to ForumRead the latest accepted solutions!
Accepted SolutionsStart a new conversation!
