 | | Brickshelf Upload Utility
|
|
I've been working on a Brickshelf upload utility similar to (URL) Flickr Uploadr>. It helps streamline the process of zipping a bunch of files and navigating to or creating the appropriate folder to upload them. These screenshots are of a scruffy (...) (17 years ago, 30-Jul-07, to lugnet.publish, lugnet.cad.dev, FTX)
|
| |
| | Re: Search path question
|
|
(...) Hi Roland, Thanks for the input. Has anyone else implemented the mechanism the way Roland has? Kevin (17 years ago, 13-Jul-07, to lugnet.cad.dev)
|
| |
| | Re: Search path question
|
|
(...) The way I understand the file handeling system, this should not load. Because every file's references must be handled relative from the file being loaded (not to the main file). So calling sub/sub2.ldr from sub/sub1.ldr will look at (...) (17 years ago, 13-Jul-07, to lugnet.cad.dev)
|
| |
| | Re: Search path question
|
|
(...) I would also lean towards always requiring the subdirectory, but am open to argument the other way. ROSCO (17 years ago, 12-Jul-07, to lugnet.cad.dev)
|
| |
| | Re: Search path question
|
|
(...) I know that LPub would only know where to find sub2 if it was specified as sub/sub2.ldr. I think if there only being only one current working directory which is the directory where you've placed your top level model file. (...) This seems the (...) (17 years ago, 12-Jul-07, to lugnet.cad.dev)
|
| |
| | Search path question
|
|
I just noticed some unexpected behavior in LDView, and I wanted to ask here whether or not the behavior was right. Suppose you have the following files: TestModel.ldr Sub/Sub1.ldr Sub/Sub2.ldr TestModel.ldr contains a reference to Sub/Sub1.ldr. When (...) (17 years ago, 12-Jul-07, to lugnet.cad.dev)
|
| |
| | LDLink: reversibly merge part libraries
|
|
Hi, folks. After reading some of the recent posts discussing support for unofficial parts and part directories, I decided to release this script I wrote to help manage the unofficial parts I use. I keep my unofficial parts in a parallel part library (...) (17 years ago, 11-Jul-07, to lugnet.cad.dev.mac, lugnet.cad.dev)
|
| |
| | Re: Convention for directoried for unofficial parts?
|
|
(...) The following files in LDView's source tree contain the LDrawIni stuff: LDLoader/LDrawIni.c LDLoader/LDrawIni.h LDLoader/LDrawInP.h There's a #include <TCFoundation/TCDefines.h> near the top of LDrawIni.c. You can delete that; the only reason (...) (17 years ago, 10-Jul-07, to lugnet.cad.dev)
|
| |
| | Re: Convention for directoried for unofficial parts?
|
|
(...) I'm using Qt, and LPub is under GPL, so this sounds perfect. I'm all for standardization, so this sounds great. (...) I'm not looking to judge or criticize anyone. All of our programming efforts are works in progress, so these self analysis' (...) (17 years ago, 10-Jul-07, to lugnet.cad.dev)
|
| |
| | Re: Convention for directoried for unofficial parts?
|
|
(...) I agree (which is why I voted yes on the other proposal, although it's not an exact match for what you're asking for). Having said that, Lars did offer the INI parsing code, and since it's already in LDView (which is under GPL), anyone who (...) (17 years ago, 10-Jul-07, to lugnet.cad.dev)
|
| |
| | Re: Convention for directoried for unofficial parts?
|
|
(...) That makes sense to me too. Based on the coincidental informal convention already used by LDView and Bricksmith, I suggest $LDRAWDIR/Unofficial as the default unofficial parts directory. It is structured like the regular LDraw directory with (...) (17 years ago, 9-Jul-07, to lugnet.cad.dev)
|
| |
| | Re: Dear LSC, was: LDrawIni API (was: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths)
|
|
(...) That's because the LSC voted against it. Took me a while to find the discussion as well - and I knew it was out there! (URL) (17 years ago, 9-Jul-07, to lugnet.cad.dev)
|
| |
| | Re: Convention for directoried for unofficial parts?
|
|
(...) Get the best of both worlds and do both. Check for the environment variable and if it is blank (or non-existant) default it to a "known" sub-directory. W (17 years ago, 9-Jul-07, to lugnet.cad.dev)
|
| |
| | Convention for directories for unofficial parts?
|
|
To all developers, The LSC does not want to specify how unofficial parts are handled. Personally if find the recommendation that we pull down individual unofficial parts into the same directory as our LDraw file a hassle. Would the group prefer (...) (17 years ago, 9-Jul-07, to lugnet.cad.dev)
|
| |
| | Convention for directoried for unofficial parts?
|
|
To all developers, The LSC does not want to specify how unofficial parts are handled. Personally if find the recommendation that we pull down individual unofficial parts into the same directory as our LDraw file a hassle. Would the group prefer (...) (17 years ago, 9-Jul-07, to lugnet.cad.dev)
|
| |
| | Re: Dear LSC, was: LDrawIni API (was: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths)
|
|
----- Original Message ----- From: "Kevin L. Clague" <kevin_clague@yahoo.com> To: <lugnet.cad.dev@lugnet.com> Sent: Monday, July 09, 2007 5:56 PM Subject: Dear LSC, was: LDrawIni API (was: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths) (...) (...) (17 years ago, 9-Jul-07, to lugnet.cad.dev)
|
| |
| | Dear LSC, was: LDrawIni API (was: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths)
|
|
(...) Dear LSC, I examined the LDraw website and was unable to find formalization for the support of optional part paths. I'm updating LPub and would like to include support for this concept of alternate paths for LDraw parts. The PRE and POST (...) (17 years ago, 9-Jul-07, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) Hello All, First I am no part designer but reading through this discussion I got an idea that might be interesting to share. First I think Orion is right with his stand to not allow povcode because of the 'why only pov-ray' argument. So I was (...) (17 years ago, 2-Jul-07, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) Since I've contributed exactly two official parts to the LDraw library (neither of them with inlined POV-Ray code), I'm sure that my opinion carries more weight than anyone's on the subject... :) For some time it has been argued that the use (...) (17 years ago, 2-Jul-07, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) I'd _like_ to see a meta-language for basic shapes defined in their primitives (the current naming system would be fine if it was consistent) as that could be used in converter software of all hues. I also realise this isn't likely to happen (...) (17 years ago, 1-Jul-07, to lugnet.cad.dev)
|
