glimmer: first stab at adding settings support

This bumps the rototiller submodule for the new described
settings stuff, among other improvements.

There are some ugly kludges surrounding widget lifecycle since I
destroy setting widgets from their signal callbacks and that
seems to anger gtk/glib.  I'm unclear on what the right way is
here, but leaking for now is relatively harmless.

It seems like gtk+ should be holding a reference on the
respective widget across signal deliveries so the callbacks can
potentialy destroy them with the underlying resource freeing
becoming queued.  Perhaps there's something like signal
propagation up the heirarchy happening and since I'm destroying
the settings frame higher up the tree and not the specific widget
being signaled things fall over.  It's a TODO item to sort out,
at least the resources leaked aren't substantial and it's only on
interactive configuration.

This has also been done in fashion preserving the
--module=foo,bar=baz arguments consistent with classic
rototiller.  You can start glimmer with the same syntax --module=
flag, and it will select the specified module and apply the
supplied settings in a way reflected in the GUI.

There should probably be a new '--go' flag added to enable
starting the rendering via commandline.  As-is glimmer will
always leave you at a settings dialog waiting for a "Go!" click,
even if you specified module+settings comprehensively via the
CLI.

1 files changed, 0 insertions, 0 deletions

diff --git a/rototiller b/rototiller
-Subproject 4960649f21582a74e949a62b8fde8067852ffab
+Subproject ee8e2327cda0fd093cb6660f98cc43b4e8f2329