| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
create-order: Adding an option for a strategy to ignore/modify parts.
ninja/init: Moving strategy from ninja to init so they're more
persistent.
|
| |
|
|
|
| |
o Showing all unresolved parts first in the report.
o Showing all MPNs and SPNs for unresolved parts.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
o Renaming <part-uri> to <part-reference>.
o Adding <supplier> on <part>, removing from <supplier-part-number>. A
part can have exactly one part.
create-order:
o Creating anonymous part objects, with two references, one schematic
reference and one part-uri reference to the selected part.
o Redoing how the order is calculated with the new ObjDb structure.
ee.part.Part:
o Absorbing bom_file_utils into Part. Much better wrapper object around
the xml goop.
|
| |
|
|
| |
ninja: Name the generated .rst file for orders too.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
o Adding <link> list on <part>. For media, datasheets etc.
digikey:
o Parsing out media.
PartDb:
o starting on a more generic object db with indexes.
order:
o Using the new object db for building data while resolving parts.
o Creating a report from the order.
|
| | |
|
| |
|
|
|
|
|
|
| |
o Renaming part.id to part.uri. Changing to URIs and use that as an
identifier if the part is known. Schematic part does not have an URI.
o Merging <schema-reference> and <part-numbers> into <references>
o Creating <part-uri> as a possible <reference>. Used by order to point
to other parts.
|
| |
|
|
| |
<part-db> document.
|
| | |
|
|
|
o Starting on functionality create orders. Very WIP.
o Adding a concept of an "ee project". Can load a gitconfig-like config
file.
o Adding a tool to import a yaml file into a part xml file.
|
