abecedarian 330 Posted October 4, 2013 Share Posted October 4, 2013 During my recent trip to Maker Faire 2013 in NYC I had the opportunity to visit the nearby MakerBot retail store and headquarters. During these visits I got to talk with CEO Bre Pettis and learn about MakerBot. We discussed MakerBot Quote Link to post Share on other sites
Rickta59 589 Posted October 4, 2013 Share Posted October 4, 2013 Nice spin ... there are other stories to be heard http://www.hoektronics.com/2012/09/21/makerbot-and-open-source-a-founder-perspective/ http://www.makerbot.com/blog/2012/09/20/fixing-misinformation-with-information/ .. my comments are in there http://hackaday.com/2012/09/20/makerbot-occupy-thingiverse-and-the-reality-of-selling-open-hardware/ read the comments http://hackaday.com/2012/09/20/makerbot-occupy-thingiverse-and-the-reality-of-selling-open-hardware/#comment-791466 Quote Link to post Share on other sites
abecedarian 330 Posted October 4, 2013 Author Share Posted October 4, 2013 Even if MakerBot is closed source, that doesn't detract from Windows having support for a protocol that could permit 3D printing, does it? Quote Link to post Share on other sites
Rickta59 589 Posted October 4, 2013 Share Posted October 4, 2013 I don't run windows and I'm sure the protocol they come up with attempt to make it work on windows only. Quote Link to post Share on other sites
Rickta59 589 Posted October 4, 2013 Share Posted October 4, 2013 http://msdn.microsoft.com/en-us/library/windows/apps/dn263137.aspx Implemented as a bunch of extensions to their printer driver code and win32 api. Of course the format the rest of the world is using (STL) isn't good enough and they can't control it so they came up with their own 3d format to cause a rift and force people to pay attention to what they are doing if they want to play. It is typical Micro$oft tactics. Embrace, extend, extinguish. Everything they get involved with becomes a cluster f***. Quote Link to post Share on other sites
abecedarian 330 Posted October 4, 2013 Author Share Posted October 4, 2013 From your link, Your app must create a 3D model and add it to a document package as independent content. A 3D model is a collection of one or more physical objects in a markup format. Your app may also provide 2D XPS content. Depending on whether the package is sent to a 3D printer or a 2D printer, the 3D content or the 2D XPS content is printed. The content is sent to the printer by writing either the 3D content or the combined 3D and XPS file via a 3D package writer object (IXpsOMPackageWriter3D). For more info about Windows printing, see Printing. Of course it's going to be tied to the printer driver code and Windows' API's: how else would it interface with Windows? And we'll forget the fact it's based around XPS which is an open standard adopted by ECMA and others, meaning anyone can interpret the container and print the object and therefore Linux developers can write their own drivers. If Linux users and dev's aren't on the bandwagon, that's their problem. I'm not here to argue motives. I only thought it was cool. Quote Link to post Share on other sites
Fred 453 Posted October 4, 2013 Share Posted October 4, 2013 It's not quite there yet. If you're using Windows 8.1 and have a printer that's apparently on board with it (Up Plus)... the standard software won't even install. :-( Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.