You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As HamClock nears the end of its life cycle with the release of its successor, OpenHamClock, several features require significant attention. Given HamClock’s widespread use on Raspberry Pi devices, these improvements are particularly important.
.env:
The focus should be on the .env setup file, as it’s missing all user-specific look and feel settings. For example, it doesn’t include map choices and positions, the satellite section, solar panel options, and callsign settings on/off on the map.
Layout:
The layouts are great, but they also lack the ability for users to choose what should be displayed. All layouts default to the DX Cluster, leaving users with no option to replace it with another feature. I love the classic layout on a 7-inch screen, but I can’t change the default windows that appear.
Multi device viewing:
The .env user setting file is crucial for OHC to function properly. Running OHC on a Raspberry Pi and accessing it from other devices is cumbersome because the user must set up each viewing device every time OHC is opened. OHC should only read the .env settings file, ensuring a consistent appearance across all devices. HamClock was that way, and I’d love to see OpenHamClock follow suit. Every feature, tab, and window was customizable to the users choice, regardless of the monitor size.
I want to express my gratitude to the OpenHamClock team for their dedication and hard work. With continued effort, OpenHamClock will only improve. These are a few key areas to focus on moving forward.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
As HamClock nears the end of its life cycle with the release of its successor, OpenHamClock, several features require significant attention. Given HamClock’s widespread use on Raspberry Pi devices, these improvements are particularly important.
.env:
The focus should be on the .env setup file, as it’s missing all user-specific look and feel settings. For example, it doesn’t include map choices and positions, the satellite section, solar panel options, and callsign settings on/off on the map.
Layout:
The layouts are great, but they also lack the ability for users to choose what should be displayed. All layouts default to the DX Cluster, leaving users with no option to replace it with another feature. I love the classic layout on a 7-inch screen, but I can’t change the default windows that appear.
Multi device viewing:
The .env user setting file is crucial for OHC to function properly. Running OHC on a Raspberry Pi and accessing it from other devices is cumbersome because the user must set up each viewing device every time OHC is opened. OHC should only read the .env settings file, ensuring a consistent appearance across all devices. HamClock was that way, and I’d love to see OpenHamClock follow suit. Every feature, tab, and window was customizable to the users choice, regardless of the monitor size.
I want to express my gratitude to the OpenHamClock team for their dedication and hard work. With continued effort, OpenHamClock will only improve. These are a few key areas to focus on moving forward.
Once again Thank You all.
Beta Was this translation helpful? Give feedback.
All reactions