<div dir="ltr"><div>+1 <br></div><div><br></div><div>(in particular I'd be interested about 1 and 3) </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 9, 2020 at 7:43 PM Andrew Sutherland <<a href="mailto:asutherland@asutherland.org">asutherland@asutherland.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Are people interested in a session(s) at the All-Hands on Searchfox? If <br>
you're interested in any of the following things, please email me here <br>
or at <a href="mailto:asuth@mozilla.com" target="_blank">asuth@mozilla.com</a> or let me know via other channels, and let me <br>
know which of the following you'd be interested in. My goal is to get a <br>
rough count so I can try and book a room if there's interest.<br>
<br>
<br>
1. Contributing to Searchfox. Want to improve something about <br>
Searchfox? You can!<br>
<br>
We can help you get set up with a local VM and credentials to try your <br>
changes on mozilla-central in the cloud without your laptop melting <br>
down! Already tried contributing and tried to melt your own laptop down <br>
out of frustration with setting up VirtualBox? We can help with that <br>
too! (Also, you can now use libvirt and save yourself a bundle in new <br>
laptops!)<br>
<br>
Already have the VM setup and appreciate the extensive Searchfox <br>
documentation at <a href="https://github.com/mozsearch/mozsearch/" rel="noreferrer" target="_blank">https://github.com/mozsearch/mozsearch/</a> and <br>
<a href="https://github.com/mozsearch/mozsearch-mozilla/" rel="noreferrer" target="_blank">https://github.com/mozsearch/mozsearch-mozilla/</a> but want some guidance <br>
on how to implement the thing you want to do? We can help with that <br>
double too!<br>
<br>
<br>
2. Talking Searchfox UX, especially as it relates to upcoming <br>
features/possibilities on the "fancy" branch.<br>
<br>
I've been doing some hacking to support a more structured representation <br>
of data to support creating diagrams[1] for both documentation purposes <br>
and to make code exploration and understanding easier.<br>
<br>
This potentially opens up a bunch of new features like <br>
<a href="https://clicky.visophyte.org/files/screenshots/20190820-174954.png" rel="noreferrer" target="_blank">https://clicky.visophyte.org/files/screenshots/20190820-174954.png</a> <br>
demonstrates, providing both the type of a thing you've clicked on, plus <br>
being able to see its documentation or uses without having to click <br>
through. But the more features you try and cram into something, the <br>
more potential for them to get in the way of what the user actually <br>
wanted to do. For example, the helpful popup also probably hides the <br>
code you were trying to look at. Should the information be in a big box <br>
at the bottom of the screen like <a href="http://cs.chromium.org" rel="noreferrer" target="_blank">cs.chromium.org</a>? The top? Configurable?<br>
<br>
Also, for the diagrams, how to make them most accessible. My current <br>
approach[2] attempts to leverage the inherent hierarchy into a ul/li <br>
tree-structure that directly mirrors the clustering used in the graphviz <br>
diagram, with in and out edges indicated at each node. Planned work <br>
includes figuring out how to best get NVDA to make those edges <br>
traversable so that the traversal is possible with more than manually <br>
using ctrl-f.<br>
<br>
<br>
3. Talking Searchfox data exposure for your own tools, especially as it <br>
relates to the new data available on the "fancy" branch.<br>
<br>
Do you have a tool that uses Searchfox and wish its result format wasn't <br>
clearly just a data structure pre-baked for presentation purposes that <br>
the receiving JS perform a light HTML-ization on?<br>
<br>
<br>
Andrew<br>
<br>
<br>
1: Here are some examples of diagrams created during prototyping:<br>
<br>
- Manually creation by clicking on calls/called-by edges in iterative <br>
search results exploration: <br>
<a href="https://clicky.visophyte.org/files/screenshots/20190503-133733.png" rel="noreferrer" target="_blank">https://clicky.visophyte.org/files/screenshots/20190503-133733.png</a><br>
- Automatic diagram from heuristics based on local same-file control <br>
flow: <a href="https://clicky.visophyte.org/files/screenshots/20190821-165907.png" rel="noreferrer" target="_blank">https://clicky.visophyte.org/files/screenshots/20190821-165907.png</a><br>
- Blockly based diagramming without rank overrides or colors applied: <br>
<a href="https://clicky.visophyte.org/files/screenshots/20191231-214320.png" rel="noreferrer" target="_blank">https://clicky.visophyte.org/files/screenshots/20191231-214320.png</a><br>
<br>
2: <br>
<a href="https://github.com/asutherland/mozsearch/blob/00a60f899936559ed4d158999278660eb5c98df5/ui/src/grokysis/frontend/diagramming/class_diagram.js#L480" rel="noreferrer" target="_blank">https://github.com/asutherland/mozsearch/blob/00a60f899936559ed4d158999278660eb5c98df5/ui/src/grokysis/frontend/diagramming/class_diagram.js#L480</a><br>
<br>
_______________________________________________<br>
firefox-dev mailing list<br>
<a href="mailto:firefox-dev@mozilla.org" target="_blank">firefox-dev@mozilla.org</a><br>
<a href="https://mail.mozilla.org/listinfo/firefox-dev" rel="noreferrer" target="_blank">https://mail.mozilla.org/listinfo/firefox-dev</a><br>
</blockquote></div>