-
-
Notifications
You must be signed in to change notification settings - Fork 7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make it easier to edit the Arduino IDE theme #6454
Comments
Here is a workaround. |
I am looking forward to work for enhancing and improving the theme work, and adding relevant information to the README.md on https://github.com/per1234/ThemeTest/blob/master/README.md . Please provide me further suggestions @per1234 |
Great! Contributions to my ThemeTest repository are welcome. You can submit pull requests to that repository for any improvements or corrections you would like to propose. |
Responding to #7115 (comment)
That would be wonderful!
I agree that it would make sense to also document any relevant parts of preferences.txt (e.g.,
That would be very useful. We don't have any way to submit this sort of documentation as a PR. My idea is that it would make sense to add a page documenting Arduino IDE themes to this repository's wiki, since it is documentation for theme developers. My suggestion would be for you to create your own GitHub repository and first publish the documentation you write in the wiki of that repository. The initial development and collaboration on the content can occur there. Once the documentation is in a finished state, you can present a link to your wiki for Arduino's approval, after which you can copy the content over to Arduino's wiki.
We already have this issue (#6454) on that topic so there is no need to create another topic. Note that if the work you are proposing is intended to be part of Arduino's Season of Docs program, you must still go through the formal process established by Google before starting the GSoD project work. Now is an appropriate time for you to be doing the research that will lead to the project proposal in your application, but the actual "Doc development" phase of the program does not start until 2019-11-02. If you just want to do the work as a volunteer outside of the Season of Docs program, that is very welcome and you can start whenever you like. |
@per1234 I have designed a basic Wiki Page for the Theme, from my research. Please have a look- I'll keep on updating the content to add the most significant and important points: |
This topic has come up previously in #3056, #3633, #6025 and #6438 but the latter two topics are more focused on controlling specific properties via the GUI.
This also comes up regularly on the Arduino forum and, as with #1878, #3056, #3633, #6025, #7451, #7780 it's almost always an accessibility issue rather than aesthetics so this is important.
I'm sure most users would prefer some sort of a GUI theme editor but I don't know how feasible that would be. This could be a standalone application or added to File > Preferences. Offering even the most minimal control of the theme would end up adding quite a few items to Preferences so it would probably be best to add a separate tab, as is already done with the Network settings.
A more simple, if less user friendly option, is to just document the location of the theme files and the function of the various properties. I have made a start at this in the readme of https://github.com/per1234/ThemeTest but it needs some polishing to make it more accessible to the average user. Since this is more advanced information, it might make sense to add it as a page on the GitHub wiki. The Arduino Playground is another option.
Below has been solved by #7115:
A significant problem is that the theme files are stored in the Arduino IDE installation folder and thus any changes to those files will be lost after upgrading to a new version. The solution is to move these files to a persistent location such as the Arduino15 folder, as is already done with preferences.txt.The text was updated successfully, but these errors were encountered: