On Fri, Apr 28, 2000 at 11:05:11PM +0000, Wilbert Knol wrote:
> etc. They have a lot of stuff you may not need: network/multi op functionality,
What does this mean?
> running totals, band maps, pop-up windows...
>
> However, it would be nice if the logging software offered basic CW features.
>
> The reason is, that a lot of CW ops use a computer to both send CW and
> also log with it. The CW 'keyer' needs to know the call of the guy being
> worked, in order to fire it back at him, and also the RST report you have
> decided to give him (as typed into the RST-sent field).
>
> It makes good sense to combine 'logging' and 'CW keyer' functions.
This is getting involved. I think we're talking about a different front end
on the same database, provided the database schema is flexible enough.
Anyway the libraries etc. to control keyers and radios should be a separate
project.
Somebody else mentioned Java. If the control functions are done with the
serial port it's possible using javax.comm, but probably not bit-banging
interfaces on the parallel port. Therefore maybe it makes more sense to
write a C library and then it's usable from various kinds of GUI's as
well as from web-based front-ends and command-line utilities.
I've been doing Java for several years but I'm liking it less for GUI
work than I used to. The problems with it seem to not be going away.
And AWT still requires Motif. If they'd implement a GTK version it would
be a big improvement. (Don't even mention Swing, what a slow pig.)
--
_______ Shawn T. Rutledge / KB7PWD [EMAIL PROTECTED]
(_ | |_) http://www.bigfoot.com/~ecloud [EMAIL PROTECTED]
__) | | \________________________________________________________________
Get money for spare CPU cycles at http://www.ProcessTree.com/?sponsor=5903
