In React (Javascript):

• unit conversion: mm to in, in to ft
  • mm2in()
  • in2ft()
• assuming the value in 7.125 inch rounded to nearest divisor of an in
  • analytically: floor(7.125) + ceil(0.125*divsor)/divisor "in"
  • interpolation: x=0:divisor:1; i=interp1(x,0.125,'ceil'); y=x(i);
• assuming the value in 7.125 ft rounded to nearest ft + divisor of an in
  • analytically: floor(7.125) "ft" + ceil(ft2in(0.125)*divsor)/divisor "in"

In Python:

- [Two routes, one for each method to learn differences between dynamic ON-EVENT and PUT/GET static

Actions

• Using https://github.com/Eyongkevin/hello_template/tree/master as a template, locally serve a hello world application using Python3, Flask, Bootstrap, and React.

• Learn about the node.js javascript framework, npm javascript package manager, and webpack.

• publish to github pages https://divisor.onrender.com/

Production

The npm command I use to build executes webpack in developer mode. The deployed website, https://divisor.onrender.com/, loads slowly on my phone. Use official guidance to convert to production mode. I'm not going to install another plugin, the webpack command can take a command line argument, i.e. mode=production

I think this will "minify" css and js in the project, hopefully speeding up loading time.

Actions:

• Add motivation/background to README.md:

• Add CHANGELOG.md

• Specify requirements in REQUIREMENTS.csv:

  • back-end functionality
  • front-end design
    • mobile and desktop friendly
    • dynamic fields

• Research tech stack in this issue

  • automated requirement verification (code coverage)

Ideas

• when rounding with smaller divisors, i.e. 4, 8, provide an error indication to right of output.
  • e.g. Error: ⬆️ #.###
• woodworking and machinist tabs: in machining a tenth it 0.0001, not 0.1.
• add a feature to calculate divisions of measurement, allowing for accounting of "saw blade kerf"

Input Fields

• add input label to divisor drop-down, and use a default value of 1/16, this way we can remove input validation for this aspect of tool.
• allow for numeric keyboard on mobile devices
• allow mathematical expressions, triggered on = or just do the math provided
• fix bug when "1." entered and "0" returned.
  • I believe input fields are "string" and feel that "1." may change type to "float." I need to enforce input option type specification/casting.