Project

General

Profile

Actions

New Model #11270

open

new version of uv-k5 quansheng from F4HWN

Added by Jocelyn Maheu about 1 month ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
03/29/2024
Due date:
% Done:

0%

Estimated time:
Equipment Loan/Gift Offered:
No
I read the instructions above:
Yes

Description

Hi

i made a chirp driver for the firmware of F4HWN who is base on egzumer firmware for the uv-k5 radio,

i made the chirp driver with egzumer for his egzumer firmware before integrated in the chirp ( auto detect now )

i would like to add it to the chirp data base instead of load module when open chirp

take a look about it. i have the french driver and the english driver,

Many set doc have been implemented and help section

let me know what can be done


Files

uvk5_egzumer_f4hwn.py (117 KB) uvk5_egzumer_f4hwn.py driver in english Jocelyn Maheu, 03/29/2024 07:04 PM
uvk5_egzumer_f4hwn_fr.py (118 KB) uvk5_egzumer_f4hwn_fr.py driver in french Jocelyn Maheu, 03/29/2024 07:04 PM
Actions #1

Updated by Dan Smith about 1 month ago

What are the differences between this and the egzumer driver? If this adds more functionality from the egzumer variant, you need to subclass that radio and only change the things necessary. Duplicating the whole driver is not acceptable, as it creates a big maintenance burden for us. See how the egzumer driver subclasses the base driver and adds its new functionality.

Please describe how your driver differs so I can help you figure out how to subclass.

Also, don't create a french and english driver. Mark your strings like _("foo"). Then update the translation files with make -C chirp/locale clean all and then find/translate them in the fr.po file. That way it will also work for other languages.

Actions

Also available in: Atom PDF