<?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 A rethink on library parts - the &amp;quot;Part-module&amp;quot; in Libraries &amp; objects</title>
    <link>https://community.graphisoft.com/t5/Libraries-objects/A-rethink-on-library-parts-the-quot-Part-module-quot/m-p/134893#M15406</link>
    <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Library parts&lt;BR /&gt;
-still no 'visual' object builder&lt;BR /&gt;
-version upgrade must be managed and can be problematic&lt;BR /&gt;
&lt;BR /&gt;
A reasonably simple method to address this issue - the "part-module":&lt;BR /&gt;
-create an object with native archicad elements. Copy and save as module from clipboard.&lt;BR /&gt;
-Save modules into a dedicated folder for the project.&lt;BR /&gt;
-Hot-link modules into the file and place as required.&lt;BR /&gt;
-These "part-modules" can be updated easily by updating the MOD file.&lt;BR /&gt;
&lt;BR /&gt;
However to really get this technique to work, some things Graphisoft could implement that would help:&lt;BR /&gt;
- create the possibility of "part-modules" nested within projects - much like worksheets&lt;BR /&gt;
- allow for  different 'stories' setup in "part-module'"&lt;BR /&gt;
- enable different plan cut level in part module so that plan symbol can be tailored. &lt;BR /&gt;
- allow in place editing of placed instances of these "part-modules" so that these can easily be updated&lt;BR /&gt;
- enable defining parameters of an element (e.g. wall height, width, length etc.) rather than a fixed number. &lt;BR /&gt;
- enable definition of relationship between elements&lt;BR /&gt;
&lt;BR /&gt;
Yes - I can hear all the GDL gurus groaning but for most users this approach is something they might use! Comments?&lt;/T&gt;&lt;/DIV&gt;</description>
    <pubDate>Wed, 28 Mar 2012 10:59:07 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2012-03-28T10:59:07Z</dc:date>
    <item>
      <title>A rethink on library parts - the "Part-module"</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/A-rethink-on-library-parts-the-quot-Part-module-quot/m-p/134893#M15406</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Library parts&lt;BR /&gt;
-still no 'visual' object builder&lt;BR /&gt;
-version upgrade must be managed and can be problematic&lt;BR /&gt;
&lt;BR /&gt;
A reasonably simple method to address this issue - the "part-module":&lt;BR /&gt;
-create an object with native archicad elements. Copy and save as module from clipboard.&lt;BR /&gt;
-Save modules into a dedicated folder for the project.&lt;BR /&gt;
-Hot-link modules into the file and place as required.&lt;BR /&gt;
-These "part-modules" can be updated easily by updating the MOD file.&lt;BR /&gt;
&lt;BR /&gt;
However to really get this technique to work, some things Graphisoft could implement that would help:&lt;BR /&gt;
- create the possibility of "part-modules" nested within projects - much like worksheets&lt;BR /&gt;
- allow for  different 'stories' setup in "part-module'"&lt;BR /&gt;
- enable different plan cut level in part module so that plan symbol can be tailored. &lt;BR /&gt;
- allow in place editing of placed instances of these "part-modules" so that these can easily be updated&lt;BR /&gt;
- enable defining parameters of an element (e.g. wall height, width, length etc.) rather than a fixed number. &lt;BR /&gt;
- enable definition of relationship between elements&lt;BR /&gt;
&lt;BR /&gt;
Yes - I can hear all the GDL gurus groaning but for most users this approach is something they might use! Comments?&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 28 Mar 2012 10:59:07 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/A-rethink-on-library-parts-the-quot-Part-module-quot/m-p/134893#M15406</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2012-03-28T10:59:07Z</dc:date>
    </item>
    <item>
      <title>Re: A rethink on library parts - the "Part-module"</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/A-rethink-on-library-parts-the-quot-Part-module-quot/m-p/134894#M15407</link>
      <description>Don't expect any groaning from the gurus. Something like this has been needed and a top wish list item for a long time. Some 3rd party attempts have been made but without some internal changes to GDL and ArchiCAD I think such efforts are doomed.&lt;BR /&gt;
&lt;BR /&gt;
Though the particulars could be (and have been debated) I think most would agree with your proposal in general. It's hard to say if we'll ever see it though &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_sad.gif" style="display : inline;" /&gt;</description>
      <pubDate>Tue, 03 Apr 2012 00:26:36 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/A-rethink-on-library-parts-the-quot-Part-module-quot/m-p/134894#M15407</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2012-04-03T00:26:36Z</dc:date>
    </item>
  </channel>
</rss>

