Re: gEDA-user: [RFC 3/6] Embedding system revamp

[John Griessen <john@xxxxxxxxxxxxxx>]

Peter TB Brett wrote:
> On Saturday 17 January 2009 15:56:03 Ales Hvezda wrote:
>> [snip]
>  However, what happens if a
>>    user does want N different versions of the same symbol embedded?

I can't seea good enough reason for that... it's not an automatable workflow.

> 
> Quite a lot of people have requested being able to edit embedded 
> symbols "in-place", and on "closing" them (e.g. by up-hierarchy), to update 
> the instances in the top-level schematic.
.
<snip>
> How would we "save" it? With the new embedding approach, we can:
> 
> 1. Save the PAGE to a memory buffer, and copy it into the store of embedded 
>    files.
> 
> 2. Call the "resolve components" function (see my spec).
.
.
> 
> Another thing this enables: because we now have an easy-to-get-at list of 
> embedded files, we can "catch" attempts to insert a library component with 
> the same name as an embedded component, and offer the user some options for 
> resolving the conflict.
> 
> Finally, *if* someone wanted the option to embed all symbols by default, this 
> makes it much easier to enable that behaviour for them.

I can see another workflow that uses the above functions.  Start with a schematic you want to reuse,
copy it, have it embed symbols, make changes, update embedded symbols.

Then add one new feature -- export embedded to local project dir.  That would be useful to act on one symbol or
all symbols in a schematic.   The schematic would look the same and netlist the same.
It might be just a skeleton with missing pieces to serve
as a starting point, and now you add in library symbols to complete it.  Switch back and forth from embedding or using local
project dir plus library symbols as needed.

This brings up the concept of library search paths -- the project dir should be first, then library dirs for this project 
workflow, so that needs defining somewhere -- ./gafrc

Do our component library specification lines act in the order they are in the gafrc file?

For instance:


(component-library "${HOME}/EEProjects/ecosensors-pub.git/gschem-cibolo/two-terminal")
(component-library "${HOME}/EEProjects/ecosensors-pub.git/gschem-cibolo/thru-hole")

do my two-terminal symbols of the same name get used, or the thru-hole ones?

John

-- 
Ecosensory   Austin TX


_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user