Re: plugin plans

On Fri, Feb 13, 2015 at 11:00:32AM -0500, al davis wrote:
> On Tuesday 10 February 2015, Felix Salfelder wrote:
> > > To enable this, there needs to be enhancements to the load 
> > > command to load whole directories.  I am working on this
> > > now.
> > 
> > loading directories sounds interesting. why not just include
> > a command file that attaches the desired ones? like in
> > $ gnucap
> > reads user rc (if esists) system rc otherwise. these load
> > plugins. or just
> > $ gnucap --rc ~/.gnucap/my_alternative_rc
> > or similar, to customize....
> 
> too much work for user.

i see. don't know if i agree. but i DO agree that usability is a
concern.

currently gnucap does not locate gnucap.rc in a useful way. i have
experimented with this in gnucap-uf, essentially it looks in cwd and
parents first. also it changes cwd to the location of the included file,
so transitive includes are working. this is not as simple as i wished...

about apache style: where is this going to be installed to?  it makes
some sense to have per-project configurations, hence per-directory. are
you proposing to copy around symlink trees instead of just rc files? i'm
not sure how this reduces the work for the user.

> The real point here is the break up gnucap-default-plugins to 
> allow post-install individual choice, and to put user plugins or 
> package plugins on an equal level.

this reminds me of python... python does not use apache-style.

> package plugins ... like the spice model packages.  JFET, BSIM4, 
> etc. .. needs to look built-in.

currently i do for example (after installing the plugins)
$ gnucap -a bsim303.so
in a similar way we should have
$ gnucap -i spice-bsim
and i think spice-bsim should make use of a *text* file provided by
gnucap-bsim. that is close to what python does.

cheers
felix