 | | Re: NEW SOFTWARE: PicToBrick - Make your own mosaic!
|
|
(...) [reply on behalf of Tobias Reichling] Hi Jordan, this paper exists in a German version only, and due to the size of this document (more than 50MB as .pdf file) it is not available for download. best regards, Jan (on behalf of Tobias) (18 years ago, 19-Jan-07, to lugnet.cad, lugnet.build.mosaic)
|
| |
| | Re: NEW SOFTWARE: PicToBrick - Make your own mosaic!
|
|
(...) Is their paper anywhere on their site? I'd like to read it. (18 years ago, 19-Jan-07, to lugnet.cad, lugnet.build.mosaic, FTX)
|
| |
| | NEW SOFTWARE: PicToBrick - Make your own mosaic!
|
|
Hello! I'm posting this on behalf of Tobias Reichling: (URL) Hi, we - Adrian Schütz and Tobias Reichling, two German students (computer science) - have passed our diploma with the title: "Generating mosaics from multicolor raster graphics by (...) (18 years ago, 19-Jan-07, to lugnet.cad, lugnet.build.mosaic, FTX) !!
|
| |
| | Re: Duplicating problem in MPD rendering
|
|
(...) Brian, Do any of the sub-assemblies use the buffer exchange feature? When using an mpd file and this feature, you can run into problems when rendering the main assembly if you ghost the wrong parts or forget to ghost other parts in the (...) (18 years ago, 19-Jan-07, to lugnet.cad)
|
| |
| | Duplicating problem in MPD rendering
|
|
I noticed when I render a multi part document using L3PAO and Povray it seems to make a duplicate ghost of some of the parts. The document has four models: - Complete assembly - Subassembly 1 - Subassembly 2 - Subassembly 3 The complete assembly (...) (18 years ago, 18-Jan-07, to lugnet.cad)
|
| |
| | Re: Contributor Agreement License details
|
|
(...) guys, before speculation grow wild I'll take the whole thing back to the steerco. thx for any input - though I have to admit that some posts go further than my wildest dreams ever did. as far as I understand the license both license files have (...) (18 years ago, 18-Jan-07, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Contributor Agreement License details
|
|
(...) I wonder whether a model file really qualifies as a "collective work" under this definition since an LDR file doesn't actually contain the parts definitions, only references to them. (Unless of course, the external parts definitions are (...) (18 years ago, 18-Jan-07, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Contributor Agreement License details
|
|
(...) This is crazy talk. People sign paintings, but nobody is ever gonna staple a note on the back of a painting that says, "This painting was created with ACME brand paints and brushes." Please don't insert any such crazy demand in the ldraw (...) (18 years ago, 18-Jan-07, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Should pattern be like we -think- they should be?
|
|
(...) Have you counted the ones at the Tracker? (URL) are currently 30 parts or shortcuts with (nedds work) in description line. /Tore (18 years ago, 18-Jan-07, to lugnet.cad.dat.parts)
|
| |
| | Re: Contributor Agreement License details
|
|
(...) While rendered images are Derivative Works, I do not think you would have to add anything such as a copyright notice to them. The language of the CALicense.txt paragraph 4.2 says to the extent reasonably practicable or at a minimum where you (...) (18 years ago, 18-Jan-07, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Contributor Agreement License details
|
|
(...) All of the parts authors would have to agree to that, because (and my knowledge is limited so if I mistake any assumptions let me know) the copyright of the part file seems to be held by the parts author not the LDraw Parts Library or any (...) (18 years ago, 18-Jan-07, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Contributor Agreement License details
|
|
(...) There is one significant difference between LDraw and Photoshop in that you pay for the right to use Photoshop without giving credit. That said I don't think we need to vandalise our images to put the credit in but I'm not completely averse to (...) (18 years ago, 18-Jan-07, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Contributor Agreement License details
|
|
(...) In publishing, that type of info is usually contained in a colophon, the use of which is sadly fading from popularity. Some few web sites include this level of detail in their "About" section. I agree it would be nice to see attribution in (...) (18 years ago, 18-Jan-07, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Contributor Agreement License details
|
|
(...) As one of the CA's authors, my view on this is that you should state somewhere in your distribution of the image (i.e. on the web page hosting it, as a text file in a .zip, on the image itself, etc...) that the content were derived from the (...) (18 years ago, 18-Jan-07, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Contributor Agreement License details
|
|
(...) I agree, clarification on rendered images is needed. If a rendering using LDraw parts is a derivative work, and derivative works are required to visibly display credit, that's a problem. It won't show up on my renders; I don't burn "Credit: (...) (18 years ago, 18-Jan-07, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Contributor Agreement License details
|
|
(...) Maybe it's just me, but if renderings are considered derivative works, we need to seriously step back and think long and hard about whether or not we are OK with that. I personally think that forcing renderings to have text on them (...) (18 years ago, 18-Jan-07, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Web browser compatibility testing request
|
|
(...) Look fine in Mozilla 1.7.13 Roland (18 years ago, 18-Jan-07, to lugnet.cad.dev)
|
| |
| | Re: Contributor Agreement License details
|
|
(...) Maybe It's a stupid question but here goes ... Does this mean when you put a rendering (or rendered animation) on the Internet you must scribble 100+ names on the png / frames / end credits. If so I think that's very restricting, a simple (...) (18 years ago, 18-Jan-07, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Web browser compatibility testing request
|
|
For anyone who's interested, here is the output from a more complicated model: (URL) chose pyramid for the test because it allowed me to take a screenshot of the entire page.) Notice that it doesn't show images for any parts that aren't recognized (...) (18 years ago, 17-Jan-07, to lugnet.cad.dev)
|
| |
| | Re: Web browser compatibility testing request
|
|
(...) <snip>> Thanks in advance. (...) Looks great on my Treo 650 with PalmOne Blazer 4.0. Although the partslist images the edges show up white reather than black ans make the parts look a bit funky... (18 years ago, 17-Jan-07, to lugnet.cad.dev)
|
