I'm interested to see this. It's not clear to me if the menu is an extension to the webapi, or a separate "control" process with a GUI menu, or something else.
I recommend publishing the code into a public repository. A test grid cap is pretty stylish though. ;-) Nathan / nejucomo On Wed, Oct 9, 2013 at 10:23 PM, Garonda Rodian <[email protected]> wrote: > As there had been some interest in a menu for tahoe, I've started picking up > a little Python, and have sketched out a very basic proof of concept. At > this time, it can create an Introducer, and while it's extremely basic (so > as to be able to run on even a Raspberry Pi), I'd like to ask for general > comments on how to improve it. > > First question: How should I share the code with the list? I suppose at a > current 6KB, I could simply put it on the test grid and publish a RO cap :). > > Future work will include both fleshing out the menus, and some method to be > determined of saving a session, probably the creation of a python script > that simply calls the "do something" functions with the parameters as they > were give, so a given setup can be recreated without going through the menus > again (i.e. as an automated installer for test grids). > > Thank you all for your time and assistance! > > _______________________________________________ > tahoe-dev mailing list > [email protected] > https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev > _______________________________________________ tahoe-dev mailing list [email protected] https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
