The Global Archicad Community

Stay informed. Get help. Share your knowledge.

Topics specific to the scripting and development of Library Parts and Libraries using Param-O or the Geometric Description Language – GDL. (Example: How do you use “REQUEST” GDL commands?)

Moderators: ejrolon, Barry Kelly, Karl Ottenstein, LaszloNagy, Gordana Radonic, nbalogh, gkmethy, mnguyen, rmasaki, Akos Somorjai, Peter Baksa, Csilla Mai

User avatar
By Karl Ottenstein
#325079
Mjules wrote: Fri Apr 23, 2021 10:02 pm Is this a free wall, karl?
I don't know what you mean? It is a free download - download it and play with it :-)
User avatar
By Mjules
#325081
Karl Ottenstein wrote: Fri Apr 23, 2021 11:52 pm
Mjules wrote: Fri Apr 23, 2021 10:02 pm Is this a free wall, karl?
I don't know what you mean? It is a free download - download it and play with it :-)
Sorry, Karl! I should have said free-form wall.
Last edited by Mjules on Sun Apr 25, 2021 2:58 am, edited 1 time in total.
User avatar
By David Shorter
#325091
I would guess that its an object (which really defeats the object of the exercise) sorry about the pun.
Also before we go back to feet and inches a level of accuracy better than 10mm is needed.
By LowFalutin
#325191
Karl Ottenstein wrote: Fri Apr 23, 2021 5:16 pm
Not yet. I hope it is at the top of their priority list. The argument is that GDL and the internals of ARCHICAD are all metric, however the fact that we can actually enter feet and inches (FFI) while coding GDL itself makes that kind of irrelevant. Seems to me that PARAM-O should honor the working units and allow entry in whatever the current working units are.
I hope so too. What is the expected workflow for US users? Convert metric for use in PARAM-O or Grasshopper, ArchiCAD, Rhino connection? I have only spent a few minutes on PARAM-O but I already know it will be easier to integrate into our workflow because the script components use the same terminology as archiCAD. I know you can do anything in the world with grasshopper but to me, that's kinda what makes it so hard to learn, imo
User avatar
By Steve Jepson
#325819
Karl Ottenstein wrote: Fri Apr 23, 2021 5:16 pm
LowFalutin wrote: Thu Apr 22, 2021 10:15 pm It seems like my model units in param-o are in SI / Metric units. Is there a way to use param-o in feet and inches?
Not yet. I hope it is at the top of their priority list. The argument is that GDL and the internals of ARCHICAD are all metric, however the fact that we can actually enter feet and inches (FFI) while coding GDL itself makes that kind of irrelevant. Seems to me that PARAM-O should honor the working units and allow entry in whatever the current working units are.
Yes. And it would not hurt to have more units of measure available as Calculation Units in the program without having to use any expressions/coding.
User avatar
By Steve Jepson
#325821
Gordana Radonic wrote: Thu Mar 25, 2021 12:44 pm Hello everyone,

Have you started using PARAM-O? What are your impressions, experiences so far? Any examples to share?

I am curious to hear what do you think about it.

Kind regards,
Gordana
My first observation about PARAM-O is that unless I can import geometry into the PARAM-O modeler, I am not so enthused with it as I would be if it could do that. I assume plans are underway to make that possible ?
User avatar
By Podolsky
#325823
My opinion that PARAM-O is quite limited in term of modelling capabilities. PARAM-O is generating GDL script, that later ArchiCAD is reading.
Knowing GDL well - it's possible to achieve much faster better results. But only if you know GDL well.

But it's good tool to start learning GDL.
User avatar
By runxel
#325851
Podolsky wrote: Wed May 12, 2021 9:14 pm My opinion that PARAM-O is quite limited in term of modelling capabilities. PARAM-O is generating GDL script, that later ArchiCAD is reading.
Knowing GDL well - it's possible to achieve much faster better results. But only if you know GDL well.

But it's good tool to start learning GDL.
But the code Param-O generates, feels a lot like the code we got out of those 2000-ish visual website generators, since it is littered with XFORMs and what not. Hard to comprehend, so not the easiest thing to learn GDL with. :)
User avatar
By Podolsky
#325856
I might say this way:
For me GDL is just great tool. I was able to extend standard ArchiCAD possibilities with just GDL code. I can agree that there are some limitations, that would be nice to extend, but still so many great things is possible to do with GDL. I can write the code much faster and better than using PARAM-O.
But.
There was a lot of critics about GDL programming - like it's hard etc. Especially when Revit appeared with families. So, PARAM-O it's a compromise for them, who afraid pure coding and remains Dynamo or Grasshopper. A little bit commercial move...

If PARAM-O would extend standard GDL possibilities - I might say - yes, this is really really needed. But unfortunately not. With PARAM-O impossible to do many things, that gives pure GDL coding. At least if PARAM-O would have feature when user can "draw" shapes in 3D like in any 3D modeller (like it was in Visual GDL or ZoomGDL). Maybe this feature will appear in upcoming versions.
User avatar
By Steve Jepson
#326137
Steve Jepson wrote: Wed May 12, 2021 8:48 pm
Gordana Radonic wrote: Thu Mar 25, 2021 12:44 pm Hello everyone,

Have you started using PARAM-O? What are your impressions, experiences so far? Any examples to share?

I am curious to hear what do you think about it.

Kind regards,
Gordana
My first observation about PARAM-O is that unless I can import geometry into the PARAM-O modeler, I am not so enthused with it as I would be if it could do that. I assume plans are underway to make that possible?
To answer my own question - we already can get other geometry/models into PARAM-O -- so long as it is converted into an ArchiCAD object first. No problem. We already have good tools for doing that.