Cool, as to other stuff historic and folkloric designs especially form the early days, I know there is a spoonapult based tcmaker design out there somewhere, I'm guessing there are many more.

On the file layout, my intention was that each type of artwork would have a page based off of the main page.

http://www.tcmaker.org/wiki/doku.php?id ... _logos_etc

So the logo and sinage page here,
http://www.tcmaker.org/wiki/doku.php?id ... nerallogos
would have the files you posted on the main page.

Similarly, the Member drive design files I have will go on the Memberdrive page here.
http://www.tcmaker.org/wiki/doku.php?id ... emberdrive

Sorry, I guess I wasn't clear about that, but I think we'll get hundreds of images on the main page if we don't subdivide, and it will likely load very slowly.

Pete

Thanks, this clarifies the layout question I asked about earlier.

i believe nicklee or theo had the source for the spoonapult logo.

If you need space for g-code files, I can upload them to my host -- or, if you want something that's Maker-owned, perhaps set up a TC Maker dropbox account?

For g-code, I believe we have added the required extensions, I'll verify it this evening.

Pete

Not too worried about g-code, it's text isn't it? I'm wondering about images and the like. One of the links on the wiki goes back to a blog post with a 100MB+ EPS download.

Assuming that is hosted on the tcmaker server, i'm thinking Brandon would appreciate a mirror someplace.

Yes g-code is just text, and I don't think I have anything anywhere near that big.

Pete

we've a few official drop box accounts, we can designate one for this I suspect, but i'm curious as to if that's the best solution before doing so.

I for one am not a fan of Dropbox, or any Cloud solution as primary storage. As a way to publicly share the files, it works fine, but as any organization should, we should control the principal storage location.

Brandon has plans on the HF network, but that is not available now.

The HF Office computer does not get regularly backed up, and it is not web accessible.

The web server appears to be the best choice, and as to how we can discuss it, but again physical control is a common sense thing.

So IMO, this needs to be addressed for all HF Documentation (Public and Private), but right now getting access to it is the primary goal, how is like any hack, go with what works right now, and refine it. We just have to follow up and find a long term solution, rather than just ignoring it once a semi working one is in place.

Regarding the plan for pages as descibed by Pete, note that a lot of the "resource" images will just be thumbnails used for linking out to larger files. We'd want to avoid characterizing the thumbnail images as resources, so people don't get confused and grab the thumbnails as the expected full file.