user99: On lugnet, it's possible ot insert specific parts in posts with the help of a specific code.
It's very handy, while here it's quite a challenge to insert a part image, and with its full name, id and link to the part it's even more cumbersome. Not to mention the source becomes completely unreadable.
Could we have a similar feature here? At the very least, picking a part and its color, the rest may not be as useful.

user202: A simple way to insert individual parts in a post would be very helpful.
I might argue for something a bit more general.  Essentially, allow markup that wraps a LDRAW-compatible text, generally like this:
<ldr>
1 1 24 -6 0 0 -1 0 -1 0 0 0 0 -1 3005.dat
1 1 48 -6 0 0 -1 0 -1 0 0 0 0 -1 3005.dat
</ldr>

Then display a basic render of it.  Maybe have it link to the raw text.
ldview can render reasonably quickly and with reasonable visual output, and the results would be straight-forward to cache.  (I'm using this approach for my own endeavor.)
Being able to post a model with source like that would open up a lot of interesting possibilities.  Answering questions about how to solve a particular set of space constraints for instance, could be initiated with a model illustrating the constraints, and answerers could start from that model and propose solutions.

user56: 
Install/Update BrickJax UserScript | Source - Updated 06/07/2018
  (Currently tested in Chrome with Tampermonkey and Firefox with Greasemonkey)

While uploading and converting a stream of LDraw mark-up might be nice, it’s certainly not all that intuitive (for me at any rate), whereas writing something like [part:3700] and having it converted via some script into an image call for that part  would be a great first step - and would then tie in with the way we can link to tags (for example [tag:feature-request] is replaced with feature-request).
Any more advanced building images could then be manually created and uploaded by the answerer, allowing finer control over the camera position, layout and finish.
LUGNet offers their images up for use - however their servers can be a little slow and we’re hoping to grow quite large, so using their bandwidth might not be great:

Note: These images are presented here for anyone to reference as needed. You may link directly to these parts images from an off-site web page. To repeat: Yes, it's O.K. to link directly to these images from your website.

What Have We Done?
To that end, Kevin Cathcart and I have put together a script and web service that could be used to replace [part:32181c02:0] with a nice picture of a piston ([part:32181c02:0]) – details of this work, and some examples of it in action can be seen here:
https://brickjax.doodle.uk/
The web service builds up an internal database of parts as they are called, I’ve pre-populated all the supported colours, however at the moment it doesn’t auto-populate the part names, but I’ve got some plans for that.
The script now also replaces set ids with links to various sites, based on this question.
If anyone has any more advice or feature requests do let us know in chat, or post a question here on meta.
What Can You Do To Help?
I would be very grateful if people could test out the GreaseMonkey/UserScript I’ve built (at the suggestion of nhinkle) and provide any feedback you have as this will help my case when talking to the SE Devs about getting this script formally added to the site.

Install/Update BrickJax UserScript | Source
  (Currently tested in Chrome with Tampermonkey and Firefox with Greasemonkey)

Currently it only runs once on page load, so live/AJAX updates aren’t supported.
It's also posted to StackApps:

BrickJax: Brick Image Replacement for bricks.stackexchange.com 

How Can I Use It?
The scripts current support the following mark-up – if the versions at the end are replaced with images or links, then everything’s working as it should.

[part:3700:4]Draw a part (Technic Brick 1 x 2 with Hole) in a colour (red) [part:3700:4].
[partlink:3700:4]Draw a part (Technic Brick 1 x 2 with Hole) in a colour (red) and link to it on Peeron.com [partlink:3700:4].
[set:5590]Link to set 5590 on Peeron: [set:5590].
[bl:5590]Link to set 5590 on BrickLink: [bl:5590].
[bs:5590]Link to set 5590 on BrickSet: [bs:5590].


99: <p>On lugnet, it's possible ot insert specific parts in posts with the help of a <a href="http://www.lugnet.com/publish/ftx/guide/ldrawparts" rel="nofollow noreferrer">specific code</a>.</p>

<p>It's very handy, while here it's quite a challenge to insert a part image, and with <a href="https://bricks.stackexchange.com/posts/363/revisions">its full name, id and link to the part</a> it's even more cumbersome. Not to mention the <a href="https://bricks.stackexchange.com/revisions/0ea2dea1-6fab-4d6c-84b9-2479fc19b246/view-source">source</a> becomes completely unreadable.</p>

<p>Could we have a similar feature here? At the very least, picking a part and its color, the rest may not be as useful.</p>
 202: <p>A simple way to insert individual parts in a post would be very helpful.</p>

<p>I might argue for something a bit more general.  Essentially, allow markup that wraps a LDRAW-compatible text, generally like this:</p>

<pre><code>&lt;ldr&gt;
1 1 24 -6 0 0 -1 0 -1 0 0 0 0 -1 3005.dat
1 1 48 -6 0 0 -1 0 -1 0 0 0 0 -1 3005.dat
&lt;/ldr&gt;
</code></pre>

<p>Then display a basic render of it.  Maybe have it link to the raw text.</p>

<p>ldview can render reasonably quickly and with reasonable visual output, and the results would be straight-forward to cache.  (I'm using this approach for <a href="https://brickbuiltnameplates.com/build" rel="nofollow">my own endeavor</a>.)</p>

<p>Being able to post a model <em>with source</em> like that would open up a lot of interesting possibilities.  Answering questions about how to solve a particular set of space constraints for instance, could be initiated with a model illustrating the constraints, and answerers could start from that model and propose solutions.</p>
 56: <blockquote>
  <p><a href="https://github.com/Zhaph/BrickJax/raw/master/BrickJax.user.js" rel="nofollow noreferrer">Install/Update BrickJax UserScript</a> | <a href="https://github.com/Zhaph/BrickJax" rel="nofollow noreferrer">Source</a> - Updated 06/07/2018<br>
  (Currently tested in Chrome with Tampermonkey and Firefox with Greasemonkey)</p>
</blockquote>

<p>While uploading and converting a <a href="https://bricks.meta.stackexchange.com/questions/62/code-to-insert-parts/85#85">stream of LDraw mark-up</a> might be nice, it’s certainly not all that intuitive (for me at any rate), whereas writing something like <code>[part:3700]</code> and having it converted via some script into an image call for that part <img src="https://i.stack.imgur.com/itluO.gif" alt="part:3700"> would be a great first step - and would then tie in with the way we can link to tags (for example <code>[tag:feature-request]</code> is replaced with <a href="https://bricks.stackexchange.com/questions/tagged/feature-request" class="post-tag" title="show questions tagged &#39;feature-request&#39;" rel="tag">feature-request</a>).</p>

<p>Any more advanced building images could then be <a href="https://bricks.stackexchange.com/questions/440/56#442">manually created and uploaded</a> by the answerer, allowing finer control over the camera position, layout and finish.</p>

<p><a href="http://guide.lugnet.com/partsref/colors/" rel="nofollow noreferrer">LUGNet offers their images</a> up for use - however their servers can be a little slow and we’re hoping to grow quite large, so using their bandwidth might not be great:</p>

<blockquote>
  <p><em>Note: These images are presented here for anyone to reference as needed. You may link directly to these parts images from an off-site web page. To repeat: Yes, it's O.K. to link directly to these images from your website.</em></p>
</blockquote>

<h1>What Have We Done?</h1>

<p>To that end, <a href="https://bricks.meta.stackexchange.com/users/184/kevin-cathcart">Kevin Cathcart</a> and I have put together a script and web service that could be used to replace <code>[part:32181c02:0]</code> with a nice picture of a piston ([part:32181c02:0]) – details of this work, and some examples of it in action can be seen here:<br />
<a href="https://brickjax.doodle.uk/" rel="nofollow noreferrer">https://brickjax.doodle.uk/</a><br />
The web service builds up an internal database of parts as they are called, I’ve pre-populated all the supported colours, however at the moment it doesn’t auto-populate the part names, but I’ve got some plans for that.</p>

<p>The script now also replaces set ids with links to various sites, <a href="https://bricks.meta.stackexchange.com/questions/154/quick-link-to-brickset-or-similar-set-database">based on this question</a>.</p>

<p>If anyone has any more advice or feature requests do let us know <a href="http://chat.stackexchange.com/rooms/1741/bricks-se-parts-javascript-discussion">in chat</a>, or post a question here on meta.</p>

<h1>What Can You Do To Help?</h1>

<p>I would be very grateful if people could test out the GreaseMonkey/UserScript I’ve built (at the suggestion of <a href="https://bricks.meta.stackexchange.com/questions/62/code-to-insert-parts/99#comment349_99">nhinkle</a>) and provide any feedback you have as this will help my case when talking to the SE Devs about getting this script formally added to the site.</p>

<blockquote>
  <p><a href="https://github.com/Zhaph/BrickJax/raw/master/BrickJax.user.js" rel="nofollow noreferrer">Install/Update BrickJax UserScript</a> | <a href="https://github.com/Zhaph/BrickJax" rel="nofollow noreferrer">Source</a><br>
  (Currently tested in Chrome with Tampermonkey and Firefox with Greasemonkey)</p>
</blockquote>

<p>Currently it only runs once on page load, so live/AJAX updates aren’t supported.</p>

<p>It's also posted to StackApps:</p>

<blockquote>
  <p><a href="https://stackapps.com/q/2799/401">BrickJax: Brick Image Replacement for bricks.stackexchange.com</a> </p>
</blockquote>

<h1>How Can I Use It?</h1>

<p>The scripts current support the following mark-up – if the versions at the end are replaced with images or links, then everything’s working as it should.</p>

<ul>
<li><code>[part:3700:4]</code><br />Draw a part (Technic Brick 1 x 2 with Hole) in a colour (red) [part:3700:4].</li>
<li><code>[partlink:3700:4]</code><br />Draw a part (Technic Brick 1 x 2 with Hole) in a colour (red) and link to it on Peeron.com [partlink:3700:4].</li>
<li><code>[set:5590]</code><br />Link to set 5590 on Peeron: [set:5590].</li>
<li><code>[bl:5590]</code><br />Link to set 5590 on BrickLink: [bl:5590].</li>
<li><code>[bs:5590]</code><br />Link to set 5590 on BrickSet: [bs:5590].</li>
</ul>
