 | | | | | |
In lugnet.cad.dev, Larry Pieniazek writes:
> In lugnet.cad.dev, Kevin L. Clague writes:
> > In lugnet.cad.dev, Larry Pieniazek writes:
>
> > > Except for time/skill/interest. (mostly time)
> >
> > I assume the lack of interest is in the coding, not the using :^)
>
> Ya. I have made good use of LSynth for hoses and for rubber bands in my
> current project and found it easy to use so I'm definitely interested in
> using it!!!!
>
> > I have a similar lack of time.
>
> OK, well maybe you've shamed me into taking a look. I just went to sourceforge
> (http://sourceforge.net/projects/lsynth/) but I'm not seeing the code there.
> Am I looking in the wrong place? Not saying I'll GET any time to look at
> this anytime soon, mind you.
Sorry, not intending to shame you.
You are looking in the right place, but I'm a neophyte on source forge.
Don, what have I failed to do?
Thanks,
Kevin
| | | | | | | | | | | | | | | |
| |
|
In lugnet.cad.dev, Kevin L. Clague writes:
> In lugnet.cad.dev, Larry Pieniazek writes:
> > OK, well maybe you've shamed me into taking a look. I just went to >>sourceforge (http://sourceforge.net/projects/lsynth/) but I'm not
> > seeing the code there. Am I looking in the wrong place?
>
> You are looking in the right place, but I'm a neophyte on sourceforge.
>
> Don, what have I failed to do?
I'm not sure. What are you trying to do? If just you're looking to
browse the code, then follow the "Browse CVS" link near the bottom
of the page at the URL given above. If you want upload changes to
the code you'll have to get a CVS program of some type. I use tkCVS
because it's a platform neutral GUI and includes the fabulous tkDiff
program, but there's also WinCVS, plain old command line CVS, and
several others.
Speaking of changes. Apparently I made some changes to my local copy
of main.c a while back, but didn't check the changes into the CVS
archive because you never came up with a policy for that. Do you
want to verify official changes via email before check in? Or would
you prefer to allow experimental code in the CVS archive and then
back it out if you don't like it?
Also, what do you want to do about releases? Do you want me to
package a source release for the 1.0 code? For executable packages
I set the homepage link to go to your website.
Don
| | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad.dev, Don Heyse writes:
> In lugnet.cad.dev, Kevin L. Clague writes:
> > In lugnet.cad.dev, Larry Pieniazek writes:
> > > OK, well maybe you've shamed me into taking a look. I just went to • sourceforge (http://sourceforge.net/projects/lsynth/) but I'm not
> > > seeing the code there. Am I looking in the wrong place?
> >
> > You are looking in the right place, but I'm a neophyte on sourceforge.
> >
> > Don, what have I failed to do?
>
> I'm not sure. What are you trying to do? If just you're looking to
> browse the code, then follow the "Browse CVS" link near the bottom
> of the page at the URL given above. If you want upload changes to
> the code you'll have to get a CVS program of some type. I use tkCVS
> because it's a platform neutral GUI and includes the fabulous tkDiff
> program, but there's also WinCVS, plain old command line CVS, and
> several others.
>
> Speaking of changes. Apparently I made some changes to my local copy
> of main.c a while back, but didn't check the changes into the CVS
> archive because you never came up with a policy for that. Do you
> want to verify official changes via email before check in? Or would
> you prefer to allow experimental code in the CVS archive and then
> back it out if you don't like it?
Letting me peek at the changes would be cool, but feel to check it in.
>
> Also, what do you want to do about releases? Do you want me to
> package a source release for the 1.0 code? For executable packages
> I set the homepage link to go to your website.
Will you package a source release please?
>
> Don
Thanks,
Kevin
| | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad.dev, Kevin L. Clague writes:
> In lugnet.cad.dev, Don Heyse writes:
> > In lugnet.cad.dev, Kevin L. Clague writes:
> > > In lugnet.cad.dev, Larry Pieniazek writes:
> > > > OK, well maybe you've shamed me into taking a look. I just went to • sourceforge (http://sourceforge.net/projects/lsynth/) but I'm not
> > > > seeing the code there. Am I looking in the wrong place?
> > >
> > > You are looking in the right place, but I'm a neophyte on sourceforge.
> > >
> > > Don, what have I failed to do?
> >
> > I'm not sure. What are you trying to do? If just you're looking to
> > browse the code, then follow the "Browse CVS" link near the bottom
> > of the page at the URL given above. If you want upload changes to
> > the code you'll have to get a CVS program of some type. I use tkCVS
> > because it's a platform neutral GUI and includes the fabulous tkDiff
> > program, but there's also WinCVS, plain old command line CVS, and
> > several others.
> >
> > Speaking of changes. Apparently I made some changes to my local copy
> > of main.c a while back, but didn't check the changes into the CVS
> > archive because you never came up with a policy for that. Do you
> > want to verify official changes via email before check in? Or would
> > you prefer to allow experimental code in the CVS archive and then
> > back it out if you don't like it?
>
> Letting me peek at the changes would be cool, but feel to check it in.
I think I'll email it to you first this time. It looks like I must have
implemented some of the changes mentioned in this thread here.
http://news.lugnet.com/cad/dev/?n=8250
There's a fix for the UPPERCASING bug and some stuff for UNITS, LENGTH
and subfile NAMEs, but I don't remember all the details, such as whether
or not I actually finished.
Do you have a nice colorized diff program so you can quickly asses
the changes? I use tkDiff myself.
> > Also, what do you want to do about releases? Do you want me to
> > package a source release for the 1.0 code? For executable packages
> > I set the homepage link to go to your website.
>
> Will you package a source release please?
Ouch. I was afraid you'd ask for that. Packaging official sourceforge
release files is one of those things I haven't done often enough to
remember how.
| | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad.dev, Don Heyse writes:
> In lugnet.cad.dev, Kevin L. Clague writes:
> > In lugnet.cad.dev, Don Heyse writes:
> > > In lugnet.cad.dev, Kevin L. Clague writes:
> > > > In lugnet.cad.dev, Larry Pieniazek writes:
> > > > > OK, well maybe you've shamed me into taking a look. I just went to • sourceforge (http://sourceforge.net/projects/lsynth/) but I'm not
> > > > > seeing the code there. Am I looking in the wrong place?
> > > >
> > > > You are looking in the right place, but I'm a neophyte on sourceforge.
> > > >
> > > > Don, what have I failed to do?
> > >
> > > I'm not sure. What are you trying to do? If just you're looking to
> > > browse the code, then follow the "Browse CVS" link near the bottom
> > > of the page at the URL given above. If you want upload changes to
> > > the code you'll have to get a CVS program of some type. I use tkCVS
> > > because it's a platform neutral GUI and includes the fabulous tkDiff
> > > program, but there's also WinCVS, plain old command line CVS, and
> > > several others.
> > >
> > > Speaking of changes. Apparently I made some changes to my local copy
> > > of main.c a while back, but didn't check the changes into the CVS
> > > archive because you never came up with a policy for that. Do you
> > > want to verify official changes via email before check in? Or would
> > > you prefer to allow experimental code in the CVS archive and then
> > > back it out if you don't like it?
> >
> > Letting me peek at the changes would be cool, but feel to check it in.
>
> I think I'll email it to you first this time. It looks like I must have
> implemented some of the changes mentioned in this thread here.
>
> http://news.lugnet.com/cad/dev/?n=8250
>
> There's a fix for the UPPERCASING bug and some stuff for UNITS, LENGTH
> and subfile NAMEs, but I don't remember all the details, such as whether
> or not I actually finished.
>
> Do you have a nice colorized diff program so you can quickly asses
> the changes? I use tkDiff myself.
I'll have to scope it out.
>
> > > Also, what do you want to do about releases? Do you want me to
> > > package a source release for the 1.0 code? For executable packages
> > > I set the homepage link to go to your website.
> >
> > Will you package a source release please?
>
> Ouch. I was afraid you'd ask for that. Packaging official sourceforge
> release files is one of those things I haven't done often enough to
> remember how.
:^) by your ownb admission you have more experience than me, because I've never
done it at all!
If you would please I would be eternally gratefull.
Kevin
| | | | | | |
