Mail Archives: geda-user/2014/03/12/08:17:33
Britton Kerin:
> On Tue, Mar 11, 2014 at 2:15 PM, <karl AT aspodata DOT se> wrote:
...
> > Gschem should pick the sym from the right author and extract the right
> > version (without manual intervention).
>
> The fact that gedasymbols is still on CVS shows pretty clearly how far there
> would be to go to get a symbol library with the features you're thinking of.
> Clearly its not enough of a priority for anyone to get a lot of attention.
Ohh, forgot that, you need a network connection for that to happen,
does not suit me at all, I'm on a dialup connection...
The repo. really needs to move to a distributed version handler to be
able to care for people like me.
...
> >> So your case for the "in the file library" solution is:
> >> >
> >> > 1, solve same name problem
> >> > 2, get some reliability against sym file changes
> >> >
> >> And make this without manual activity.
> >
> > Agreed.
> >
> >> 3, and distribution
> >> >
> >> Am I right?
> >> >
> >> Yes.
> >
> > Good, can we do that without any copying ?
>
> Maybe but copying is the easiest way. Its not even that inappropriate for
> hardware, since you want a pretty hard freeze once you have things working.
> I'm not convinced the concern over clone-and-modify destructiveness applies
> well here. For one thing there isn't that much out there to destroy.
> For another I don't think modifications in subdesigns would cause that
> much harm: the only cost would be lost effort that could have improved the
> root symbol. Symbols are relatively simple compared to other software, and
> at some fairly early point in development can be considered "good enough".
Current situation makes it problematic to put your symbols in a
repository, since there, at least what gschem sees, is only the last
version. You are more or less forced to copy out the symbol to a
project dir.
If it was easier to compare symbols, it would lessen the problem with
having "all thoose" copies around.
Let's say I have all my stuff in /dir, the tool finds all thoose
diode.sym, here's a list of all that are identical, this one differs in
that attribute and that one differ in graphic, shown in an overlayed
picture...
> And it would still be a huge efficiency improvement over the amount of
> reinvention that goes on in the current situation.
I don't follow you here. What are are you reffering to with "it" and
"reinventaion".
> >> Also minus is that all these solutions are distributed.
> >> There are thousands of scripts to make any changes to the schema file.
> >> Only refdesrenum-like scripts are about 10, maybe 100.
> >> But there is no one place where collected their descriptions.
> >
> > Well, it means that there is an ecosystem around gschem. It could
> > mean that there might be something missing in gschem, but could also
> > be that it easy to make thoose scripts and adapt to a new problem, and
> > that is a strenght.
>
> My Makefile+scripts is 1600 lines and its all doing the obvious stuff that
> everyone else must be doing also in some slightly different incompatible way,
> its just a waste
...
It "just" takes someone to donate their time to identify thoose "ovious
stuff", put them into perspective, make a prototype implementation, ask
users all along about the direction, and either become a developer or
somehow make a developer interested in your stuff.
Isn't that the common problem with open source, if you are not doing
it, it won't be realized.
Regards,
/Karl Hammar
-----------------------------------------------------------------------
Aspö Data
Lilla Aspö 148
S-742 94 Östhammar
Sweden
+46 173 140 57
- Raw text -