Ernieift/pico c

This adds a picoC widget to the gcs. Further more UAVObjects are available in user scripts. It also new is an access level management for writing sensible UAVObjects.
Here is a video of working: https://vimeo.com/100625857. Sorry for the poor quality, i try to upload it in HD soon.
Tested on OSX and Linux32-VM.
I'm with you about this. The security levels have been introduced for this. Level 1 enables to write problematic objects in disarmed state only.
I had also thought of some sort of code. But this is nonsense.
The wiki isn't up to date about this. I'll update it soon. How did we introduce a warning within the gcs? What if the gcs scans the script before uploading it for some keywords and ask the author with an "are you sure" box?