Graphical Input View

[grumpyinca]

Ideas for a new "View" are under discussion. This issue was previously called "Guided View" to emphasize guidance to the user described in the final paragraphs below. It is now referred to as "Graphical Input View".

A number of things distinguish Graphical Input View:

• Selectable variable names on top of an image backdrop.
• No default values. See issue: #462.
• A continue button that performs a search and then provides a dialog specific to the feasible status of the results

Here is a possible image backdrop: Perhaps user feedback should be acquired for a compression spring implementation before extending Graphical Input View to other spring types.

Hovering the cursor over the variable names should produce a tooltip. Clicking a variable name should produce a pop-up modal dialog box similar to what right-click does in Calculator View.

Clicking the Continue button should run a search and either produce a pop-up modal dialog box or a complete new page (tab?) that is specific to the result of the search.

• If the result is feasible, there should be an explanation of the possible design situations (under-specified or properly-specified). If under-specified, go back and adjust FIXes & constraints. If properly specified, try the Seek feature.
• If the result is not feasible, there should be an explanation of the possible design situations (over-specified or properly specified with overly ambitious goals). If over-specified, go back and adjust FIXes & constraints. If properly specified with overly ambitious goals consider using the Trade feature. There should be an explicit test for violation of FS_2 MAX. If this constraint is violated, describe the implications of over-design, suggest that the constraint can be disabled or the constraint level modified.
• Provide all the warnings currently provided by Report1 & Calculator View. Provide buckling indicator (icon with tooltip?)

Offer the opportunity to switch to a different view.

When a satisfactory design is established, select a standard wire size and then execute another search to resolve any resulting constraint violations. Note that the guidedDesign tutorial session provides more detail on this approach. See: Add SelectSize+Search and SelectSize+Seek #406.

[1fifoto]

Make two React Components. One for Force-Deflection graph. One for Side-view representation. Add Symbol Value uses for all user input. Incorporate into Calculator view (either above [preferred] or below today's spreadsheet like view). A/B test to see behaviorally what user's interact with the most: (a) Today's spreadsheet like calculator view or (b) these two new React Components.