2021-05-2911:46 PM - last edited on 2021-09-1409:10 AM by Noemi Balogh
After long thinking on this subject I would like to hit the new Open Source GDL programming project on this forum. The idea to involve GDL developers worldwide to start building new, independent, international, non-commercial library for all. GDL technology has very strong potential and that is very important part why ArchiCAD as a CAD and BIM system is so unique.
Please read the initial statements of this project:
1. The project is running under the GNU GPL licence. It is based on GDL technology, but not limited by it. Any further translations to different programming languages or use in different CAD systems apart of ArchiCAD are welcomed. Additional C++ programming to improve use of the library parts by making special Add-Ons are welcomed too. 2. Anyone, who is taking part of the project, doing it by their free will and free of charge just following the desire to make BIM world better. Donations, investments and grants for developers are discussible and acceptable. 3. The objects must follow all official GDL standards (like GDL white paper) and Graphisoft recommendations. For example - I like to use uppercase in my GDL script for commands (because GDL manual shows all of them in uppercase). But as soon as GS recommends to use lowercase - my opinion or preferences are not valid. 4. Developed library parts must use standard GS variables names to have full compatibility with standard libraries, distributed with official ArchiCAD releases. As well - to use standard GDL subtypes, as soon as introducing new one is not necessary. 5. All library elements must be compatible with Grasshopper - means that most of calculations (that usually happens in Parameter script) shall happens in Master Script, because Grasshopper is not reading Parameter script. 6. Completed library element must be uploaded to BIMcomponents.com web-site for free access of ArchiCAD users worldwide. 7. Any modification to the library part code must be reflected into the versions text file (or log file), provided with the library element. 8. Library part must be truly international - means that they must have multi-language support. 9. Library objects must be not manufacturer-oriented but building element class-oriented with manufacturer support. For example - instead of having ACO drain element - to have rainwater drain element with possibility to choose ACO from manufacturers list. 10. There is no discussions about leadership of the project. Everyone is equal and differs only by experience - strongest are supporting weakest. I will try to manage this project as long as I can, also I'm willing to open some of my personal developments, but I do not pretend to be head of the project (even if this is my idea). 11. Anyone can be involved into any stage of library part development - starting from conceptual graphical schemes and algorithms ending by writing and re-writing actual scripts. 12. Any object must have textual / graphical description how to use it and YouTube video. The links to the manual must be implemented into the object User Interface. 13. Each object must have User Interface. 14. Common global variables names as for example from Add-Ons or MVO objects - matter of community decisions and consultancy with Graphisoft. After the decision is made - this subject is not discussable without serious technical reason. 15. Every GDL object must be written on as lowest ArchiCAD/GDL version as possible - as soon as needed features allowed to use the version. 16. Developing of the new object is starting by introducing your ideas in the post plus hand-drawn (or CAD drawn) sketches and logical (drawn) schemes. 17. This is not PARAM-O project. PARAM-O can be used as a temporary tool, but because of nature of scripts, generated by program automatically, must be reviewed and rewritten by human to achieve better performance and smaller size of script.
Hello. My name is Bektur, I am from Kyrgyzstan. Only complex objects are discussed and made here? What are the rules? I just for myself (because of an urgent need) began to create some library elements (Library Part Maker) such as a Car with dimensions (Box) for collision detection with engineering networks, and others. Are these welcomed here?
Now its possible to assign 3 different profile-manager-profiles to the 3 street-edges. In 2D, at an special GDL-scripted detailed corner-section-view, you can switch the profiles with editable hotspots. The z-hights in 2D now can be moved from its position with ed. hotspots to get a better readability.