K4ETY
|
Wolphi,
You have done a tremendous job of creating a nice set of Android Apps for Hams. As a developer and a ham, I have made a point to try to support developers that are writing Amateur Radio ralated apps for Android, so I have purchased all of your apps. Each has been very well done, and I look forward to seeing what you have added each time I see a new version of one of them in the market.
I am wanting to learn CW, and in comparing the Morse Code apps I found that yours is the most polished and has the best set of features and functionality. There are various CW Traing apps, SMS to CW apps, CW ringtone apps, and apps that will “read” an ebook in Morse Code. Each app had some good ideas, but they are not very configurable, and each has a different (and inferior) way of implementing the actual Morse Code generation than what you have done. Each one of them tries to reinvent the wheel.
I think it would be great that when one of my ham friends calls, my phone would automatically look up their callsign from the Nickname field of the Contact list entry, then announce their callsign as Morse Code, like a ringtone. However, I also realize that other people may want to have a different setup, and trying to develop an all-inclusive app that does every possible function can quickly get out of hand. In fact, there are apps that already exists that do a great job at “customizing” this type of setup – the one I use is called Tasker. But, while Tasker can readily invoke a text-to-speech engine to speak something in any language imaginable, there is no way to “say” something in Morse Code.
What I think would be very beneficial is for you to extend the work you have done in your CW Training app to expose the Morse Code generation capability so that other apps could take advantage of it. The most elegant way to do that would be to turn the Morse Code Generation function of the app into a Text-to-Speech engine, except the language it would speak would be Morse Code. To any other app (or your own app, for that matter), it would be invoked just as any other TTS engine, using the standard Android TTS API. The training functionality of your app would not be changed, substantially, but this would make your app far more useful to someone wanting to customize their phone to use Morse Code in some way. It would also be a great reinforcement to someone, like me, who is trying to learn Morse Code.
Thanks, and keep up the good work!
73,
K4ETY
|
Wolphi
|
Hi William:
Thank you for your post and all the flowers 
After reading your post I did some research on TTS on the internet and in my Android books. I found a lot of examples on how to use existing TTS libraries but not on how to program new ones. I think your idea is ready good. After thinking a little bit more about I think it would be a better idea to run a morse code service and have other apps send broadcast to that service. I am not really sure what the best way is to do archive it. It is a really good idea and I will do more research on it. Right now I have too many projects on my hand so it would be something which I would program really soon. If you find anything about creating or programming TTS libraries it would be a big help .
vy 73
Wolfgang
|