On 6/21/2023 11:33 PM, Glen Strecker wrote:
Thanks, John,
As I said earlier, I appreciate what you are trying to do. Most of
us only have so much time and so many resources to put toward this
HOBBY. Unfortunately, I am not a programmer.
The D-Rats development work can use help of of non-programmers.
Example of non-programming tasks:
Updating and organizing the Wiki for end users.
Testing pull requests for fixes.
Status of some tickets:
*
Position reports being interpreted wrong on the map
A fix in in progress.
It was discovered that D-Rats has been
sending the wrong position for outgoing reports. I do not
remember changing that code from the 0.3 version.
The map positions being plotted wrong is a harder problem
to solve and we are collecting some data to see if we can
find why the plotted latitude of some points are wrong.
*
GPS device not being read correctly.
On hold waiting for more information from you or others.
Need a manual for the GPS or some description of the
messages that it sends to the computer.
With out that, there is no way to fix.
*
GMAIL integration for e-mail.
This may just be a documentation issue.
Instead of a password, you need to configure a token in Gmail
to use instead, and be able to validate its use through two-factor
authentication.
*
Printed e-mails not formatted correctly.
Need some info:
Is this an issue also on the 0.3 version as nothing should
have changed in this section of the code.
Not sure what can be done to "fix" this so that it does not
break what someone else expects.
When these messages are sent over a real SMTP e-mail, they
get MIME encoded for sending and various e-mail clients may
preserve or mangle the lines depending on which bugs they have.
For D-Rats to D-Rats processing, what you type in is what
you get on the other end. If there are no hard line breaks
when the message is composed, then there are none when
it is displayed in a web browser for printing.
*
Form save/send/print has errors.
Fix is in review. In a few places that only showed up
for some forms the conversion to lxml was missed.
73,
-John