Mail Archives: geda-user/2015/02/15/05:15:27
On Sun, 15 Feb 2015, karl AT aspodata DOT se wrote:
> Lev:
> ...
>> My wish list is: ...or work I'd do if I had the time:
> ...
>
Ohh, and the wishlist...
For PCB I don't have any (I maintain my own fork where I implement what I
need and won't have to convert to C++).
For gschem, I don't have anything that's top urgent, the tool is almost
perfect for my needs. There are some minor things, tho. Except for the
language-related ones they are so minor that before this thread I didn't
even consider posting them:
- 'en' prints all symbol stuff but it's then too crowded and hard to read.
For normal attributes the editor window is fine, but I haven't found a way
to display (or edit) pin attributes in-situ. Maybe a tab on the attribute
editor window for the pins?
- support for non-scheme scripts; I have my own favorite non-popular
language (awk) which I don't expect to be supported, but honestly,
I'd be happy with anything mostly procedural (e.g. tcl, lua, python)
- at least one complex backend rewritten in such a non-scheme/non-lisp
language, to serve as an example to those who want to write their own.
Preferably a backend in common use should be the victim and the scheme
variant should be removed so that the rewritten code has more chance to
stay up to date long term
- once we have such a scripting language, I'd like it to be embedded in
the UI. Not necessarily as a text editor where I can change my scripts on
the fly, but as a way to extend the GUI. Like if I want to have my own
renumbering, I can write my fewliner and bind it to a menu and key combo,
restart gschem and it's there.
- default configs shipped with the project should always support finding
stuff in the local project directory, and this should be the highest prio
search path. There should be an option provided to disable this feature
(or replace the search path or remove named directories, whatever).
In my practice I always want the project dir on search path, can't recall
a single situation where this would have hurt me so I find it a bit
suboptimal I have to set this up manually on a fresh install. Might be
something highly dependent on personal preferences (I don't want to
trigger a flame war).
- really really low prio: the file format could be made more text editor
friendly in the sense of more indentation and less magic numbers. For me,
being able to fool around in the source of CAD files is a big plus.
- very low prio: some optional, easily switchable graphical mark to see
which symbols are embedded or even better, which symbols are coming from
what search path. This would help me deciding what to embed before I share
my sch.
Regards,
Igor2
- Raw text -