Provide a sketch navigation/outline view

[lmihalkovic]

Even something seemingly simple as a single file sketch is in reality a more complex application silently pulling on multiple resources under the surface. The idea here is to be able to easily visualize these resources, without taking away any of the current beautiful simplicity.

Well done, this feature is the doorway to many other possible extensions.

Proposed reference design:

Expanded view (references is inappropriate)

[lmihalkovic]

Done

[lmihalkovic]

I am at the point where i will be able to automatically add the #include statements to the sketch source code when the user clicks on a checkbox near the name of a lib in the outline view [chk boxes to ba added soon] or automatically heckbthe right boxes when the sketch is loaded, and remove them when a #include is removed.
The point is code or clicks are fully interchangeable. And the include search path will be passed accordingly (i have my own compiler that supports that)

[lmihalkovic]

I also have a experimental [read ugly read boxes] design for

• when the selection is a file inside "References" (meaning a ref to a system library): moving references up and down in the outline view to decide on the link order. Default behavior is the order of the #include statement in the code (moving the refs up/down) does the same to the #includes in the source file.
• when the selection is a file inside a sketch: changing the order of the tabs inside the sketch
• when the selection is a file inside a library: changing the order of the tabs in this library

System library source files can only accessed RO, so there is no point in changing the order of the tabs to view these files

[lmihalkovic]

Lastly, i was thinking about making the #includes section of a sketch read only with a nice shadowed box around to signify that although it is source code, the IDE owns it (use the outline to add/remove/moveup/movedown the individual #include statements).. But dunno if would be useful or confusing. For each of the selected references (i.e. library), the IDE could systematically generated a guarded include statement like:

#include <XXXXXXXX.h>
#ifndef XXXXXXXX_lib
#error Library XXXXXXXX is required by this sketch
#endif

to ensure clean reporting even from the command line. but there are pitfalls with this approach... so at best it should be opt in... [#warn instead of #error, or some other checks - Like for e.g. I can actually test if the lib in question has the #define XXXXXXXX_lib and only generate the guarding code if things won't break]

and if we want to be really finicky.. there could also be some sort of a XXXXXXXX_ver macro....