software autoupdate, support for modifying oculus_settings.txt

[GoogleCodeExporter]

What steps will reproduce the problem?
1. run autoupdate that loads new software that accesses NEW line-items in 
oculus_settings.txt
2.
3.

What is the expected output? What do you see instead?
failure on accessing new settings line-items, since current auto-update doesn't 
update oculus_settings.txt

Please use labels and text to provide additional information.

add routine to go thru each line item from new oculus_settings_default.txt, add 
default values, remove old/unused values

Original issue reported on code.google.com by skyz...@gmail.com on 28 Apr 2011 at 2:24

[GoogleCodeExporter]

Original comment by skyz...@gmail.com on 28 Apr 2011 at 2:24

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

I'll handle this one.

Original comment by brad.zdanivsky on 28 Jul 2011 at 6:29

[GoogleCodeExporter]

are we sure we want to remove other settings? Like developer, notifyonlogin 
etc? I'll create an enum of manditory settings.  

Original comment by brad.zdanivsky on 30 Jul 2011 at 9:51

[GoogleCodeExporter]

Original comment by brad.zdanivsky on 1 Sep 2011 at 7:35

• Changed state: Started

[GoogleCodeExporter]

Re: are we sure we want to remove other settings? Like developer, notifyonlogin 
etc? I'll create an enum of manditory settings.  

don't remove *any* settings unless they are obsolete, make sure all settings 
are there that new code relies on

Original comment by skyz...@gmail.com on 1 Sep 2011 at 7:51

[GoogleCodeExporter]

yes, will add email etc settings not yet accessible to the client into the GUI 
too (developer menu)  

Original comment by brad.zdanivsky on 1 Sep 2011 at 7:53

[GoogleCodeExporter]

if they're developer settings don't bother -- unless you need to change them 
all the time, so would rather access from GUI

Original comment by skyz...@gmail.com on 1 Sep 2011 at 7:56

[GoogleCodeExporter]

things like email.. can ask, but optional in init.html

Original comment by brad.zdanivsky on 1 Sep 2011 at 8:01

[GoogleCodeExporter]

call Settings.writeFile() to clean out settings and organize the file 

Original comment by brad.zdanivsky on 5 Sep 2011 at 6:29

[GoogleCodeExporter]

suggestions (@ rev 356)
-remove 'developer account' and 'hold servo' checkboxes in 
initialize.html--only bare bones settings to get server operational should be 
there, rest in client
-when calling 'restore factory settings' from client, do NOT remove admin 
account, (since won't be able to login again from client)
-move 'restore factory settings' to menu section 'calibration/settings'

(BTW -- for future reference, 'hold servo' should default to OFF--may cause 
premature death if used continuously on new servo, needs more testing to know 
for sure)

Original comment by skyz...@gmail.com on 9 Sep 2011 at 4:43

[GoogleCodeExporter]

I think this one is fin...

Original comment by brad.zdanivsky on 11 Sep 2011 at 10:17

[GoogleCodeExporter]

Original comment by skyz...@gmail.com on 2 Nov 2011 at 6:23

• Changed state: Fixed