[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gEDA-dev: geda naming convention



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


Stuart Brorson wrote:
> I'll second Ryan's idea.  I think that it would help newbies if gEDA
> were to act like svn, say.  That is, svn gives you a lot of tools to
> perform various tasks, and you invoke them all like this:
>
> svn foo <args>
> svn bar <args>
>
> I would propose that the following system would work quite well:
>
> geda          -> brings up xgsch2pcb project browser, from where
>                   you can run any of the tools by selecting the
>                   correct menu option.
> geda gschem   -> command line symlink to gschem
> geda gattrib  -> command line symlink to gattrib
> geda pcb      -> command line symlink to pcb
> etc.
>
> This would help unify the gEDA suite in people's minds.  Also, if some
> tools need certain environment variables set (i.e. search paths in
> some future library system), then "geda" would be a script which would
> first set the env vars, and then invoke the corresponding program.
>
> I don't think we should do away with the straight command-line
> invocation of the programs, though.  Rather, the above scheme would
> supplement what we already have.
>
> Stuart
>
>
>
>
> On Sun, 9 Dec 2007, Ryan wrote:
>
>   
>> Has anyone here ever considered using a consistent naming scheme for gEDA's countless glue-scripts and general programs? It would seem very useful to adopt a naming convention similar to the git source control package - such as geda-pcb, geda-gattrib, geda-gsch2pcb, etc.. . This would allow the user to simply type "geda-" and use the tab for name completion; thus providing a method for users who don't use gEDA on a daily basis to stop trying to remember all of these odd-ball script names. I also think many new users are discouraged because, at first glance, they see a ton of seemingly unrelated programs and think, "I have to learn all of this to create a simple board?". I find the software very useful and would like to encourage others (students and professors at my University) to learn, but in my experience people are short on time and many have the point-and-click mentality that comes with  almost all EDA software these days. Anything to lessen the learning curve and impr
>>     
>  ov
>   
>> e the new user experience is sure to bring many more people on board - and makes my task of promoting the software more convincing to those reluctant to try anything else.
>>
>> Thanks,
>> 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
>
>   




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