Reply to thread

Message

<blockquote data-quote="Guest 6801328" data-source="post: 8003806">This is really coming along!What I'm wishing for are two features:<ol>
<li data-xf-list-type="ol">The ability to compare more builds simultaneously.</li>
<li data-xf-list-type="ol">An easy way to post/share builds.</li>
</ol>I'm not sure if this is possible with the libraries you're using, but if I were building it manually this is what I might do:<ol>
<li data-xf-list-type="ol">Instead of two identical input interfaces on opposite sides, just one, with an &quot;open/close&quot; toggle (like the sort that collapses a folder view in a file browser.).</li>
<li data-xf-list-type="ol">An &quot;Add New Build&quot; button, or maybe a &quot;Duplicate This Build&quot; so that you don't have to start from scratch each time.&nbsp; Each new build you add appears as another line in the chart.&nbsp; The open/close buttons enable you to pack a bunch of them on the screen without overcrowding.&nbsp; (I might even set it up so that only one can be opened at a time...but would want to test out whether that's annoying.)</li>
<li data-xf-list-type="ol">Add a text field to the build interface that displays an alphanumeric string representing the build.&nbsp; (Basically you come up with a scheme...a code...to represent builds, then convert it into a base-36 or base-62 number). To share a build, you just copy this string and post it in the forum.&nbsp; Somebody else can copy/paste that string into the same text field and...presto!...build shared.</li>
<li data-xf-list-type="ol">Finally, add a utility (maybe on the right side of the chart) that shows only the deltas between the builds currently displayed.&nbsp; Currently it's too easy to lose track of how the builds differ.&nbsp; For example, if the only thing different is that one has Great Weapon Master and one doesn't, then the only thing in this new panel is something like &quot;Build 1: Great Weapon Master (true)&quot; and &quot;Build 2: Great Weapon Master (false)&quot; or something like that.&nbsp; That way you can double check that you're testing what you think you're testing.</li>
</ol>Again, none of this might be possible with those libraries.&nbsp; It would require a whole bunch of server-side javascript.&nbsp; Just sorta daydreaming here.</blockquote>

[QUOTE="Guest 6801328, post: 8003806"] This is really coming along! What I'm wishing for are two features: [LIST=1] [*]The ability to compare more builds simultaneously. [*]An easy way to post/share builds. [/LIST] I'm not sure if this is possible with the libraries you're using, but if I were building it manually this is what I might do: [LIST=1] [*]Instead of two identical input interfaces on opposite sides, just one, with an "open/close" toggle (like the sort that collapses a folder view in a file browser.). [*]An "Add New Build" button, or maybe a "Duplicate This Build" so that you don't have to start from scratch each time. Each new build you add appears as another line in the chart. The open/close buttons enable you to pack a bunch of them on the screen without overcrowding. (I might even set it up so that only one [I]can[/I] be opened at a time...but would want to test out whether that's annoying.) [*]Add a text field to the build interface that displays an alphanumeric string representing the build. (Basically you come up with a scheme...a code...to represent builds, then convert it into a base-36 or base-62 number). To share a build, you just copy this string and post it in the forum. Somebody else can copy/paste that string into the same text field and...presto!...build shared. [*]Finally, add a utility (maybe on the right side of the chart) that shows only the deltas between the builds currently displayed. Currently it's too easy to lose track of how the builds differ. For example, if the only thing different is that one has Great Weapon Master and one doesn't, then the only thing in this new panel is something like "Build 1: Great Weapon Master (true)" and "Build 2: Great Weapon Master (false)" or something like that. That way you can double check that you're testing what you think you're testing. [/LIST] Again, none of this might be possible with those libraries. It would require a whole bunch of server-side javascript. Just sorta daydreaming here. [/QUOTE]

Verification