I hope GitHub adds support for scad files soon. In theory it should be pretty easy since they already support STL -- have openscad generate an STL from the scad files on the fly.
It sounds like what you'd really want, in that case, would be an ASCII-encoded log-structured manipulation-history format--sort of similar to a Redis Append-Only File.
This model is a combination of stl or dae files, created with a script file that puts the coordinates of the individual stl files.
I'm waiting for the day that maybe github could host full simulations and we test them out in the browser.
(Now that would be cool).
* Visual STL diffs, maybe by coloring deleted/added triangles. Possibly with a viewer on gh-pages or on the /:username/:reponame/commits/:branchname endpoint?
* DXF sucks, but yeah DXF rendering.
* Maybe consider thingiview.js (which does not use WebGL) or possibly a WebGL equivalent viewer. Controlled rotation, zooming, camera repositioning, etc. It seems that most of these features are implemented:
* openscad rendering- I know this is a pain in the butt, especially since openscad still requires xserver. But at least it feels more like source code. There are some other options other than openscad that could be easier to render without an xserver, which would be fine in my book, I am not particularly attached to openscad.
* Other scripting/rendering options... maybe implicitcad, pythonocc (opencascade/python bindings), HeeksCAD/python, FreeCAD/python, OpenJSCAD, something like that. The problem with STL is that it's like transmitting compiled binaries to other developers, but what developers really want to work with is the source code. Having to commit STL is like having to commit compiled binaries.
* UI widgets for committing from SolidWorks, Pro/Engineer, CATIA, AutoCAD, HeeksCAD, FreeCAD, and other front-ends would be really useful. I would be happy to use github.com while working on my next fighter jet project.
* Upverter claims to support git, but really it's just a link to a remote git repository and you can't push your schematics to Upverter. Please feel free to eat their lying lunches. Maybe also circuitlab's (although they have never claimed to have git integration). So yeah, schematics.
* Some projects require thousands of parts that need to be included when rendering, especially in assemblies. It would be nice to be able to see a fully rendered image of a version of the repository contents. This quickly devolves into a mess of file format hell, which I imagine is not something you want to tackle. But maybe this could be done through continuous integration hooks or something?
For whatever it's worth, here's a terrible post-receive bash script I wrote in 2010 for scad rendering on a git server:
* It would be exceedingly awesome if you could get the RepRap project to jump ship from svn to git. RepRap is the largest, most well organized open source hardware project, and I think it would be a great community to work with to show how strong git is for distributed hardware development.
There are already some really excellent RepRap projects in git repositories on github:
Actually, I implemented a lot of this on a private project in 2010-2011 that I never launched. There are a lot of other competitors trying to be "GitHub for Hardware"- but a lot of them fail to bother to implement git support. I think it's great that GitHub is moving in this direction.
Is your project open-source?
CAD is a really interesting industry from an open source perspective. BRLCAD has done some really excellent work. "Something" needs to come in and bulldoze the mess that OpenCASCADE has left. It turns out that writing NURBS intersection code is really not a cake walk.. go figure. Not sure what that "something" is going to be yet.
Btw, I would love to talk with you about your industry experience. We could mutually complain about how terrible ISO 10303 is!
GrabCAD is about as close to this as you get as far as implementing solid CAD stuff.
Nick, you and I have met, we've talked about this before. I'm really surprised that you think that I think they are simple add-ons. We've talked for hours about these things, how the heck could you get that impression from me!
Feel free to send me an offer :)
They seem to be doing precisely that:
"This viewer is powered by Three.js and uses WebGL when available, but will fall back to the slower canvas renderer."
OpenNURBS doesn't count because Rhino has kept all the interesting bits to themselves. BRLCAD has had people from GSoC implement some of the remaining closed-source parts of the OpenNURBS library, so maybe they have had some recent progress on this front?
OpenCASCADE doesn't count because trying to extract just what you need is like trying to rewrite the multiple decades of software piled up in there..
Edit: Nick, didn't we have this exact conversation before in some HN comments like two years ago? I feel like we did and I feel bad for not remembering the url. Maybe this?
Invalid 'X-Frame-Options' header encountered when loading 'https://render.github.com/view/3d/?url=https%3A%2F%2Fraw.github.com%2FEmmanuelG%2FFoldaRap2%2Fmaster%2Fstl%2Flower-corners.stl': 'ALLOW-FROM: https://github.com/' is not a recognized directive. The header will be ignored.
Running Chrome stable. Looks like a malformed cross-origin directive?
EDIT: The error is still here but it works from time to time. Some of the time I get a "Something went wrong? Reload" message, the rest of the time, the 3D model actually appears.
It's be nice if, when you sign in, you could change which viewer was associated with which file type. Then I could fork their viewer, add my own features, and use that.
A better error message would go a long way here :)
Sketchfab doesn't have native support for git repositories. You could upload a tarball of a git repository, but that's seriously missing the point.
Next step: support Wavefront's .OBJ files.
That or Thingiverse integration.
STL is for manufacturing. STL has long been popular for commercial FDMs and CNC machines, and it is also what hobbyists use for their FDMs ("3D printers").
Finally people are moving forward from the twenty-year-old OBJ and the horrorshow that is FBX...
Here, here's the specs for that pile of offal:
It's a shitty, bad, bloated, slow, rubbish XML format. It has accumulated so much garbage in the name of interop that it is overkill for >95% of applications, and parsing/generating it is really annoying. It's a solution in search of a problem.