<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Why GDL? in Modeling</title>
    <link>https://community.graphisoft.com/t5/Modeling/Why-GDL/m-p/22437#M10754</link>
    <description>Because GDL allows you to make a single object have multiple options or settings that allow it to serve multiple purposes.&lt;BR /&gt;
&lt;BR /&gt;
You do not need to learn GDL to make objects, though. You can just model the object you want and said it as an object.</description>
    <pubDate>Fri, 03 Nov 2006 22:50:52 GMT</pubDate>
    <dc:creator>TomWaltz</dc:creator>
    <dc:date>2006-11-03T22:50:52Z</dc:date>
    <item>
      <title>Why GDL?</title>
      <link>https://community.graphisoft.com/t5/Modeling/Why-GDL/m-p/22436#M10753</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;I have yet to try MaxonForm, so my question may be a little ignorant, I apologize in advance. &lt;BR /&gt;
&lt;BR /&gt;
Why does ArchiCad use GDL as the means to creating complex objects, forms, etc? I don't quite understand why ArchiCad would not incorporate menus, palettes, buttons, and commands to do this in a more intuitive manner (similar to programs that allow a user to do these things without knowing code, Maya, Rhinoceros, Autocad, etc). &lt;BR /&gt;
If I have any major complaints, this is it. ArchiCad's lack of intuitive complex shape-making. For example I think it is easier to think of a "Table" in terms of shapes rather than walls, slabs, beams, and columns. Perhaps this is just because I learned Autocad first...&lt;BR /&gt;
&lt;BR /&gt;
Anywho, I am just looking for some feedback...&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 03 Nov 2006 21:44:44 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Why-GDL/m-p/22436#M10753</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2006-11-03T21:44:44Z</dc:date>
    </item>
    <item>
      <title>Re: Why GDL?</title>
      <link>https://community.graphisoft.com/t5/Modeling/Why-GDL/m-p/22437#M10754</link>
      <description>Because GDL allows you to make a single object have multiple options or settings that allow it to serve multiple purposes.&lt;BR /&gt;
&lt;BR /&gt;
You do not need to learn GDL to make objects, though. You can just model the object you want and said it as an object.</description>
      <pubDate>Fri, 03 Nov 2006 22:50:52 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Why-GDL/m-p/22437#M10754</guid>
      <dc:creator>TomWaltz</dc:creator>
      <dc:date>2006-11-03T22:50:52Z</dc:date>
    </item>
    <item>
      <title>Re: Why GDL?</title>
      <link>https://community.graphisoft.com/t5/Modeling/Why-GDL/m-p/22438#M10755</link>
      <description>&lt;BLOCKQUOTE&gt;mzinski wrote:&lt;BR /&gt;I have yet to try MaxonForm, so my question may be a little ignorant, I apologize in advance. &lt;BR /&gt;
&lt;BR /&gt;
Why does ArchiCad use GDL as the means to creating complex objects, … I foolishly learned Autocad first...&lt;BR /&gt;
&lt;BR /&gt;
Anywho, I am just looking for some feedback...&lt;/BLOCKQUOTE&gt;

These tool names are hold-overs from the early days of Archicad where the UI designer was trying to make designing a building more like the modeling process and less like abstracted geek-land. These descriptions and the tools are deliberately limited (directed) to make understandable architectural elements.&lt;BR /&gt;
&lt;BR /&gt;
I understand your trepidation because by calling a primitive that has a primarily horizontal orientation a "slab," it prejudices the user from using it in unexpected ways, such as like a board, say. And in calling a tiltable, trimmable plane a "Roof," it prejudices the user from making table legs with it.&lt;BR /&gt;
&lt;BR /&gt;
Recipe for table:&lt;BR /&gt;
&lt;BR /&gt;
A 3/4" slab = table top&lt;BR /&gt;
Profiler at perimeter for nosing.&lt;BR /&gt;
A set of four 3/4" thick walls x 4" high = table skirt&lt;BR /&gt;
A set of four square roof pieces of zero slope 26" deep with 1 degree tapered edges all around = tapered legs.&lt;BR /&gt;
&lt;BR /&gt;
Now you have a table modeled with "primitives."&lt;BR /&gt;
&lt;BR /&gt;
Model these elements together, make a top view in 3D and Save 3D model As - Archicad Object File. No GDL at all.&lt;BR /&gt;
&lt;BR /&gt;
You'll see, reviewing the 3D Script of the object, that it is editable GDL code, made without you knowing the GDL language at all.&lt;BR /&gt;
&lt;BR /&gt;
It CAN be an interesting game to actually create objects with GDL code to permit parameter adjustments. &lt;BR /&gt;
&lt;BR /&gt;
Anyone would admit that Archicad is not a good free-form, modeler. If you want to make ambiguous, editable losenges, forget it - without the Maidenform tool. But for a block of flats, it has no equal.</description>
      <pubDate>Sat, 04 Nov 2006 00:25:29 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Why-GDL/m-p/22438#M10755</guid>
      <dc:creator>Dwight</dc:creator>
      <dc:date>2006-11-04T00:25:29Z</dc:date>
    </item>
  </channel>
</rss>

