but I wasn't 100% sure what version of which sketch I had installed on it.
So, what do you think?
Quotebut I wasn't 100% sure what version of which sketch I had installed on it.building a version string /signature in your sketch to be displayed at start up could solve that for less than 20 bytes(?)
That said, I like the idea but it should be optional as some of my sketches leave no room even without source in ti In fact the idea is quite old, every interpreting computer - e.g. the Commodore 64 - did/does store the source in memory
QuoteSo, what do you think?Well it would make the downloading process much longer and it would limit the program size, just so someone who forgot what code was downloaded into the system could get it back.Not much of a gain for the pain.
The idea has usefulness that is somewhat inversely proportional to how likely it is to work.It works really well for small sketches like BLINK, but who cares? As your sketch gets bigger and more complicated, it would be more useful, but it's less likely to work :-(
Saving a copy of the source doesn't get rid of the need for reasonable discipline in version control.
If you have 16k of source with no other markings (like version numbers), and are trying to figure out what it does compared to other source for the same sketch that is 6 months newer (or older), you're probably ... in trouble.
I wonder if some intermediate level of information stored in flash would be nearly as useful? Sketch name and date, perhaps (+ username + computername + ip address? Gotta make those arduino chips traceable in case someone uses them for evil purposes.)
This suggestion is more in the spirit of making the development process simpler, as opposed to improving the developer
... or better writes a copy of the source to your personal cloud ..\..\myCloud\ArduinoSketches\$UUID$.pde
Again I ask, where is the harm in an option to include the source if it fits?
QuoteAgain I ask, where is the harm in an option to include the source if it fits?There is no harm as long as it is an option which is default off.
The harm can be that * I want have access to the source of the sketch, but don't want to publish the source to my customer. (intellectual property)
* The size of larger sketches do not fit anymore (mentioned before) especially well documented sketches => I have several sketches that are 25K+ in size
* one need to store the used libraries too if you want to be able to debug it in detail ... or at least there version numbers* IDE version, compiler version etc need to be stored too (that are not so much byts)* ....
Maybe even more, but if I must be able to recreate my PC configuration which I needed to compile and debug this app one need to go this far (in the medical IT world companies even have working windows 3.1 compiler configs as customers still have them in the field.... That is the only way to give 100% service.In theory - and I think quite far in practice - my proposal can realize this. It can store the compile environment including version numbers of IDE, avrtools and OS name/version (although it doesn't need to backup those)OK, for hobby purposes it doesn't need so "extreme" but just to give you food for thought