 | | Re: Planes & Requirements for a generic download-tool
|
|
Ok I do not have a problem with http ... so as it looks we are going to use http with some informational files ... just for my understanding ... what the matter with ldraw.org and ftp ? Have I missed something ? Michael Steve Bliss (...) (24 years ago, 15-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: eliminating polygons?
|
|
(...) Thanks! I guess I'll have to get pretty involved in the in-to's and out's of part- making. I'm kind of lazy. I thought there might be an easy way of doing it. Anyway, I shouldn't infringe on the LDraw organization, since they're their parts, (...) (24 years ago, 15-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: Planes & Requirements for a generic download-tool
|
|
(...) We can always either: a. Enable directory listings for the appropriate directories. b. Supply a parts.dir file, containing the directory listing. BTW, unless something radical changes with the current situation, FTP is the wrong way to go for (...) (24 years ago, 14-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: Planes & Requirements for a generic download-tool
|
|
Yes I know, with Win32 it's easy no matter if it's http or ftp, but is it also under Unix? I would like to keep the source as portable as possible. In general it doesn't depend on the protocol, but getting directory listings from ftp servers is (...) (24 years ago, 14-Jul-00, to lugnet.cad.dev)
|
| |
| | Re: Part Command (1)
|
|
Ok unless my new parsing-routine is ready I will replace the spaces by underlines as a work-arround since I found out the real problem is the space in the file-name. MLCad stops after reading the first word ... has the halfe file-name and cries that (...) (24 years ago, 14-Jul-00, to lugnet.cad.dev)
|
