Subversion Repositories OpenARM Single-board Computer

Rev

Rev 224 | Details | Compare with Previous | Last modification | View Log | RSS feed

Rev Author Line No. Line
224 jelle 1
== see the PLANNING document for more information ==
2
 
3
== new document used to describing some implementation plans ==
4
 
5
== BOM - Bill Of Materials system ==
6
 
7
We want the schematics and there symbols to stay as molecular as possible.
8
Howerver we want to be able to create an extended automated bill of materials
9
This list should contain at leased the following information:
10
 
11
make bom (all, is default)
12
make bom "refdefs,value,description,footprint,supplier,order-number,price" (example)
13
 
14
output document can be plain text and as landscape pdf document
15
 
16
- refdefs
17
- value
18
- device
19
- description
20
- footprint
21
- supplier
22
- order-number
23
- price
24
- quantity
25
- catalog page
26
- manufacturer
27
- manufacturer-number
28
- websitelink-supplier
29
- datasheetlink-supplier
30
- websitelink-manufacturer
31
- datasheetlink-manufacturer
32
 
33
I think its to much info to add all this information as attributes to the symbols,
34
this also decrease interoperability.
35
 
36
So i would suggest parsing an external document for the component information.
37
 
38
example, symbols had the below attributes
39
 
40
- refdef
41
- value
42
- device
43
- footprint
44
 
45
- information ../../doc/ETHERNET/ENC28J60/information.txt
46
 
47
now the file ../../doc/ETHERNET/ENC28J60/information.txt is parsed to get all the other information
48
 
49
format:
50
line-one=supplier
51
line-two=manufacturer
52
line-third=order-number
53
line-four=manufacturer-number
54
line-five=description
55
line-six=websitelink-supplier
56
line-seven=datasheetlink-supplier