Re: Making Whimsy tools user-friendly and findable

2017-05-27 Thread Shane Curcuru
sebb wrote on 5/27/17 5:07 AM: > On 26 May 2017 at 23:34, Shane Curcuru wrote: ...snip... >> A second task is making the /committers/tools list be comprehensive of >> all the available scripts that Whimsy provides. Since many tools are >> access restricted, I plan to put color-coded glyphicon-loc

Re: Making Whimsy tools user-friendly and findable

2017-05-27 Thread sebb
On 26 May 2017 at 23:34, Shane Curcuru wrote: > I plan to implement some UI and documentation changes to most of the > *.cgi in /www, to have simple documentation in every page, as well as > adding some related links to pages. There are a lot of highly useful - > if not required - tools on Whimsy

Re: Making Whimsy tools user-friendly and findable

2017-05-27 Thread sebb
On 27 May 2017 at 03:38, Sam Ruby wrote: > On Fri, May 26, 2017 at 10:25 PM, Shane Curcuru wrote: >> Optimization exercise: how would we turn the output of tools/wwwdocs.rb >> get_annotated_scan(...) into a nightly generated >> /public/whimsy-tools.json? Side effect: learning more about whimsy >

Re: Making Whimsy tools user-friendly and findable

2017-05-27 Thread Daniel Gruno
On 05/27/2017 12:34 AM, Shane Curcuru wrote: > I plan to implement some UI and documentation changes to most of the > *.cgi in /www, to have simple documentation in every page, as well as > adding some related links to pages. There are a lot of highly useful - > if not required - tools on Whimsy n

Re: Making Whimsy tools user-friendly and findable

2017-05-26 Thread Sam Ruby
On Fri, May 26, 2017 at 10:25 PM, Shane Curcuru wrote: > Optimization exercise: how would we turn the output of tools/wwwdocs.rb > get_annotated_scan(...) into a nightly generated > /public/whimsy-tools.json? Side effect: learning more about whimsy > architecture. > > * Inputs (all public files):

Re: Making Whimsy tools user-friendly and findable

2017-05-26 Thread Shane Curcuru
Optimization exercise: how would we turn the output of tools/wwwdocs.rb get_annotated_scan(...) into a nightly generated /public/whimsy-tools.json? Side effect: learning more about whimsy architecture. * Inputs (all public files): - /www/**/*.cgi where line =~ ... PAGETITLE = ... - whimsy-vm4.apa

Re: Making Whimsy tools user-friendly and findable

2017-05-26 Thread Sam Ruby
Shane, go be crazy if you really want! - Sam Ruby On Fri, May 26, 2017 at 6:34 PM, Shane Curcuru wrote: > I plan to implement some UI and documentation changes to most of the > *.cgi in /www, to have simple documentation in every page, as well as > adding some related links to pages. There are

Making Whimsy tools user-friendly and findable

2017-05-26 Thread Shane Curcuru
I plan to implement some UI and documentation changes to most of the *.cgi in /www, to have simple documentation in every page, as well as adding some related links to pages. There are a lot of highly useful - if not required - tools on Whimsy now, and it would be nice to help users find them more