xlib

Eurobricks Vassals
 View Profile  See their activity

  • Content Count

    41

  • Joined

  • Last visited

Everything posted by xlib

  1. xlib
    I just wanted to point out that those "stolen" videos doesn't actually infringe copyright. Whenever I browse sites like rebrickable or this very forum, I never saw license terms attached to some model (unless instructions are sold). This said, if I take, for example, Sariel's model, assemble it and make a video about it, law says that I'm legitimate copyright holder. Re-posting video is also "a-OK" in the eyes of law, especially when you do it on the same site (youtube). It may be some TOS violation, though. Plagiarism is bad, but not illegal.
  2. xlib
    :) That's because "likeness rights" is not a thing. Most close concept (in USA) is "design patent" (kind of patent Apple fought Samsung) or publicity rights for people.
  3. xlib
    The license attached to LDD prohibit commercial use. Quote: You may NOT: (vii) use the Software or the backup copy for any commercial purpose; (viii) remove any proprietary notices or labels on the Software or Documentation; So the answer is simple - commercial use of LDD will violate its license. There's no such thing. Lego attempted to patent its bricks, and failed to do so. You can even manufacture compatible bricks, unless you call them "Lego" or any other registered phrase, like "Nexo" (that would be trademark violation). Now, since you're seeking legal advice on internet forum instead of your lawyer, I suspect that it is possible that nobody will care, you're not shooting Hollywood blockbuster.
  4. xlib
    Impressive construct, though grip looks unstable
  5. xlib
    According to ebay listing calculator that listing would cost $750.
  6. xlib
    And in software world this kind of request is common practice. Like 'derived work must retain licence and give credit'. Idea that can be bought and sold is called 'patent'. It doesn't require to give credit.
  7. xlib
    Yes, all this is correct. Actually, it means 1) my volume estimate is correct, it's container-sized and 2) my price estimate is off by only x1.5. Very big, too expensive - fake.
  8. xlib
    Uhm - no. "Ships to: Worldwide" However, back-of-envelope calculation shows that: Dimensions of "Lego 42009 mobile crane" are 22.9 x 18.9 x 3.6 inches, and weight is 8.6 pounds. Assuming that those ~4500kg have about same density, it takes about 35m^3. Volume of common shipping container is 39m^3. This thing is huge. Same amount of those cranes will cost about $350K which is about x3 cheaper, and it's for new stuff. Conclusion - 100% fake. Or advertising. Or something.
  9. xlib
    Or, alternatively, you can take a look at http://ev3lessons.com/index.html
  10. xlib
    1. You asked 2 questions: a)"press X times -> run X'th program" and b)"run the program depending on color sensor output". Answer for "b" is simple - you're just using "switch" block controlled by output of color sensor. Or maybe I'm missing something? Answer for "a", however, is more complicated. What you say "press button 2 times" what you actually mean is "time between press #1 and #2 is less then some threshold". So, you should build simple state machine here - touch sensor starting timer. Then you wait for timeout expiration or new button press. If timeout expired - act upon number of presses you counted. And yes, this is somewhat complicated, maybe i will come up with examples later. 2. This looks simple - just have another loop that counts distance and stop the motors (or do other action).
  11. xlib
    First of all, I really like an idea of more-than-basic PF controller. However: 1. Price Fair comparison is $15 x 2 + $13 + $12 (cost of 6 AAA rechargeable batteries) = $55 vs $100, with added bonus of replaceable batteries. 2. Setup IR connection require switch in correct position; BT connection require pairing. Depending on firmware this may limit connectivity to 1/2/3 specific phone(s)/tablet(s). 3. Connectivity Connecting BT stuff to iPhone require Apple's certification and maybe royalties. This is not even mentioned on product page, and may add to cost. 4. API availability Closed, proprietary API is bad idea in almost any case, and this is not an exception. Lack of reasonably open API is definitely a drawback. CE, FCC and similar certifications are usually handled by supplier of BT component.
  12. xlib
    Yes, library is documented. And copyrighted. So you can't "easy to extend the library" - only with author's permission.
  13. xlib
    Hi all I'd like to present a viewer for LDR/MPD files on Apple devices. The idea is to open files which are already present on device in Dropbox, Google Drive, email and so on. App allows to view model from different angles, zoom, rotate or "disassemble" it to view internals. Line to iTunes https://itunes.apple.com/us/app/studless/id1039486304?ls=1&mt=8 Opinions and/or complains are welcomed
  14. xlib
    Ah, I see where confusion is coming from. Let me explain. Yes, LDD2POVRay and Bluerenderer are using data from LDD, but in order to do that, you must download and install LDD by yourself. This is key point here - you may use files which are legally installed on your computer, but you may not distribute files of someone else. So, you your program require LDD to be installed in order to use its library - that's OK. But distribute LDD's library (or anything derived from it) along with your program - not OK. So, IMHO relying on LDD library is bad proposition - this data is internal to LDD and developers are not required to maintain backward compatibility even IF application is continued to be supported.
  15. xlib
    LDCad is close-sourced. Its library is copyrighted. Even IF you somehow understand how its library works, you can't (legally) take it. Same true for SR3D. Yes, _stud_ is indeed primitive. But opposite part of stud (how does it called?) is not. Think: you connect stud in the middle between 4 "walls". That's just place where stud fits. How do you automatically define this point when surrounding "walls" are not parts of some logical structure? IIRC it's hard algorithmic problem.
  16. xlib
    In privacy of your home you can do whatever you want, disassembling programs included. Of cause, you can't distribute modified copyrighted stuff, be it book, program and so on. That is only true for disassembling native machine code. In case of run-on-VM languages, like Java, .NET and similar you may get actual human-readable source code. Even identifiers will be preserved in some cases. In your example, “benefits = revenues - expenses” can be disassembled to MoneyModule.var1 = MoneyModule.var2 - MoneyModule.var3. Data which accompanying the program is copyrighted in same was as a program itself. Meaning, that if you understand .DOC format, it doesn't mean you can (legally) reuse Microsoft's templates coming with Office install. So, while .G format is pretty simple, reverse engineering of it will bring no actual benefit beyond academic exercise.
  17. xlib
    Developing such program is indeed big effort. However, such effort can not be even started before more fundamental problems with data format are resolved. Main problem is that LDraw format is unsuitable for CAD as it lacks connectivity information and is very inconvenient from computational geometry point of view. This is easy part - don't use stuff from LDD. TLG have no software patents, so independently developed program can't be "C&D'ed". Let's explore all presented here options. "LDraw" - crappy format, no connectivity or physics information, very comprehensive database "LDD" - format undocumented, data copyrighted. Definite no-go unless TLG release data and documentation under some kind of very permissive license. "build one from scratch" - unrealistic goal. Neither me nor _anyone_ I've met on these forums have good knowledge in computational geometry. There's no reason proposed standard will be better than LDraw. The best chance is to use LDraw as a base and add connectivity information by "compute+manual override".
  18. xlib
    False and what's more important - irrelevant. They have plenty of time, and unlimited brick supply. And - they must build physical set anyway. Common sense suggests, that "design/idea check/prototype" is done by physical bricks; and virtual/3D model is built together with other production steps. Agree. The only way it can be usefully "opened" - is to make LDD open source. No chance for this to happen.
  19. xlib
    First, there seem to be a strange assumption that there's one-size-fit-all software. I can bet that internally, TLG people using all kinds of software for different purposes. * For design of parts itself, Autocad/Solidworks style software is an absolute must. That's industry standard for engineering projects of all sizes. * There's most probably some computer-graphics software for making all those animations * All printed materials (instruction manuals, promotion, etc) must be prepared using some Adobe stuff - that's pretty match standard too * 3D drawing must be photo-realistically rendered ... and I'm sure there are others.
  20. xlib
    The answer is of cause "No". You _already_ can create bricks fully compatible with Lego. Some Chinese shops have it available: http://www.aliexpress.com/item/Sluban-Building-Blocks-Compatible-with-Lego-City-Fire-Station-Truck-Helicopter-Firefighter-Minifigure-learning-Education-toys/32337468015.html TLG keep selling not because it's somehow illegal to create compatible bricks.
  21. xlib
    Extremely unlikely. First, LDD, as a CAD program is not very useful for industrial design. But, since Lego don't have shortage of parts - I believe they design their sets physically. The only reason for them to use _any_ CAD program at all is for designs with new parts. And for those LDD is completely inadequate. Now as LDD reverse engineering suggests, internal parts database seems to have some other uses since it have more information that needed for simple 3D rendering. So maybe there's some kind of CAD program used internally. And maybe it shares rendering engine with LDD.
  22. xlib
    LDD is indeed CPU hog, but truth have to be told: any CAD model made from 25K parts (be it Autocad, Solidworks or even electronic schematics) will put your computer to its limit. This is even more true for 3D-presenting programs.
  23. xlib
    Since when company's (any company) customer service is tasked in answering question about future plans? Those plans usually are confidential and customer service doesn't comment about them. Phrase "there are no planned updates" means exactly that: no updates was announced.
  24. xlib
    At a times of such loss, question of man's legacy always arise. If someone can talk to his family, get the source with permission to make it open source - I think many people (me included) will help to keep it alive.
  25. xlib
    That is implementation - dependent, and for sure can be done in loader. In your example of car, lego worlds loader can easy distinguish wheel from brick and make one rolling. It is tricky in case of interlocked parts (gears, axles, etc) but definitely possible.