Allow to pass options through to GUI

[jgosmann]

Allow to pass GUI arguments to pytry that will be passed on to the nengo GUI

GUI arguments:

  -p [PASS], --password [PASS]
                        password for remote access
  --cert CERT           SSL certificate file
  --key KEY             SSL key file
  -P PORT, --port PORT  port to run server on
  --debug               turn on debug logging
  -b BACKEND, --backend BACKEND
                        default backend to use
  --browser
  --no-browser
  --auto-shutdown AUTO_SHUTDOWN
                        Time limit before automatic shutdown. Set to 0 to
                        deactivate.

[tcstewar]

Ooo... nifty idea. That'd also be a good excuse to take a look at nicer ways of passing those sorts of settings into nengo_gui.....

Another option that I've also been batting around a bit is to make nengo_gui aware of NengoTrial objects. That'd be a pretty trivial change to nengo_gui (if you don't find a model, check if there's a single NengoTrial class defined, and if so, instantiate it and call make_model() on it), would automatically give access to all these nengo_gui parameters, and it'd mean you can use the editor in nengo_gui.

Right now, you can get a similar effect by putting this at the end of your file:

if __name__ == '__builtin__':
    model = MyNengoTrialClass().make_model()

but it'd be nice to not have to do that....

[jgosmann]

To me it seems more flexible if nengo_gui needed not to be aware of pytry. Maybe one could pass on the nengo_gui instantiation some additional code that is used to create the model?