<?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[Looking for experienced SketchUp Ruby developer for lightweight data-extractor extension]]></title><description><![CDATA[<p dir="auto">Hi everyone,</p>
<p dir="auto">I’m looking for an experienced SketchUp Ruby extension developer for a small paid task, and I would also appreciate general guidance from people who know the SketchUp plugin ecosystem well.</p>
<p dir="auto">My background is in architecture / interiors / renovation. I’m working on a broader project that helps design software send structured project/model data into an external coordination system, so project information can continue into cost, time, procurement, approvals, and project memory instead of staying trapped inside separate design files.</p>
<p dir="auto">For SketchUp, the first version is intentionally lightweight.</p>
<p dir="auto">V1 goal:<br />
Build a SketchUp Ruby extension that reads useful model data and sends structured JSON to an HTTPS endpoint.</p>
<p dir="auto">Rough V1 scope:</p>
<ul>
<li>installable .rbz extension</li>
<li>Windows + Mac support if practical</li>
<li>run on manual save / save trigger</li>
<li>recursively traverse groups and component instances</li>
<li>preserve parent/child hierarchy</li>
<li>include persistent IDs where available</li>
<li>extract object names</li>
<li>extract tags/layers</li>
<li>extract object type</li>
<li>extract bounding box / dimensions</li>
<li>extract existing attribute dictionaries / metadata where available</li>
<li>separate component definition data from placed component instance data where practical</li>
<li>POST structured JSON to an HTTPS endpoint</li>
<li>save a local JSON/log file if POST fails</li>
<li>include sample JSON output and basic install/config instructions</li>
</ul>
<p dir="auto">For V1, I do not need live sync, writeback, model editing, or a complex UI.</p>
<p dir="auto">Later, there may be a V2 with bidirectional features, such as:</p>
<ul>
<li>writing project IDs/status back into SketchUp attribute dictionaries</li>
<li>detecting meaningful changes after an object is linked</li>
<li>selecting/highlighting objects from backend-provided IDs</li>
<li>sending selected object information back to the backend</li>
<li>placing components from a library file with metadata attached</li>
</ul>
<p dir="auto">I am trying to be careful not to build V1 in a way that blocks V2 later.</p>
<p dir="auto">If you are an experienced SketchUp Ruby extension developer and this sounds like something you can help with, please reply or message me.</p>
<p dir="auto">I would also appreciate advice from the community on:</p>
<ol>
<li>whether this should be built purely as a SketchUp Ruby extension</li>
<li>any important limitations around persistent_id, entityID, attribute dictionaries, or save observers</li>
<li>what a good V1 architecture should include so V2 does not require a rewrite</li>
<li>where experienced SketchUp Ruby developers usually look for this kind of paid work</li>
</ol>
<p dir="auto">Thank you — I appreciate any guidance.</p>
]]></description><link>https://community.sketchucation.com/topic/164849/looking-for-experienced-sketchup-ruby-developer-for-lightweight-data-extractor-extension</link><generator>RSS for Node</generator><lastBuildDate>Wed, 06 May 2026 12:06:52 GMT</lastBuildDate><atom:link href="https://community.sketchucation.com/topic/164849.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 03 May 2026 14:31:21 GMT</pubDate><ttl>60</ttl></channel></rss>