Re: gEDA-dev: geda naming convention

[Steve Meier <smeier-at-NOSPAMalchemyresearch_dot_com>]

I use gschem, mra-netlist, pcb and gerbv daily not to mention backnet
and a few other custom commands.

I fail to see how puuting all of them together would help me know what
they are only to find them. Since I CAN READ putting them all together
on a web page is as effective as giving them all the same prefix. Sorry
I see no benefit off giveing them the same prefix it would be as useless
as trying make linux into gnu/linux. But fear not I am fairly capable
call them what you like I can allways rename then for my ease of useage.

Steve Meier

Ryan wrote:
> Steve Meier wrote:
>   
>> What?
>>
>> so this would change me from typing
>>
>> gschem top.sch
>>
>> to
>>
>> geda gschem top.sch
>>
>> Well I am far to lazy to do that, though if others want to go ahead. But
>> it makes no scense to me. Also it seems to mush like
>>
>> mother may I gschem top.sch
>>
>> Steve meier
>>
>>   
>>     
> If you use only gschem - well that's wonderful. Why even name the
> project gEDA, let's just call it gschem and keep it simple. My point is
> that you have so many scripts/programs that are scattered - I would bet
> you couldn't name even half of them. Just from browsing, I found the
> following:
>
> gsch2pcb
> gschupdate
> gschemdoc gschem
> gschlas
> pcb pcb_backannotate
> gattrib
> gnetlist
> gsymcheck
> tragesym
> gerbv
> pcb_backannotate
> refdes_renum
> gschupdate
> gnet_hier_verilog.sh
> pads_backannotate
> sarlacc_sym
> gnucap
>
> I am sure some of you may claim that these are totally separate,
> unrelated programs which only furthers the point. Is there anyone out
> there who even knows how many of these useful programs/scripts exist?
> Maybe a handful of people - that's my guess. If the old names were left
> in place (as mentioned) and a simple prefix "geda-" or the other
> mentioned method were used, it seems things would be much easier to
> locate and better organized for the future. If someone doesn't, at a
> minimum, put some sort of organized method of naming scripts related to
> this project, then you guys might make better headway by stringing beads
> together and designing a gEDA dictionary that we can wear around our
> necks for quick reference. We may be able to sell them to large
> corporate firms with custom bindings displaying their logo and then
> follow-up with full day seminars explaining the reasoning behind the
> current naming scheme and how to efficiently use this new dictionary.
> Well, enough of the BS for now - but I hope someone understands.
>
> Ryan
>
>
>
> _______________________________________________
> geda-dev mailing list
> geda-dev@moria.seul.org
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
>
>   



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