gEDA-dev: geda naming convention

[Ryan]

I wouldn't mind writing a script to do this but here's the problem: Do I
then go around the EE dept. here at the University and tell people I
recommend this software but you will need my custom, unofficial script
to lessen the learning curve. People aren't going to go for this. So
many suggestions here go round and round and end up in the
write-your-own-script-if-its-not-good-enough bin. I agree in many cases
(when someone wants a strange feature), but if it might potentially
attract new users into the group without disturbing the few gurus here -
why not? Both gschem and pcb are very usable in their current state -
but if we had some user interface guidelines to make the programs feel
the same, combined with some sense of integration; this project would
get the publicity it deserves and compete with some of the more popular
design suites. Anyway, just a few ideas - I am not asking anyone to
alter their lifestyle.

Ryan


> If you want to write a script go right ahead just don't make in
> manditory. Else I wil have to make an even more custom version to make
> it non-manditory.
>
> Other wise sure as long as you are having fun,
>
> Steve Meier
>
> Ryan wrote:
>   
>>> /usr/bin/geda could be a simple shell script that parses command line
>>> arguments and calls the right tool(s) on the old name. This way existing
>>> makefiles and user habits wouldn't break while we could have a general
>>> geda command.
>>>
>>>
>>>
>>>   
>>>     
>>>       
>> You can also add addition options in the script - such as a help command
>> that will display all existing programs/scripts tied to gEDA. The
>> "geda-" prefix would be easier in the sense that a shell script could be
>> replaced with symbolic links and allow the user to TAB a few times to
>> see what's available. On the other hand, a script could provide a solid
>> base for more advanced capabilities later on.  Also, some structured
>> naming convention would provide a start for people who might contribute
>> scripts to the project - some set of guidelines, if this doesn't already
>> exist.
>>
>> Ryan
>>
>>
>>
>> _______________________________________________
>> geda-dev mailing list
>> geda-dev at moria.seul.org
>> http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
>>
>>   
>>     
>
>
>
> _______________________________________________
> geda-dev mailing list
> geda-dev at moria.seul.org
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
>
>