[pskmail] Re: Developers
- From: Rein Couperus <Rein@xxxxxxxxxxxx>
- To: pskmail@xxxxxxxxxxxxx
- Date: Mon, 14 Jan 2008 21:27:19 +0100
Hello all,
yes, it is rather quiet here.
I have enough ideas for going further, and I'd like your comments about it.
* First there are still some quirks (also caled bugs) which have to be sorted
out:
- The server relays APRS messages sent by another server on the same frequency.
This
requires a change in the linklayer protocol for APRS messaging, and there must
also be a bug
in the 'link list check', as the other server cannot possibly in the link list.
Then there are some things changing in the background which must be accomodated
* I have been experimenting with the new hamlib rigctld, which is a rig control
server
which can be operated via a tcp link. I want to use it for pskmail and tlf.
This makes
it possible to use grig and pskmail at the same time.
For the future there is another development which may be interesting for us:
* WA5ZNU (Leigh) has written a PSK31 modem in Java, which is completely
decoupled from
the GUI. Via a tcp socket it provides connection to the GUI, and the interface
incorporates
data for the warterfall and the quality indicator.
This development enables to incorporate the function of fldigi (you are using
waterfall, rx window and
quality indicator) into the pskmail GUI. if we can (in the process) rewrite the
protocol engine and the
GUI in C++ or Java we could open the project for users of other operating
systems as well, which
would no doubt create a broader user base. Of course we would also need to
incorporate PSK63, 125
and 250 in the modem part.
There could be 3 devt. teams working on this, one for the modem, 1 for the
protocol layer and 1 for the GUI.
Then we would need a load of people to handle the user documentation....
I would probably leave the server in perl, in order to be able to change it
quickly, and add new stuff like
telnet, Delay Tolerant Networking and an unproto convers channel.
Things to do on the server:
* Logging of transmitted frames
* Better on-the-fly changing of the transmission speed (only push the button on
the client)
* A 'signalling channel' to send command strings between server and client (at
the moment embedded in the
data stream).
* telnet socket via the rf link to control the server when your internet is
down (PI4TUE is 20 km from my qth :)
As you see, there is enough work to be done, these are just some of the wild
things that come to my mind now :)
Hw?
73,
Rein PA0R
On Mon, 14 Jan 2008 14:29:03 +0100 (CET)
"Per Crusefalk" <per@xxxxxxxxxxxx> wrote:
> Hi all,
>
> The list is too quiet for me now so I decided to try to change that ;-)
>
> I have started to get settled at my new QTH (it only took abt 6 months)
> and that means I have started to have some time for ham radio once agn. I
> have started looking at what I would like to improve on the project and
> have just added tls auth for using googles smtp server with pskmail. I am
> also thinking abt what I can do next. If there are others out there that
> would like to participate then I just want to mention a few words about
> how you may do so.
>
> As this is an open source project you can just download the source and
> start, you can also use the project subversion server where all the latest
> stuff should be available. Subversion is a revision control system and
> more info on that is available here:
> http://subversion.tigris.org/
>
> The project subversion repository has a web interface here:
> http://www.crusefalk.se/websvn/
>
> If you prefer to use a real client for subversion then the url for that is:
> svn://www.crusefalk.se/websvn
>
> Also, I'm curious abt what you would like to see done next? What could be
> done better and what essential feature may be missing?
> I know we have the wiki for these things but perhaps its easier to discuss
> it here first and then post on the wiki?
>
> 73 de Per, sm0rwo
>
> P.s. Developers are essential, even Steve Ballmer realizes that:
> http://video.google.com/videoplay?docid=6304687408656696643
>
>
>
--
Rein Couperus <Rein@xxxxxxxxxxxx>
Other related posts: