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
This may come from a lack of understanding of the actual user base of this product so feel free to refute.
In my opinion, working with the files in the Arduino IDE would be much easier if the specific hardware files were grouped together and the most frequently changed by new people were gathered together at the top. I'd call the second group the primary config files.
Towards that end, I'd like to suggest that the hardware name be a prefix instead of a suffix and that keyer_pin_settings.h, keyer_settings.h and keyer_features_and_options.h have the keyer_ prefix changed to config_ which would bring it to the top. When displayed in the Arduino IDE 2.0.0, it would have the most important files in tabs visible to the new user instead of behind the ... button. Also, if you're working with specific hardware, you'll have them grouped for easy finding also
We'd end up with a file listing like below resulting in less hunting for the most commonly used files.
This may come from a lack of understanding of the actual user base of this product so feel free to refute.
In my opinion, working with the files in the Arduino IDE would be much easier if the specific hardware files were grouped together and the most frequently changed by new people were gathered together at the top. I'd call the second group the primary config files.
Towards that end, I'd like to suggest that the hardware name be a prefix instead of a suffix and that keyer_pin_settings.h, keyer_settings.h and keyer_features_and_options.h have the keyer_ prefix changed to config_ which would bring it to the top. When displayed in the Arduino IDE 2.0.0, it would have the most important files in tabs visible to the new user instead of behind the ... button. Also, if you're working with specific hardware, you'll have them grouped for easy finding also
We'd end up with a file listing like below resulting in less hunting for the most commonly used files.
If this is interesting to the community, I'm willing to take on a push request. I should be able to script it into shape pretty quick.
The text was updated successfully, but these errors were encountered: