<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Group vs. Component]]></title><description><![CDATA[<p dir="auto">I am continuously confused by people referring to components. I have read a recent thread in this forum where the writer says that any sub-group in a DC must be a component to work properly.<br />
In fact I ONLY create my DC with Groups and sub-groups.<br />
Scouring the Google documentation, the only case for using a component is when you make copies of some geometry so that when one of them is modified, the others change as well. This feature is not necc. for a DC which has the Copies feature of course.<br />
Writers in the forums talk about "component this" and "component that" but is it really necc... not in my experience. The attached DC uses only Groups.<br />
Obviously I still have doubts , which is why I post here to see if there are any who would like to argue the point  <img src="https://community.sketchucation.com/assets/plugins/nodebb-plugin-emoji/emoji/android/1f604.png?v=e3ff0b7518f" class="not-responsive emoji emoji-android emoji--smile" style="height:23px;width:auto;vertical-align:middle" title=":smile:" alt="😄" /></p>
<hr />
<p dir="auto"><img src="/uploads/imported_attachments/LH9r_sketchupscreenshot.jpg" alt="sketchupscreenshot.jpg" class=" img-fluid img-markdown" /></p>
]]></description><link>https://community.sketchucation.com/topic/133873/group-vs-component</link><generator>RSS for Node</generator><lastBuildDate>Tue, 19 May 2026 10:27:19 GMT</lastBuildDate><atom:link href="https://community.sketchucation.com/topic/133873.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 14 Mar 2012 22:59:55 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Group vs. Component on Thu, 05 Apr 2012 16:40:34 GMT]]></title><description><![CDATA[<p dir="auto">I have exactly the same question, I like the idea of using groups inside my dynamic components as they don't clutter me up with lots of little sub-components that only have relevance within the main component.</p>
<p dir="auto">I have used both groups and components successfully and haven't noticed any discernable difference but I am a newbie.</p>
<p dir="auto">One day when I have time I have considered making a dynamic component using nested groups and an identical one using nested components and then compare the two for file size, speed etc.</p>
<p dir="auto">Unfortunately my TODO list is pretty long, I will watch this thread with interest</p>
]]></description><link>https://community.sketchucation.com/post/1320244</link><guid isPermaLink="true">https://community.sketchucation.com/post/1320244</guid><dc:creator><![CDATA[FlobRob]]></dc:creator><pubDate>Thu, 05 Apr 2012 16:40:34 GMT</pubDate></item><item><title><![CDATA[Reply to Group vs. Component on Wed, 04 Apr 2012 19:29:42 GMT]]></title><description><![CDATA[<p dir="auto">Groups should work just fine.  I think I (and perhaps most people) just get used to making everything a component.  I've never found much use for groups personally.</p>
<p dir="auto">-Brodie</p>
]]></description><link>https://community.sketchucation.com/post/1320041</link><guid isPermaLink="true">https://community.sketchucation.com/post/1320041</guid><dc:creator><![CDATA[brodie]]></dc:creator><pubDate>Wed, 04 Apr 2012 19:29:42 GMT</pubDate></item></channel></rss>