<?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: ISSUE_Style - ArchiCAD GDL Reference Guide in Libraries &amp; objects</title>
    <link>https://community.graphisoft.com/t5/Libraries-objects/ISSUE-Style-ArchiCAD-GDL-Reference-Guide/m-p/280352#M3124</link>
    <description>I just use &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;"buildingMatIndex"&lt;E&gt;&lt;/E&gt; or something along those lines then maybe follow it with a suffix if there are multiple. Or following a similar line of thought, you could put &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;"Index or idx"&lt;E&gt;&lt;/E&gt; at the start in reference to file attributes. But in the end, it comes down to user preference and/or user protocol of how you label everything.&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
Ling.</description>
    <pubDate>Wed, 30 Jan 2019 01:41:31 GMT</pubDate>
    <dc:creator>Lingwisyer</dc:creator>
    <dc:date>2019-01-30T01:41:31Z</dc:date>
    <item>
      <title>ISSUE_Style - ArchiCAD GDL Reference Guide</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/ISSUE-Style-ArchiCAD-GDL-Reference-Guide/m-p/280351#M3123</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;R&gt;Hi there,&lt;BR /&gt;
&lt;BR /&gt;
In "&lt;B&gt;ArchiCAD 22 GDL Reference Manual&lt;/B&gt;" page 494 under "&lt;B&gt;Variable names&lt;/B&gt;" it states and I quote:&lt;BR /&gt;

&lt;BLOCKQUOTE&gt;You should use a prefix in generally used variable names to denote general categories. This can spare time when someone needs to find out the&lt;BR /&gt;
type of a variable or parameter.&lt;/BLOCKQUOTE&gt;

But there nothing mentioned about Building Materials ... I think you should include this point in the GDL manual&lt;/R&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 29 Jan 2019 20:15:56 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/ISSUE-Style-ArchiCAD-GDL-Reference-Guide/m-p/280351#M3123</guid>
      <dc:creator>Nader Belal</dc:creator>
      <dc:date>2019-01-29T20:15:56Z</dc:date>
    </item>
    <item>
      <title>Re: ISSUE_Style - ArchiCAD GDL Reference Guide</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/ISSUE-Style-ArchiCAD-GDL-Reference-Guide/m-p/280352#M3124</link>
      <description>I just use &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;"buildingMatIndex"&lt;E&gt;&lt;/E&gt; or something along those lines then maybe follow it with a suffix if there are multiple. Or following a similar line of thought, you could put &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;"Index or idx"&lt;E&gt;&lt;/E&gt; at the start in reference to file attributes. But in the end, it comes down to user preference and/or user protocol of how you label everything.&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
Ling.</description>
      <pubDate>Wed, 30 Jan 2019 01:41:31 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/ISSUE-Style-ArchiCAD-GDL-Reference-Guide/m-p/280352#M3124</guid>
      <dc:creator>Lingwisyer</dc:creator>
      <dc:date>2019-01-30T01:41:31Z</dc:date>
    </item>
    <item>
      <title>Re: ISSUE_Style - ArchiCAD GDL Reference Guide</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/ISSUE-Style-ArchiCAD-GDL-Reference-Guide/m-p/280353#M3125</link>
      <description>Ling, my comment was for standardisation</description>
      <pubDate>Wed, 30 Jan 2019 15:14:42 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/ISSUE-Style-ArchiCAD-GDL-Reference-Guide/m-p/280353#M3125</guid>
      <dc:creator>Nader Belal</dc:creator>
      <dc:date>2019-01-30T15:14:42Z</dc:date>
    </item>
  </channel>
</rss>

