Author: atagar Date: 2011-02-26 02:49:26 +0000 (Sat, 26 Feb 2011) New Revision: 24266 Modified: website/trunk/getinvolved/en/volunteer.wml Log: Low priority project idea for an arm gui. Modified: website/trunk/getinvolved/en/volunteer.wml =================================================================== --- website/trunk/getinvolved/en/volunteer.wml 2011-02-25 05:17:40 UTC (rev 24265) +++ website/trunk/getinvolved/en/volunteer.wml 2011-02-26 02:49:26 UTC (rev 24266) @@ -388,7 +388,8 @@ <p> <b>Project Ideas:</b><br /> - <i><a href="#armClientMode">Client Mode Use Cases for Arm</a></i> + <i><a href="#armClientMode">Client Mode Use Cases for Arm</a></i><br /> + <i><a href="#armGui">GUI for Arm</a></i> </p> <a id="project-orbot"></a> @@ -1206,6 +1207,38 @@ </p> </li> + <a id="armGui"></a> + <li> + <b>GUI for Arm</b> + <br> + Priority: <i>Low</i> + <br> + Effort Level: <i>High</i> + <br> + Skill Level: <i>Medium</i> + <br> + Likely Mentors: <i>Damian</i> + <p> + Arm has several unique features, some of the most interesting being its + connection listing (correlating netstat results against the Tor consensus) + and configuration editor (a quick method for editing Tor's config, with + information pulled from the control port and man page). However, since arm + is a command line controller it's of limited appeal to certain sets of + users. This project would be to build a GTK or Qt frontend for the + controller, providing similar features set but with a windowed interface. + </p> + + <p> + The vast majority of arm's more interesting functionality lies in its + backend <a + href="https://svn.torproject.org/svn/arm/trunk/src/util/">utilities</a>, so + there should be little to no work decoupling the CLI from its backend. + Instead, this project would mostly be UI hacking and experimentation, + trying different interfaces to find something that's elegant and simple, + but matches the information found in the current terminal application. + </p> + </li> + <!-- <li> <b>Help with independent Tor client implementations</b>