 | | Re: Standardized Inventory File Format?
|
|
(...) I don't suppose I'd have a problem myself. My code is a little messy, but it (usually) gets the job done. I was thinking of other people, who may have recorded inventories in spreadsheets, or HTML, or whatever document format they found handy. (...) (27 years ago, 5-Oct-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
(...) I am not sure I understand your question completely. There certainly are XML-writers available. One is included in the new Java extension Project X available from Sun at (URL) You probably have to register, but that is free and pretty simple. (...) (27 years ago, 4-Oct-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
(...) Hmm, interesting. Are there any XML writers, to convert flat-ASCII to flat-XML? Steve (27 years ago, 4-Oct-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
(...) Why not adopt XML? Watching this thread, I have seen discussions about parsing such inventories in different programming languages and about the fact that it should be readable by human beings. XML is designed exactly for that. There are a (...) (27 years ago, 3-Oct-99, to lugnet.db.inv)
|
| |
| | 8251 Sonic Cycle
|
|
This set may have been inventoried before, but I couldn't find it, so I made my own. Notes: (1) 'gray' is the American spelling, 'grey' is the British spelling. (2) dk = dark (3) tr = transparent/translucent (4) The flexible tubes were probably (...) (27 years ago, 2-Oct-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
(...) I wasn't speaking for myself--I could learn Perl, if I wanted. I haven't needed to yet, and haven't felt like making the time--other activities have higher priorities. I was thinking of people who aren't programmers, don't know how to program, (...) (27 years ago, 28-Sep-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
(...) Are you speaking for yourself? If so, explain why you'd rather use some other programming language system in place of Perl. Remember, we're trying to design a standard that will work for lots of people who aren't here to represent themselves. (...) (27 years ago, 27-Sep-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
Op een zekere dag, te weten Thu, 23 Sep 1999 13:54:23 GMT, klom blisses@worldnet.att.net (Steve Bliss) in het toetsenbord en schreef ons: (...) Excel (97) at least can import multi-char delimeters. In the import-window, you can choose the delimeter (...) (27 years ago, 25-Sep-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
(...) But any major dude with half a heart surely will tell you, my friend... - ABSie Dan (well. it seemed funny at the time, but I still have coaster hair so what do I know. Could be all the mosquitoes I inhaled while screaming.) -- Larry Pieniazek (...) (27 years ago, 25-Sep-99, to lugnet.db.inv, lugnet.off-topic.fun)
|
| |
| | Re: Standardized Inventory File Format?
|
|
Steve Bliss wrote in message <37ebce49.24708031@l...et.com>... (...) will do (...) I could easily write an inventory file formatting program to perform this task. It would give the user full control over how he/she wanted a file to be formatted, and (...) (27 years ago, 24-Sep-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
(...) But not every major user wants to run Perl. Steve (27 years ago, 24-Sep-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
(...) It doesn't do much good if the use of commas makes it so the columns don't line up. You want these inventory files to be easy to read by humans, and that means the columns need to line up! If we use commas as delimeters, we also need to add (...) (27 years ago, 23-Sep-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
(...) Yes -- the way to do that type of transformation in a single operation is to replace the grep expression / +/ with /,/. Of course, if you don't have grep replace in your text editor, get a real text editor (-: Just kidding! Every major OS can (...) (27 years ago, 23-Sep-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
(...) My parts database format is human-readable and well-suited to use by programs as well as humans, and solves your problem quite well. My inventory scripts use it. Look at: (URL) are some sample entries: ld2412, mr0055 Name: 1 x 2 tile with (...) (27 years ago, 23-Sep-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
Steve Bliss wrote in message <37ea300b.59491442@l...et.com>... (...) People may end up with multiple commas if there happens to be a gap of six or more spaces, then. Of course after replacing ' ' with ',', they could replace ',,' with ','. It might (...) (27 years ago, 23-Sep-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
(...) Look at (URL) The LDraw numbers are included there, and there are links to Technica and Lutz Uhlman's parts list. Steve (27 years ago, 23-Sep-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
(...) Are there many programs that support multi-character delimiters in their import function? I'm fairly certain Excel and MS-Access do not. The point of making a standard format is to make the data more accessible to everyone. Not just coders. I (...) (27 years ago, 23-Sep-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
John Cromer wrote in message ... (...) I'd start at (URL) and try printing the Word version of the parts catalog. M$IE garbled the images and then crashed badly on me when I tried viewing the HTML version from the zip file. Forced a reboot (I made (...) (27 years ago, 23-Sep-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
(...) This (...) Let's do it. 3 spaces between fields: count DATfilename Color Optional description Now, not being a CAD nut, where would I find the DATfilenames? And what do we put for parts without DATfilenames? as evah, John C. (27 years ago, 22-Sep-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
(...) I solve that problem by using *3 or more spaces* as the delimiter. If you want to delimit the next field, you must always use at least 3 spaces in a row. This allows things like color names to include spaces and allows for a little human error (...) (27 years ago, 22-Sep-99, to lugnet.db.inv)
|
