Skip to content
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

Give some coolness factor to the ArduinoIDE #4084

Closed
lmihalkovic opened this issue Nov 5, 2015 · 6 comments
Closed

Give some coolness factor to the ArduinoIDE #4084

lmihalkovic opened this issue Nov 5, 2015 · 6 comments
Assignees
Labels
Type: Invalid Off topic for this repository, or a bug report determined to not actually represent a bug
Milestone

Comments

@lmihalkovic
Copy link

Aside from the bang-on-feature-set and quality of the board, IMHO the utterly simple approach of the supplied IDE is what made the Arduino a hit... instead of the dark-art that embedded programming has been for years, it suddenly became possible for any teenager to download a single zip and reliably get going in minutes. This is a awesome achievement!!! As time has passed, the IDE as retained the simplicity that made its success while adding capabilities.

IMHO the platform is coming to a cross-roads. The skill-set of programmers keep growing, more rapidly than before I might add, and the current IDE is approaching (some might say it passed it) a point where its minimum feature-set will not longer be enough.

This issue entry is for the purpose of referencing under a single umbrella other individual issues meant to inject a number of capabilities that will give a dose of coolness factor to the current IDE (1.6.5_r5 at the time this is started).

More practical

Nice to haves

External references:
https://groups.google.com/a/arduino.cc/d/topic/developers/KsstENd2384/discussion

@ffissore
Copy link
Contributor

ffissore commented Nov 5, 2015

Thank you @lmihalkovic I'm gonna close this one as it's not really an issue but rather a collection of proposals. Please join the developers mailing list where you can share your priorities with other arduino hackers and receive their feedback and points of view

@ffissore ffissore closed this as completed Nov 5, 2015
@ffissore ffissore self-assigned this Nov 5, 2015
@ffissore ffissore added this to the Release 1.6.7 milestone Nov 5, 2015
@ffissore
Copy link
Contributor

ffissore commented Nov 5, 2015

@ffissore ffissore added the Type: Invalid Off topic for this repository, or a bug report determined to not actually represent a bug label Nov 5, 2015
@lmihalkovic
Copy link
Author

Yes, thanks for the pointer, I will join.

@NicoHood
Copy link
Contributor

NicoHood commented Nov 5, 2015

You always show screenshots of those features.
If you implemented them already, why not open a PR or at least upload the fork changes so people can recompile the IDE and try it out? Or am I missing something?

@lmihalkovic
Copy link
Author

This is working code, with probably still half the tr() calls missing where they should be (which reminds me that I still don't know how to update the resource files). I recently got an arduino, and in the process of discovering it, I started running into pain points with the IDE. Considering the maturity of the IDE I figured I couldn't be the first one... Except for the debugger, these are small tasks requiring remarkably little work with the editor the way it is today. Having a bit of time on my hands, I decided to write code partially to test the ideas, partially to make myself more productive, partially to make others more productive (this is very subjective as it assumes that my solutions are general enough that they make sense to others).

My time for this effort is very limited to a few hours per day, and I will soon have to return to other things altogether. I work from a series of branches that I rebase against the official code. Some of the features would be moving faster with a bit of help (mostly simply question answers) from people who know the environment better than I do (for e.g. I still don't know if there is a keywords.txt for the code platform code, and only started working on .S completion tonight when I realized ASM code also works in the editor). So far I have answered more questions than even the simplest of mine have received answers (not complaining, just sharing an observation).

I have not taken the time to push my tree to my GH fork, and I am not creating PR because either takes time that this week I'd rather spend making progress. On the topic of PRs, I ran into #3484 today. It seems the work spans over the entire year 2015, with some creation date going even further back in time. Other PRs seem to have lingered for variable durations (no doubt subject to the many higher priorities of the maintainers).. I did not see an urgency to me pushing code I started to write last week. I will however post something here when I push the code (I might also save a binary distro before that)

PS: I do however very much appreciate you taking an interest is this effort. thank you.

@NicoHood
Copy link
Contributor

NicoHood commented Nov 6, 2015

Thanks for the answer. I really think you should share the code if you want them to fix it. Even if the patch is not ideal, they might have a simple idea to fix it another way. This helps more than just asking for those features. Also the time of the devs is limited, but trust me, they are doing the best they can. I am hoping that you features will be included to the IDE :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Invalid Off topic for this repository, or a bug report determined to not actually represent a bug
Projects
None yet
Development

No branches or pull requests

3 participants