Marcelo I believe you deserve to be in there, you did a great job,
something none of us would have been capable to do.
I would also suggest Marcelo reviews the graphical aspect of the
presentation so to give it a better first impression: would you agree Jan?
Obviously if Marcelo can spare some more time for this...
If there will be WiFi (I hardly believe there will not be) then I would
suggest to use prezi.com for the presentation and I can work with Marcelo
on this once the contents are solid (here is an example
<http://prezi.com/lsrekxxxyhnj/?utm_campaign=share&utm_medium=copy&rc=ex0share>
of a prezi presentation). That obviously unless EclipseCon haven't asked
you to specifically use their template (which I believe they did).
But also I wouldn't assume there is going to be WiFi (unless they gave you
this info), so we either bring some USB pen drives or any other mean to
distribute the plugin.
Regarding the presentation contents it looks like a checklist, which I
believe it is good for a workshop, but there are some points I don't
understand or where I can suggest improvements:
1. why are we asking for their competencies on
C++/Eclipse/Arduino/Eclipse? I mean, will it make any difference for the
workshop? Are you planning to tailor it depending on the audience
knowledge? Speaking at EclipseCon I hardly believe there will be someone
not knowing eclipse :-D
2. the comparison in table format doesn't provide a sense of confidence
because we are reporting numbers without providing any trusted source
backing them up. If we want to give a comparison table of some sort we can
use a semaphore (green, yellow, red), but the numbers are too much IMHO
3. If we run a comparison, shouldn't we also include the "semi official
arduino plugin"? I know it might raise some competition, but I don't think
just ignoring its existance will be beneficial....
4. I would avoid using both V3 and Toddler together: if we go for
codenames (which I like) then Toddler is the official release name,
corresponding to an internal only version number. Using the two together
communicates we are still transistioning or haven't decided yet
5. I believe we should bring a project reporting a valid, real life,
representation of which benefits Sloeber brings when you decide to scale up
in arduino development, when a firmare gets bigger than just one .ino file.
That might be shown at the end of the workshop or when we describe the
features, to practically demonstrate how refactor, code browsing and the
other cool stuff works.
6. In case we have many people completely ignoring what ArduinoIDE is,
might it be usefull to open and show that a bit?
So, all together, I believe it's a good decision to start with the
preliminary tasks first (so you can speak while they are still
downloading), but I would rather change some titles:
- *Preparation* (or *Meanwhile I get you bored* if you want to be ironic)
- *Who are we?*
- *What is Sloeber?*
- *Let's play!*
- *The cool stuff* (Advanced)
In the *What is Sloeber?* section I would mention a little bit of history
about the plugin (version1, version 2, etc...) to communicate this is not a
brand new and unstable project, but something who has already gone through
multiple iterations.
I also suggest each one of us, in his own page, publishes some connecting
information (twitter, email, blog?) to demonstrate we are there for real.
I would also add a final page with all the relevant links and urls (mailing
list, twitter, patreon, etc...) where you can also explain the way the
project is managed, the fact the project stays alive under two conditions:
our time availability and your patreon supporters.
On Tue, May 24, 2016 at 1:16 AM, Marcelo Limori <x4j7h32m@xxxxxxxxx> wrote:
My two cents:
- The name's Marcelo (Limori is the last name). But there's no need to
include my name in there, I just drew a logo and splash screen. :)
- You mention at some point that it is compatible with ino files. I would
add (as it's a big selling point to me personally) that the structure of an
Eclipse project is 100% retro-compatible with the structure of a project
written with the Arduino IDE. So if at some point in the future, for some
strange reason, you want to go back and compile with the Arduino stuff, you
can.
- I see you will talk about this in a section, but anyways, I'd stress
very very much the auto-complete, refactor and navigation stuff that we all
know very well. In my experience beginners (to programming at least, people
that never coded with a full IDE) don't seem to comprehend how much better
your life can be if you can just Ctrl-click a method and jump to its code
directly or Ctrl-space to see a list of parameters in a function call.
- You might want to briefly touch the "workspace" concept as it's also a
thing beginners seem to have trouble with.
On Mon, 23 May 2016 18:33:13 -0300, Jan Baeyens <jan@xxxxxxxxxx> wrote:
Hi
attached is the workshop presentation I'm working on. The first part is
based on previous work so is ok (content wise) the last part is still
"expanding".
I have a slide for each of us to represent yourself. I advise not to
leave it to me to make a picture of you. :-) I guess you all know what
that would look like.
If there is something you feel that is missing or needs more attention
... just share your thoughts.
Best regards
Jantje
--
Using Opera's mail client: http://www.opera.com/mail/
<a href="https://www.freelists.org/list/eclipse-arduino-dev>
eclipse-arduino-dev@xxxxxxxxxxxxx</a>
