To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cad.devOpen lugnet.cad.dev in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / Development / 8244
8243  |  8245
Subject: 
Re: lsynthcp community development project setup on sourceforge
Newsgroups: 
lugnet.cad.dev
Date: 
Mon, 20 Jan 2003 16:02:10 GMT
Viewed: 
994 times
  
In lugnet.cad.dev, Don Heyse writes:
In lugnet.cad.dev, Kevin Clague writes:
Hopefully the sourceforge effort will also get some folks that can help me
with the mathematical ins and outs of the effort.

I don't know about the math, but I do have a few thoughts after a quick
peek at the sources.  So how should we go about making changes?  Discuss
them here first, or just put them in CVS with an appropriate comment if
we think they won't break anything.

I'd like to discuss changes before they are made, so I can keep track of new
capabilities of the program.


I contacted Michael about lsynthcp support in MLCAD, but he was already
wrapping up the 3.0 release.  I'm hoping that he integrates it in a future
release.  The core synthesizer is actually a command line program, making it
easier to integrate into MLCAD than if it were GUI based.

I don't know about MLCAD, but most of my current ideas relate to making
it easier to integrate lsynthcp into other stuff.

I don't think main() should do the fputs() on the uppercased line.
Remember the thread here about not making unnecessary changes to the
files.

   Yes. I was trying to make lsynth not case sensitive when it came to
recognizing keywords, but I don't like the fact that it changes every line.


Perhaps there could be an option to only dump the SYNTH portions, and
dump them to separate files based on an optional FILENAME at the end of
the SYNTH BEGIN line.

This sounds good.  We need to be careful about how we describe optional
parameters though.  I know we want to add a length parameter, now filename,
and I'm sure there will be others.  I think that positional parameters may
be a real hassle.  How do you feel about named parameters
(FILENAME="foo.dat", LENGTH=20, UNITS=CM)?


Optionally read from stdin, write to stdout so it can be used as a pipe.

Sounds reasonable.


I'm not sure yet when I will move LPub to sourceforge, but it will most
likely end up there.

You might also want to think about putting the installer program there.

OK.


Don

Kevin



Message has 2 Replies:
  Re: lsynthcp community development project setup on sourceforge
 
(...) Yeah, I thought so. Other options are copying the line before the strupper(), or using strnicmp() or strncasecmp() for the keyword test. The copy method is easier to do in a portable way. (...) I like the named parameters. That makes it easy (...) (22 years ago, 20-Jan-03, to lugnet.cad.dev)
  Re: lsynthcp community development project setup on sourceforge
 
(...) What about getopt() style parameters, eg: -f foo.dat -l 20 -u cm --filename foo.dat --length 20 --units cm ROSCO (22 years ago, 20-Jan-03, to lugnet.cad.dev)

Message is in Reply To:
  Re: lsynthcp community development project setup on sourceforge
 
(...) I don't know about the math, but I do have a few thoughts after a quick peek at the sources. So how should we go about making changes? Discuss them here first, or just put them in CVS with an appropriate comment if we think they won't break (...) (22 years ago, 20-Jan-03, to lugnet.cad.dev)

19 Messages in This Thread:





Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR