Rev 224 | View as "text/plain" | Blame | Compare with Previous | Last modification | View Log | RSS feed
== see the PLANNING document for more information ==
== new document used to describing some implementation plans ==
== BOM - Bill Of Materials system ==
We want the schematics and there symbols to stay as molecular as possible.
Howerver we want to be able to create an extended automated bill of materials
This list should contain at leased the following information:
make bom (all, is default)
make bom "refdefs,value,description,footprint,supplier,order-number,price" (example)
output document can be plain text and as landscape pdf document
- refdefs
- value
- device
- description
- footprint
- supplier
- order-number
- price
- quantity
- catalog page
- manufacturer
- manufacturer-number
- websitelink-supplier
- datasheetlink-supplier
- websitelink-manufacturer
- datasheetlink-manufacturer
I think its to much info to add all this information as attributes to the symbols,
this also decrease interoperability.
So i would suggest parsing an external document for the component information.
example, symbols had the below attributes
- refdef
- value
- device
- footprint
- information ../../doc/ETHERNET/ENC28J60/information.txt
now the file ../../doc/ETHERNET/ENC28J60/information.txt is parsed to get all the other information
format:
line-one=supplier
line-two=manufacturer
line-third=order-number
line-four=manufacturer-number
line-five=description
line-six=websitelink-supplier
line-seven=datasheetlink-supplier