Images for the wiki

Have a suggestion for the website or forum? Post it here.
Post Reply
Posts: 8616
Joined: Mon Apr 09, 2012 6:11 pm
Location: Pennsylvania --- south of the Turnpike, East of US-15

Images for the wiki

Post by WillAdams » Fri May 10, 2013 3:50 pm

First a technology question: Would it be possible to run OpenSCAD on the server? That way, if we could re-create all the 3D renderings using OpenSCAD, we could have source code on the web pages and have the server render them when they're up-dated.

Anyway, there are a number of images on the wiki which need to be up-dated, as well as some photos which need to be taken or re-taken --- anyone have a handle on how to go about that?

Shapeoko 3XL #0006 w/ Carbide Compact Router w/0.125″ and ¼″ Carbide 3D precision collets

Posts: 4442
Joined: Thu Jul 19, 2012 6:50 pm
Location: Camberley, UK

Re: Images for the wiki

Post by cvoinescu » Fri May 10, 2013 6:04 pm

You don't need to run OpenSCAD on the server, unless you want to do this on the fly, which I feel is not necessary (or even desirable). As long as the parts, the assembly diagrams and whatever else you need can be expressed as text, stored under source control, and there is a program or series of programs that can take the text and convert it into the image you need, that's fine. You can run that on your box and upload the results. That's how SourceForge, GitHub etc work for programs -- they don't run the compilers on the server. A maintainer gets the source code from the server, builds it on his or her machine, and uploads the binaries.

That reduces the problem to: can we describe a given diagram as, say, an OpenSCAD source file, plus any additional files and command line options as necessary, to include such details as guide lines, viewing angles, rendering options, part number callouts, legends and so on, so that the image can be built without additional user input? Can we put all of that in a makefile and run that to rebuild them when the source changes? (That makefile could also include steps to upload the resulting images, but let's focus on the essential for now.)
Proud owner of ShapeOko #709, eShapeOko #0, and of

Post Reply