[chirp_users] What's next for CHIRP
Hi all,
I'd like to announce the availability of what I'm calling the "CHIRP-next" build for the new year. If you're not aware, some of the libraries that CHIRP depends on have been orphaned such that CHIRP was a bit stuck in time for many years. Overcoming this obstacle required a lot of changes to CHIRP's core, drivers, and the GUI has had to be completely rewritten as a result. This has been a ton of work, and we still have a lot left to do.
However, it's time to rope you, the users and power users, into the effort. Several of us have tested hundreds of radios over the last few months getting ready for this, but we need your help to flesh things out. Over 90% of the radios that get used most often with CHIRP have been tested, but there are still plenty left that need to be confirmed (or fixed). Similarly, the GUI has been tested fairly well amongst the developers at this point, but there are surely still plenty of bugs to find and fix.
Ultimately, this new build will become what is today the "daily" builds, and the current version of chirp will be renamed "legacy". As of now, all new development is being done on the "next" builds and only critical bug fixes will be considered for legacy. If CHIRP-next works for you and your radios, we want you running it as soon as possible.
I've put together a page that describes in more detail why we're having to do this, how you can help, and what to look for and report:
https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuild
Also, here's a page that describes some of the changes you can expect in the new version:
https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuildChanges
While we're not doing this specifically to add features, the "opportunity" to redesign some things has allowed us to add some improvements. Further, being on newer dependent libraries has allowed us to add some features we never had before.
If you're on MacOS or Linux, you will almost certainly want to be running the new build immediately. It uses modern dependencies and also behaves much more like a native application on all platforms.
We really need your help testing and vetting this new version, so if you feel comfortable, please consider giving it a try and letting us know what you run into. I'm getting the word out here to the users groups a little early, before we start offering it on the download page specifically. Feel free to forward this to your own groups, facebook pages, etc to get more visibility than just the users here.
You can find the CHIRP-next builds here:
https://trac.chirp.danplanet.com/download?stream=next
As always, you'll want to stay up-to-date with these, as things have been moving fast!
--Dan
Awesome! Thanks Dan.
Marc KQ4ENX
On Sat, Dec 31, 2022, 8:31 PM Dan Smith via chirp_users < chirp_users@intrepid.danplanet.com> wrote:
Hi all,
I'd like to announce the availability of what I'm calling the "CHIRP-next" build for the new year. If you're not aware, some of the libraries that CHIRP depends on have been orphaned such that CHIRP was a bit stuck in time for many years. Overcoming this obstacle required a lot of changes to CHIRP's core, drivers, and the GUI has had to be completely rewritten as a result. This has been a ton of work, and we still have a lot left to do.
However, it's time to rope you, the users and power users, into the effort. Several of us have tested hundreds of radios over the last few months getting ready for this, but we need your help to flesh things out. Over 90% of the radios that get used most often with CHIRP have been tested, but there are still plenty left that need to be confirmed (or fixed). Similarly, the GUI has been tested fairly well amongst the developers at this point, but there are surely still plenty of bugs to find and fix.
Ultimately, this new build will become what is today the "daily" builds, and the current version of chirp will be renamed "legacy". As of now, all new development is being done on the "next" builds and only critical bug fixes will be considered for legacy. If CHIRP-next works for you and your radios, we want you running it as soon as possible.
I've put together a page that describes in more detail why we're having to do this, how you can help, and what to look for and report:
https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuild
Also, here's a page that describes some of the changes you can expect in the new version:
https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuildChanges
While we're not doing this specifically to add features, the "opportunity" to redesign some things has allowed us to add some improvements. Further, being on newer dependent libraries has allowed us to add some features we never had before.
If you're on MacOS or Linux, you will almost certainly want to be running the new build immediately. It uses modern dependencies and also behaves much more like a native application on all platforms.
We really need your help testing and vetting this new version, so if you feel comfortable, please consider giving it a try and letting us know what you run into. I'm getting the word out here to the users groups a little early, before we start offering it on the download page specifically. Feel free to forward this to your own groups, facebook pages, etc to get more visibility than just the users here.
You can find the CHIRP-next builds here:
https://trac.chirp.danplanet.com/download?stream=next
As always, you'll want to stay up-to-date with these, as things have been moving fast!
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Marc T. at marcptramontana@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
Can you please unsubscribe me from your mailing list? Thank you!
On Thu, Jan 5, 2023, 11:42 PM Marc marcptramontana@gmail.com wrote:
Awesome! Thanks Dan.
Marc KQ4ENX
On Sat, Dec 31, 2022, 8:31 PM Dan Smith via chirp_users < chirp_users@intrepid.danplanet.com> wrote:
Hi all,
I'd like to announce the availability of what I'm calling the "CHIRP-next" build for the new year. If you're not aware, some of the libraries that CHIRP depends on have been orphaned such that CHIRP was a bit stuck in time for many years. Overcoming this obstacle required a lot of changes to CHIRP's core, drivers, and the GUI has had to be completely rewritten as a result. This has been a ton of work, and we still have a lot left to do.
However, it's time to rope you, the users and power users, into the effort. Several of us have tested hundreds of radios over the last few months getting ready for this, but we need your help to flesh things out. Over 90% of the radios that get used most often with CHIRP have been tested, but there are still plenty left that need to be confirmed (or fixed). Similarly, the GUI has been tested fairly well amongst the developers at this point, but there are surely still plenty of bugs to find and fix.
Ultimately, this new build will become what is today the "daily" builds, and the current version of chirp will be renamed "legacy". As of now, all new development is being done on the "next" builds and only critical bug fixes will be considered for legacy. If CHIRP-next works for you and your radios, we want you running it as soon as possible.
I've put together a page that describes in more detail why we're having to do this, how you can help, and what to look for and report:
https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuild
Also, here's a page that describes some of the changes you can expect in the new version:
https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuildChanges
While we're not doing this specifically to add features, the "opportunity" to redesign some things has allowed us to add some improvements. Further, being on newer dependent libraries has allowed us to add some features we never had before.
If you're on MacOS or Linux, you will almost certainly want to be running the new build immediately. It uses modern dependencies and also behaves much more like a native application on all platforms.
We really need your help testing and vetting this new version, so if you feel comfortable, please consider giving it a try and letting us know what you run into. I'm getting the word out here to the users groups a little early, before we start offering it on the download page specifically. Feel free to forward this to your own groups, facebook pages, etc to get more visibility than just the users here.
You can find the CHIRP-next builds here:
https://trac.chirp.danplanet.com/download?stream=next
As always, you'll want to stay up-to-date with these, as things have been moving fast!
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Marc T. at marcptramontana@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Anthony F at centralcoastking@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
You have to unsubscribe yourself. At the bottom of every post are the instructions.
On Fri, Jan 6, 2023 at 3:31 AM anthony farley centralcoastking@gmail.com wrote:
Can you please unsubscribe me from your mailing list? Thank you!
On Thu, Jan 5, 2023, 11:42 PM Marc marcptramontana@gmail.com wrote:
Awesome! Thanks Dan.
Marc KQ4ENX
On Sat, Dec 31, 2022, 8:31 PM Dan Smith via chirp_users < chirp_users@intrepid.danplanet.com> wrote:
Hi all,
I'd like to announce the availability of what I'm calling the "CHIRP-next" build for the new year. If you're not aware, some of the libraries that CHIRP depends on have been orphaned such that CHIRP was a bit stuck in time for many years. Overcoming this obstacle required a lot of changes to CHIRP's core, drivers, and the GUI has had to be completely rewritten as a result. This has been a ton of work, and we still have a lot left to do.
However, it's time to rope you, the users and power users, into the effort. Several of us have tested hundreds of radios over the last few months getting ready for this, but we need your help to flesh things out. Over 90% of the radios that get used most often with CHIRP have been tested, but there are still plenty left that need to be confirmed (or fixed). Similarly, the GUI has been tested fairly well amongst the developers at this point, but there are surely still plenty of bugs to find and fix.
Ultimately, this new build will become what is today the "daily" builds, and the current version of chirp will be renamed "legacy". As of now, all new development is being done on the "next" builds and only critical bug fixes will be considered for legacy. If CHIRP-next works for you and your radios, we want you running it as soon as possible.
I've put together a page that describes in more detail why we're having to do this, how you can help, and what to look for and report:
https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuild
Also, here's a page that describes some of the changes you can expect in the new version:
https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuildChanges
While we're not doing this specifically to add features, the "opportunity" to redesign some things has allowed us to add some improvements. Further, being on newer dependent libraries has allowed us to add some features we never had before.
If you're on MacOS or Linux, you will almost certainly want to be running the new build immediately. It uses modern dependencies and also behaves much more like a native application on all platforms.
We really need your help testing and vetting this new version, so if you feel comfortable, please consider giving it a try and letting us know what you run into. I'm getting the word out here to the users groups a little early, before we start offering it on the download page specifically. Feel free to forward this to your own groups, facebook pages, etc to get more visibility than just the users here.
You can find the CHIRP-next builds here:
https://trac.chirp.danplanet.com/download?stream=next
As always, you'll want to stay up-to-date with these, as things have been moving fast!
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Marc T. at marcptramontana@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Anthony F at centralcoastking@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to John Wuest at jhwuest@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
Thank you for all the hard work you and other guys having the programming intellect. Of which I have none. Taking two test during computer school back in the 70's. Failed to grasp the computer programming skills. However I was to be more technically incline to fix or repair any and all computer systems. Keep up the great work. Bob KC4LB...
On Sat, Dec 31, 2022, 8:31 PM Dan Smith via chirp_users < chirp_users@intrepid.danplanet.com> wrote:
Hi all,
I'd like to announce the availability of what I'm calling the "CHIRP-next" build for the new year. If you're not aware, some of the libraries that CHIRP depends on have been orphaned such that CHIRP was a bit stuck in time for many years. Overcoming this obstacle required a lot of changes to CHIRP's core, drivers, and the GUI has had to be completely rewritten as a result. This has been a ton of work, and we still have a lot left to do.
However, it's time to rope you, the users and power users, into the effort. Several of us have tested hundreds of radios over the last few months getting ready for this, but we need your help to flesh things out. Over 90% of the radios that get used most often with CHIRP have been tested, but there are still plenty left that need to be confirmed (or fixed). Similarly, the GUI has been tested fairly well amongst the developers at this point, but there are surely still plenty of bugs to find and fix.
Ultimately, this new build will become what is today the "daily" builds, and the current version of chirp will be renamed "legacy". As of now, all new development is being done on the "next" builds and only critical bug fixes will be considered for legacy. If CHIRP-next works for you and your radios, we want you running it as soon as possible.
I've put together a page that describes in more detail why we're having to do this, how you can help, and what to look for and report:
https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuild
Also, here's a page that describes some of the changes you can expect in the new version:
https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuildChanges
While we're not doing this specifically to add features, the "opportunity" to redesign some things has allowed us to add some improvements. Further, being on newer dependent libraries has allowed us to add some features we never had before.
If you're on MacOS or Linux, you will almost certainly want to be running the new build immediately. It uses modern dependencies and also behaves much more like a native application on all platforms.
We really need your help testing and vetting this new version, so if you feel comfortable, please consider giving it a try and letting us know what you run into. I'm getting the word out here to the users groups a little early, before we start offering it on the download page specifically. Feel free to forward this to your own groups, facebook pages, etc to get more visibility than just the users here.
You can find the CHIRP-next builds here:
https://trac.chirp.danplanet.com/download?stream=next
As always, you'll want to stay up-to-date with these, as things have been moving fast!
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Bob at kc4lb1@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
That's brilliant. Thanks Dan and HNY Tony G7TXU
On Sun, 1 Jan 2023 at 01:49, bob burks kc4lb1@gmail.com wrote:
Thank you for all the hard work you and other guys having the programming intellect. Of which I have none. Taking two test during computer school back in the 70's. Failed to grasp the computer programming skills. However I was to be more technically incline to fix or repair any and all computer systems. Keep up the great work. Bob KC4LB...
On Sat, Dec 31, 2022, 8:31 PM Dan Smith via chirp_users < chirp_users@intrepid.danplanet.com> wrote:
Hi all,
I'd like to announce the availability of what I'm calling the "CHIRP-next" build for the new year. If you're not aware, some of the libraries that CHIRP depends on have been orphaned such that CHIRP was a bit stuck in time for many years. Overcoming this obstacle required a lot of changes to CHIRP's core, drivers, and the GUI has had to be completely rewritten as a result. This has been a ton of work, and we still have a lot left to do.
However, it's time to rope you, the users and power users, into the effort. Several of us have tested hundreds of radios over the last few months getting ready for this, but we need your help to flesh things out. Over 90% of the radios that get used most often with CHIRP have been tested, but there are still plenty left that need to be confirmed (or fixed). Similarly, the GUI has been tested fairly well amongst the developers at this point, but there are surely still plenty of bugs to find and fix.
Ultimately, this new build will become what is today the "daily" builds, and the current version of chirp will be renamed "legacy". As of now, all new development is being done on the "next" builds and only critical bug fixes will be considered for legacy. If CHIRP-next works for you and your radios, we want you running it as soon as possible.
I've put together a page that describes in more detail why we're having to do this, how you can help, and what to look for and report:
https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuild
Also, here's a page that describes some of the changes you can expect in the new version:
https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuildChanges
While we're not doing this specifically to add features, the "opportunity" to redesign some things has allowed us to add some improvements. Further, being on newer dependent libraries has allowed us to add some features we never had before.
If you're on MacOS or Linux, you will almost certainly want to be running the new build immediately. It uses modern dependencies and also behaves much more like a native application on all platforms.
We really need your help testing and vetting this new version, so if you feel comfortable, please consider giving it a try and letting us know what you run into. I'm getting the word out here to the users groups a little early, before we start offering it on the download page specifically. Feel free to forward this to your own groups, facebook pages, etc to get more visibility than just the users here.
You can find the CHIRP-next builds here:
https://trac.chirp.danplanet.com/download?stream=next
As always, you'll want to stay up-to-date with these, as things have been moving fast!
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Bob at kc4lb1@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Tony Ling at tonyg7txu@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
I want to thank all of you that are working on Chirp. Amazing! Dean - KC9REN
On 12/31/2022 7:30 PM, Dan Smith via chirp_users wrote:
Hi all,
I'd like to announce the availability of what I'm calling the "CHIRP-next" build for the new year. If you're not aware, some of the libraries that CHIRP depends on have been orphaned such that CHIRP was a bit stuck in time for many years. Overcoming this obstacle required a lot of changes to CHIRP's core, drivers, and the GUI has had to be completely rewritten as a result. This has been a ton of work, and we still have a lot left to do.
However, it's time to rope you, the users and power users, into the effort. Several of us have tested hundreds of radios over the last few months getting ready for this, but we need your help to flesh things out. Over 90% of the radios that get used most often with CHIRP have been tested, but there are still plenty left that need to be confirmed (or fixed). Similarly, the GUI has been tested fairly well amongst the developers at this point, but there are surely still plenty of bugs to find and fix.
Ultimately, this new build will become what is today the "daily" builds, and the current version of chirp will be renamed "legacy". As of now, all new development is being done on the "next" builds and only critical bug fixes will be considered for legacy. If CHIRP-next works for you and your radios, we want you running it as soon as possible.
I've put together a page that describes in more detail why we're having to do this, how you can help, and what to look for and report:
https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuild
Also, here's a page that describes some of the changes you can expect in the new version:
https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuildChanges
While we're not doing this specifically to add features, the "opportunity" to redesign some things has allowed us to add some improvements. Further, being on newer dependent libraries has allowed us to add some features we never had before.
If you're on MacOS or Linux, you will almost certainly want to be running the new build immediately. It uses modern dependencies and also behaves much more like a native application on all platforms.
We really need your help testing and vetting this new version, so if you feel comfortable, please consider giving it a try and letting us know what you run into. I'm getting the word out here to the users groups a little early, before we start offering it on the download page specifically. Feel free to forward this to your own groups, facebook pages, etc to get more visibility than just the users here.
You can find the CHIRP-next builds here:
https://trac.chirp.danplanet.com/download?stream=next
As always, you'll want to stay up-to-date with these, as things have been moving fast!
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dean Berglund at deanberg2044@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
Hello Dan, Congratulations to you and all who work hard on it. And it sounds like good news to those who can use it. Do we still need flatpak to install and use it? Those of us who have to use a screenreader can't use Chirp with flatpak. Glenn ----- Original Message ----- From: "Dan Smith via chirp_users" chirp_users@intrepid.danplanet.com To: "Discussion of CHIRP" chirp_users@intrepid.danplanet.com Sent: Saturday, December 31, 2022 7:30 PM Subject: [chirp_users] What's next for CHIRP
Hi all,
I'd like to announce the availability of what I'm calling the "CHIRP-next" build for the new year. If you're not aware, some of the libraries that CHIRP depends on have been orphaned such that CHIRP was a bit stuck in time for many years. Overcoming this obstacle required a lot of changes to CHIRP's core, drivers, and the GUI has had to be completely rewritten as a result. This has been a ton of work, and we still have a lot left to do.
However, it's time to rope you, the users and power users, into the effort. Several of us have tested hundreds of radios over the last few months getting ready for this, but we need your help to flesh things out. Over 90% of the radios that get used most often with CHIRP have been tested, but there are still plenty left that need to be confirmed (or fixed). Similarly, the GUI has been tested fairly well amongst the developers at this point, but there are surely still plenty of bugs to find and fix.
Ultimately, this new build will become what is today the "daily" builds, and the current version of chirp will be renamed "legacy". As of now, all new development is being done on the "next" builds and only critical bug fixes will be considered for legacy. If CHIRP-next works for you and your radios, we want you running it as soon as possible.
I've put together a page that describes in more detail why we're having to do this, how you can help, and what to look for and report:
https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuild
Also, here's a page that describes some of the changes you can expect in the new version:
https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuildChanges
While we're not doing this specifically to add features, the "opportunity" to redesign some things has allowed us to add some improvements. Further, being on newer dependent libraries has allowed us to add some features we never had before.
If you're on MacOS or Linux, you will almost certainly want to be running the new build immediately. It uses modern dependencies and also behaves much more like a native application on all platforms.
We really need your help testing and vetting this new version, so if you feel comfortable, please consider giving it a try and letting us know what you run into. I'm getting the word out here to the users groups a little early, before we start offering it on the download page specifically. Feel free to forward this to your own groups, facebook pages, etc to get more visibility than just the users here.
You can find the CHIRP-next builds here:
https://trac.chirp.danplanet.com/download?stream=next
As always, you'll want to stay up-to-date with these, as things have been moving fast!
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to K0LNY at glenn@ervin.email To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
I definitely roger Glenn's congratulations on chirp-next. Very much looking forward to trying it out with Orca. Keep up the great work, Dan and team, and here's to a great 2023.
Guy Ke8Jyp
On 12/31/22 22:17, K0LNY_Glenn wrote:
Hello Dan, Congratulations to you and all who work hard on it. And it sounds like good news to those who can use it. Do we still need flatpak to install and use it? Those of us who have to use a screenreader can't use Chirp with flatpak. Glenn ----- Original Message ----- From: "Dan Smith via chirp_users" chirp_users@intrepid.danplanet.com To: "Discussion of CHIRP" chirp_users@intrepid.danplanet.com Sent: Saturday, December 31, 2022 7:30 PM Subject: [chirp_users] What's next for CHIRP
Hi all,
I'd like to announce the availability of what I'm calling the "CHIRP-next" build for the new year. If you're not aware, some of the libraries that CHIRP depends on have been orphaned such that CHIRP was a bit stuck in time for many years. Overcoming this obstacle required a lot of changes to CHIRP's core, drivers, and the GUI has had to be completely rewritten as a result. This has been a ton of work, and we still have a lot left to do.
However, it's time to rope you, the users and power users, into the effort. Several of us have tested hundreds of radios over the last few months getting ready for this, but we need your help to flesh things out. Over 90% of the radios that get used most often with CHIRP have been tested, but there are still plenty left that need to be confirmed (or fixed). Similarly, the GUI has been tested fairly well amongst the developers at this point, but there are surely still plenty of bugs to find and fix.
Ultimately, this new build will become what is today the "daily" builds, and the current version of chirp will be renamed "legacy". As of now, all new development is being done on the "next" builds and only critical bug fixes will be considered for legacy. If CHIRP-next works for you and your radios, we want you running it as soon as possible.
I've put together a page that describes in more detail why we're having to do this, how you can help, and what to look for and report:
https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuild
Also, here's a page that describes some of the changes you can expect in the new version:
https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuildChanges
While we're not doing this specifically to add features, the "opportunity" to redesign some things has allowed us to add some improvements. Further, being on newer dependent libraries has allowed us to add some features we never had before.
If you're on MacOS or Linux, you will almost certainly want to be running the new build immediately. It uses modern dependencies and also behaves much more like a native application on all platforms.
We really need your help testing and vetting this new version, so if you feel comfortable, please consider giving it a try and letting us know what you run into. I'm getting the word out here to the users groups a little early, before we start offering it on the download page specifically. Feel free to forward this to your own groups, facebook pages, etc to get more visibility than just the users here.
You can find the CHIRP-next builds here:
https://trac.chirp.danplanet.com/download?stream=next
As always, you'll want to stay up-to-date with these, as things have been moving fast!
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to K0LNY at glenn@ervin.email To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Guy Schlosser at guyster@bex.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com .
There's no box to put in username and password for RepeaterBook and that server doesn't even come up. I think I read here that they were "down".
Congrats, Dan, nice clean lines on the new CHIRP.
73 DR N1EA
On Sat, Dec 31, 2022 at 8:31 PM Dan Smith via chirp_users chirp_users@intrepid.danplanet.com wrote:
Hi all,
I'd like to announce the availability of what I'm calling the "CHIRP-next" build for the new year. If you're not aware, some of the libraries that CHIRP depends on have been orphaned such that CHIRP was a bit stuck in time for many years. Overcoming this obstacle required a lot of changes to CHIRP's core, drivers, and the GUI has had to be completely rewritten as a result. This has been a ton of work, and we still have a lot left to do.
However, it's time to rope you, the users and power users, into the effort. Several of us have tested hundreds of radios over the last few months getting ready for this, but we need your help to flesh things out. Over 90% of the radios that get used most often with CHIRP have been tested, but there are still plenty left that need to be confirmed (or fixed). Similarly, the GUI has been tested fairly well amongst the developers at this point, but there are surely still plenty of bugs to find and fix.
Ultimately, this new build will become what is today the "daily" builds, and the current version of chirp will be renamed "legacy". As of now, all new development is being done on the "next" builds and only critical bug fixes will be considered for legacy. If CHIRP-next works for you and your radios, we want you running it as soon as possible.
I've put together a page that describes in more detail why we're having to do this, how you can help, and what to look for and report:
https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuild
Also, here's a page that describes some of the changes you can expect in the new version:
https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuildChanges
While we're not doing this specifically to add features, the "opportunity" to redesign some things has allowed us to add some improvements. Further, being on newer dependent libraries has allowed us to add some features we never had before.
If you're on MacOS or Linux, you will almost certainly want to be running the new build immediately. It uses modern dependencies and also behaves much more like a native application on all platforms.
We really need your help testing and vetting this new version, so if you feel comfortable, please consider giving it a try and letting us know what you run into. I'm getting the word out here to the users groups a little early, before we start offering it on the download page specifically. Feel free to forward this to your own groups, facebook pages, etc to get more visibility than just the users here.
You can find the CHIRP-next builds here:
https://trac.chirp.danplanet.com/download?stream=next
As always, you'll want to stay up-to-date with these, as things have been moving fast!
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to D.J.J. Ring, Jr. at n1ea@arrl.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
Dan and the Chirp code gang, a big hand and thank you for the work you guys have done. I recall my first encounter with Chirp and the IC-92AD, it worked well and I was able to program my radio in Linux rather than windows.
Now to those who complained and made remarks about Chirp being behind, I hope you realize that they have been working on it all along and the needed changes were NOT trivial, also remember these folks have lives and families that need tending to, it got done, a LOT of hard work. I am not a coder but used to test code that coders did on the hardware it was written for. I learned that getting it just right takes a LOT of time and patience.
Thanks Dan group.
And a very Happy New Year.
On Sat, Dec 31, 2022 at 9:44 PM D.J.J. Ring, Jr. n1ea@arrl.net wrote:
There's no box to put in username and password for RepeaterBook and that server doesn't even come up. I think I read here that they were "down".
Congrats, Dan, nice clean lines on the new CHIRP.
73 DR N1EA
On Sat, Dec 31, 2022 at 8:31 PM Dan Smith via chirp_users chirp_users@intrepid.danplanet.com wrote:
Hi all,
I'd like to announce the availability of what I'm calling the
"CHIRP-next" build for the new year. If you're not aware, some of the libraries that CHIRP depends on have been orphaned such that CHIRP was a bit stuck in time for many years. Overcoming this obstacle required a lot of changes to CHIRP's core, drivers, and the GUI has had to be completely rewritten as a result. This has been a ton of work, and we still have a lot left to do.
However, it's time to rope you, the users and power users, into the
effort. Several of us have tested hundreds of radios over the last few months getting ready for this, but we need your help to flesh things out. Over 90% of the radios that get used most often with CHIRP have been tested, but there are still plenty left that need to be confirmed (or fixed). Similarly, the GUI has been tested fairly well amongst the developers at this point, but there are surely still plenty of bugs to find and fix.
Ultimately, this new build will become what is today the "daily" builds,
and the current version of chirp will be renamed "legacy". As of now, all new development is being done on the "next" builds and only critical bug fixes will be considered for legacy. If CHIRP-next works for you and your radios, we want you running it as soon as possible.
I've put together a page that describes in more detail why we're having
to do this, how you can help, and what to look for and report:
https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuild
Also, here's a page that describes some of the changes you can expect in
the new version:
https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuildChanges
While we're not doing this specifically to add features, the
"opportunity" to redesign some things has allowed us to add some improvements. Further, being on newer dependent libraries has allowed us to add some features we never had before.
If you're on MacOS or Linux, you will almost certainly want to be
running the new build immediately. It uses modern dependencies and also behaves much more like a native application on all platforms.
We really need your help testing and vetting this new version, so if you
feel comfortable, please consider giving it a try and letting us know what you run into. I'm getting the word out here to the users groups a little early, before we start offering it on the download page specifically. Feel free to forward this to your own groups, facebook pages, etc to get more visibility than just the users here.
You can find the CHIRP-next builds here:
https://trac.chirp.danplanet.com/download?stream=next
As always, you'll want to stay up-to-date with these, as things have
been moving fast!
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to D.J.J. Ring, Jr. at n1ea@arrl.net To unsubscribe, send an email to
chirp_users-unsubscribe@intrepid.danplanet.com
To report this email as off-topic, please email
chirp_users-owner@intrepid.danplanet.com
Searchable archive:
https://www.mail-archive.com/chirp_users@intrepid.danplanet.com _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chuck Hast at kp4djt@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
Initial impression:
On windows 10 -- screen hard to read point size of text too small and light.
On Ubuntu 22.04.1 -- can't figure out how to get it to run.
On 12/31/22 19:30, Dan Smith via chirp_users wrote:
Hi all,
I'd like to announce the availability of what I'm calling the "CHIRP-next" build for the new year. If you're not aware, some of the libraries that CHIRP depends on have been orphaned such that CHIRP was a bit stuck in time for many years. Overcoming this obstacle required a lot of changes to CHIRP's core, drivers, and the GUI has had to be completely rewritten as a result. This has been a ton of work, and we still have a lot left to do.
However, it's time to rope you, the users and power users, into the effort. Several of us have tested hundreds of radios over the last few months getting ready for this, but we need your help to flesh things out. Over 90% of the radios that get used most often with CHIRP have been tested, but there are still plenty left that need to be confirmed (or fixed). Similarly, the GUI has been tested fairly well amongst the developers at this point, but there are surely still plenty of bugs to find and fix.
Ultimately, this new build will become what is today the "daily" builds, and the current version of chirp will be renamed "legacy". As of now, all new development is being done on the "next" builds and only critical bug fixes will be considered for legacy. If CHIRP-next works for you and your radios, we want you running it as soon as possible.
I've put together a page that describes in more detail why we're having to do this, how you can help, and what to look for and report:
https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuild
Also, here's a page that describes some of the changes you can expect in the new version:
https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuildChanges
While we're not doing this specifically to add features, the "opportunity" to redesign some things has allowed us to add some improvements. Further, being on newer dependent libraries has allowed us to add some features we never had before.
If you're on MacOS or Linux, you will almost certainly want to be running the new build immediately. It uses modern dependencies and also behaves much more like a native application on all platforms.
We really need your help testing and vetting this new version, so if you feel comfortable, please consider giving it a try and letting us know what you run into. I'm getting the word out here to the users groups a little early, before we start offering it on the download page specifically. Feel free to forward this to your own groups, facebook pages, etc to get more visibility than just the users here.
You can find the CHIRP-next builds here:
https://trac.chirp.danplanet.com/download?stream=next
As always, you'll want to stay up-to-date with these, as things have been moving fast!
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Paul AC0HY at ac0hy@wpmills.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
On Sun, Jan 1, 2023 at 8:44 PM W Paul Mills ac0hy@wpmills.com wrote:
Initial impression:
On windows 10 -- screen hard to read point size of text too small and light.
On Ubuntu 22.04.1 -- can't figure out how to get it to run.
Ubuntu - chirp should be installed in /usr/bin/chirpw.
Try running "chirpw" in a terminal - I use MATE and my terminal is mate-terminal; other terminals work as well.
If you haven't rebooted, try that, if it is still not there, try installing xfce4-appfinder that should now shop up in "Accessories" - "Application Finder" - (on my system, CHIRP right below that menu item) - chirp will show up if you start typing "chirp". I've seen Debian based distros install CHIRP under "Network" and I overlooked it several times.
Lastly add a launcher to the menu manually. https://askubuntu.com/questions/16825/how-can-i-add-and-change-items-in-my-a...
73
DR
On 1/1/23 20:03, D.J.J. Ring, Jr. wrote:
On Sun, Jan 1, 2023 at 8:44 PM W Paul Mills ac0hy@wpmills.com wrote:
Initial impression:
On windows 10 -- screen hard to read point size of text too small and light.
On Ubuntu 22.04.1 -- can't figure out how to get it to run.
Ubuntu - chirp should be installed in /usr/bin/chirpw.
Try running "chirpw" in a terminal - I use MATE and my terminal is mate-terminal; other terminals work as well.
If you haven't rebooted, try that, if it is still not there, try installing xfce4-appfinder that should now shop up in "Accessories" - "Application Finder" - (on my system, CHIRP right below that menu item) - chirp will show up if you start typing "chirp". I've seen Debian based distros install CHIRP under "Network" and I overlooked it several times.
Lastly add a launcher to the menu manually. https://askubuntu.com/questions/16825/how-can-i-add-and-change-items-in-my-a...
73
DR
NOPE! Found it on the github.com, that one works. Files missing in link location in Dan's email.
Doesn't display properly with dark themes -- my usual setup.
The file 'chirpwx.py' and 'INSTALL' and others are missing. Can be run from source directory with 'chirpwx.py' added.
Paul / AC0HY
Dan Smith via chirp_users chirp_users@intrepid.danplanet.com writes:
I'd like to announce the availability of what I'm calling the "CHIRP-next" build for the new year. If you're not aware, some of the libraries that CHIRP depends on have been orphaned such that CHIRP was a bit stuck in time for many years. Overcoming this obstacle required a lot of changes to CHIRP's core, drivers, and the GUI has had to be completely rewritten as a result. This has been a ton of work, and we still have a lot left to do.
I maintain the chirp package in pkgsrc. So far I haven't dug in to CHIRP-next but I've been silently cheering you on; chirp is one of the last 3 programs on my system to need python2.7.
What is the transition plan? Is CHIRP-next a branch in the repo, and when it works well enough it will be merged, and hence the chirp daily snapshots (with YYYYMMDD) will then be python3? If so, that's great and I will simply adjust the package.
Or, is chirp going to remain python2.7 and basically not get updates, and I should create a packge for CHIRP-next which will remain as the name, with the current distribution tarball location, even after next becomes the standard approach?
Or, something else?
73 de n1dam
participants (13)
-
anthony farley -
bob burks -
Chuck Hast -
D.J.J. Ring, Jr. -
Dan Smith -
Dean Berglund -
Greg Troxel -
Guy Schlosser -
John Wuest -
K0LNY_Glenn -
Marc -
Tony Ling -
W Paul Mills