I understand the java/eclipse argument very well. That is why I will
accept the pull request when V3 is released.
It makes the behavior more eclipse like. It is just another way to do
the same thing. I'll have a look at it when it is integrated.
Best regards
Jantje
On 29-02-16 14:54, Jan Baeyens wrote:
I have been doing the most of the development with win 10 so win 7 is less tested
On 29-02-16 13:58, Roberto Lo Giacco wrote:
Thanks Janje,
I thought I was on the list from day one, apparently the "send email to subscribe" didn't work for me as I did that twice.
Anyway, yes, that seems to perfectly match my idea, at least from a functional perspective. Probably I was imagining a different UI, but my perspective is driven by the Java side of Eclipse (which I use on a daily basis).
I can test the V3 today on Win7 and/or Win 10 64 bit, do you have any preference?
Roberto
On Mon, Feb 29, 2016 at 1:43 PM, Jan Baeyens <jan@xxxxxxxxxx <mailto:jan@xxxxxxxxxx>> wrote:
Roberto
Welcome to the developers list.
What you are describing is very close to what is in a pull
request waiting for V3 to be released:
https://github.com/jantje/arduino-eclipse-plugin/pull/376
However I advice to also read my answer as I see little added
value as we already have multiple configuration (which I would
call multiple board types) which supports different com ports and
different board types.
The fact that the switching of the com port (which I would call
multiple boards of the same type) forces a rebuild is a long
lasting issue which I have in mind to fix for patreon users only.
https://github.com/jantje/arduino-eclipse-plugin/issues/80.
Best regards
Jantje
PS: Note that the patreon user only stuff is something I want to
discuss here as soon as V3 is out the door.
On 29-02-16 13:06, Roberto Lo Giacco wrote:
Hi guys,
I'm really pleased by your achievements on Toddler and I'm here
to contribute an idea which might be helpful, at least on my
projects: support for multi boards on one project.
Practically speaking we are currently assigning the board and
the com port to the project, while I'm suggesting to decouple
that into another view so to have multiple boards and coms
associated to a project. this way it will be very easy to upload
the same project to multiple targets and I'm obviously
suggesting to keep the compiled code for the different boards
separately, so to prevent the full recompilation each and every
time.
We can consider those as "deploy targets", each one having an
associated board type: if I have 5 pro minis on 5 com ports I
will only need one compiled code, but I can have 5 com ports
configurations.
If I understand correctly the process, selecting a board now
selects the toolchain and prepares the compile and upload
commands, with an additional parameter to be the com port.
If you have any experience with Java and web projects, we have
another view to decide which project goes onto which server and
this is the kind of decoupling I'm suggesting.
So, this view can be the "deploy targets" view, where the
configured boards are listed (arduino uni, teensy, etc...) and
under those there are the associated com ports (some may be
repeated, obviously).
Obviously this is not high priority as I'm not sure many need
this feature, but can be a nice addition which might help us
distinguish from other projects.
Open for comments and thoughts,
Roberto
