My input for the new and noteworthy
So what is so new and impressive?
1) The Arduino eclipse plugin now contains a boards and library manager
like the arduino IDE.
As such you do not have to go to the arduino ide to install/upgrade your
boards.
Actually you do not need the arduino ide at all.
2) Install and play.
If you go for the product you only need to install the product.(!!!!No
need to install a arduino IDE!!!!!!)
At first startup the plugin downloads the arduino avr boards and toolchains
And configures itself.
So no configuration is needed at all for Arduino avr boards.
3) Auto include of the arduino libraries.
In your code add #include "Library I use" and save the file. The library
will be added to your project fully automatically.
Try to delete it when you uses it. Won't work :-) Why? Because you use
it it will be added back in fully automatically.
4)Auto opening of serial monitor.
Do you hate to open a serial connection in the serial monitor? Pressing
plus, selecting the com port, selecting the baud rate and clicking ok.
Now just select the project you want to connect to and press the open
serial monitor button on the toolbar. Bingo you are connected.
5)Better information integration
The board and the port of your project is now visible in the project
manager.
6) Better support for ino files.
Ino files are now fully supported in the toolchain. Which means: only
ino files are only compiled if needed and also compilation will work
with the standard eclipse build commands.
7) For the die hards: multi arduino version support.
In the arduino ide you can only have 1 version of a platform at a time.
You can downgrade or upgrade the platform but not install 2 versions.
The Arduino Eclipse plugin supports multiple (if you want all) versions.
This way you do not have to upgrade all your projects (at once).
Of-course there are also some bug fixes. But is that worth mentioning
with the impressive list above?
Op 23/01/2016 om 21:28 schreef Wim Jongman:
Sure, no problem.
On Thu, Jan 21, 2016 at 9:54 PM, Jan Baeyens <jan@xxxxxxxxxx <mailto:jan@xxxxxxxxxx>> wrote:
yes point 5 :-)
Op 21/01/2016 om 21:27 schreef Wim Jongman:
I have been offline. Any things that require attention from me?
On Jan 21, 2016, at 15:57, Jan Baeyens <jan@xxxxxxxxxx
<mailto:jan@xxxxxxxxxx>> wrote:
A small update on the progress
1) Get Teensy to work nicely
Done (Add [teensyduino]/hardware/teensy to private paths
It works but the platform.txt needs to be modded. Paul will
(if test turn out ok in teensyduino) change this in
teensyduino 1.2.8 (no idea when that will be released)
2) fix for 325
Done. I think this is a cool feature.
I want to add a turn on/off functionality in case things go
wrong (default on)
3) board name- port-baut rate in project explorer (like the
version control tools do but I don't find how :-( )
Done but I skipped the baud rate for a cool reason
4) complete #349
Done.
I want to add a turn on/off functionality in case things go
wrong (default on)
5) fix for 347
Done
But I would like input from wim on "why is the plugin is
still using the old location".
Can you debug it.baeyens.arduino.common.getInstallationPath()
on your system? Please...
I think this may be related to the things in 7
6) documentation (all your items)
Still open
7) testing
Kind of like started as we are now on the nightly.
2 people (both linux) reported problems which look like
failing dowload
https://github.com/jantje/arduino-eclipse-plugin/issues/353
https://github.com/jantje/arduino-eclipse-plugin/issues/354
Seems like there is some issue left there.
I also would like to fix 311 (normal build does not generate
.ino.cpp)
This because default now a build is started and that one
fails if you have a ino project which is any project stated
from a sample.
Best regards
Jantje
Op 16/01/2016 om 20:10 schreef Jan Baeyens:
Good to see there is a +1 for merging.
Following things I would like "done" before releasing
1) Get Teensy to work nicely
2) fix for 325
3) board name- port-baut rate in project explorer (like the
version control tools do but I don't find how :-( )
4) complete #349
5) fix for 347
6) documentation (all your items)
7) testing
of which 1 is something I'd like for merging but I fear that
won't work out fully.
I have made a wiki page on the release process :-)
https://github.com/jantje/arduino-eclipse-plugin/wiki/The-release-process
more below
Op 16-1-2016 om 19:03 schreef Wim Jongman:
+1 for merging. When do you want to release and what isI'm well endowed in ccm with several tools (f.i. clearcase
still pending for this release?
Since you can now see the beauty of branches, how about
using git flow. I am happy to give anyone a short
demonstration and some general background on git's internal
structure (as far as i know it ;).
clearquest, rtc) but I seem to have a problem with git
terminology. So yes a demonstration would be great.
What are the things that still need to be done?
### Documentation.
* New and Noteworthy for this release
* How does the workflow change for someone that currently
has a Arduino IDE installed?
* 3.0.0 FAQ
* Website changes?
### Fixes
* The long path problem
* Keeping hold of the installation path
* Moving the install_path application parameter to a java
property?
I'm not sure what you mean with
* Keeping hold of the installation path
* Moving the install_path application parameter to a java
property?
On Fri, Jan 15, 2016 at 11:54 PM, Jan Baeyens
<jan@xxxxxxxxxx <mailto:jan@xxxxxxxxxx>> wrote:
I'm not sure what you guys think about it but I feel it
is about time to push branch "big change" to the
"master" branch.
I think we increased the user experience and the
version is stable enough to make it the nightly.
I propose to make a branch 2.4 -just before pushing big
change to master- just for sakes of history.
Best regards
Jantje
<a
href="https://www.freelists.org/list/eclipse-arduino-dev>eclipse-arduino-dev@xxxxxxxxxxxxx
<mailto:eclipse-arduino-dev@xxxxxxxxxxxxx></a>
