|
|
 | | Re: Partsref is Moving to LUGNET
|
| (...) This is kludgy but might work. Details left as an exercise. Your problem is that what you want is to know when a file is *new to YOU* not what it's timestamp is. Keep two complete sets of .dat files. One is an image of the state of files, but (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
| | | | | Re: Partsref is Moving to LUGNET
|
| (...) You could try the version which comes with Cynwin32: (URL) used Beta 20.1; it seems pretty stable. If you're not too keen on using the Unix sub-layer (slow), try dmake: (URL) it seems to have gone commercial -- you have to *pay* for the (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
| | | | | Re: Partsref is Moving to LUGNET
|
| (...) Yep, I'm familiar with make. I even went to look for one once. Do you know how hard it is to search the net for 'make'? I never could figure out a decent set of search-words... Oh, wait. I've got a make.exe with my old copy of Turbo Pascal. (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
| | | | | Re: Partsref is Moving to LUGNET
|
| (...) Are you familiar with the make utility? It allows you to describe an arbitrary set of modules, with their associated interdependencies, and then re-build only the modules which have changed and modules dependant upon them. Of course, using (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
| | | | | Re: Partsref is Moving to LUGNET
|
| (...) That's fine with me. The only downside is applying updates. When new parts are released for LDraw, I don't update individual partsref images and pages, I just regenerate the whole shebang. So any manual edits would probably get overwritten. (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
|
|
