input-duration 2.0.12 → 2.1.1

package/README.md

@@ -38,34 +38,34 @@
 <div align="center">
   
   
-  <a href="https://github.com/StephanLuis/chronlyhms">
-   <h3 align="center">ChronlyHMS-- Best 'Time Only' Input</h3> <img src="readme/logo.svg" alt="Logo" width="90" height="90">
+  <a href="https://github.com/StephanLuis/input-duration">
+   <h3 align="center">Input-Duration -- The best 'Time Only' Input</h3> <img src="readme/logo.svg" alt="Logo" width="90" height="90">
   </a>
 
   
 
-  <p align="center">A time unit input that works on Safari in close imitation of a time input on Chrome. </p>
+  <p align="center">A vanilla JS boosted input that works on Safari in very close imitation of a time input on Chrome <br>... only better. </p>
 </div>
 
-'Time Only' means that this control is for time as a unit, or a duration, like for count down timers.  Not for time of day nor date on a calendar, so no AM/PM conversions on Safari, no unwanted date-time selectors.  Just time up to 999 hrs and down to 1 millisecond.<br>
+'Time Only' means that this control is for time as a unit, or a duration, like for count down timers.  Not for time of day nor date on a calendar, so no unwanted AM/PM conversions on Safari, no unwanted date-time selectors.  Just time up to 999 hrs and down to 1 millisecond.<br>
 <p>
 <div>
   </div>
     <div align="center">
-    <a href="https://6s0mfy.csb.app/" target="_blank">Demo</a>
+    <a href="https://6mxpg2.csb.app/" target="_blank">Demo</a>
     ·
-  <a href="https://stephanluis.github.io/chronlyhms/" target="_blank">Docs</a>
+  <a href="https://stephanluis.github.io/input-duration/" target="_blank">Docs</a>
   ·
-  <a href="https://codesandbox.io/s/naughty-booth-6s0mfy?fontsize=14&hidenavigation=1&theme=dark" target="_blank">
+  <a href="https://codesandbox.io/s/peaceful-waterfall-6mxpg2?file=/index.html" target="_blank">
   Fiddle
 </a>
   ·
-    <a href="https://github.com/StephanLuis/chronlyhms/issues">Bugs</a>
+    <a href="https://github.com/StephanLuis/input-duration/issues">Bugs</a>
     ·
-    <a href="https://github.com/StephanLuis/chronlyhms/issues">Request Feature</a>
+    <a href="https://github.com/StephanLuis/input-duration/issues">Request Feature</a>
   </p>
   </div>
-  Ok, what about mobile??  Yep, ChronlyHMS works on all popular operating system / browser combinations.  
+  Ok, what about mobile??  Yep, input-duration works on all popular operating system / browser combinations.  
 <br/>
 </div>
 <br/>
@@ -108,28 +108,28 @@
 
 <!-- ABOUT THE PROJECT -->
 ## About The Project
-Time inputs <input type='time'> are updated by browsers in unwanted ways!   Safari on desktop adds AM/PM if the user is in the USA and on mobile the cool scroll time selector does not allow fractions of a second.  The best html5 option doesn't cut it, sadly, so ChronlyHMS was designed and buit for a consistant UX no matter the browser, OS, or location settings.
+Time inputs <input type='time'> are updated by browsers in unwanted ways!   Safari on desktop adds AM/PM if the user is in the USA and on mobile the cool scroll time selector does not allow fractions of a second.  The best html5 option doesn't cut it, sadly, so input-duration was designed and buit for a consistant UX no matter the browser, OS, or location settings.
 
 <!-- [![Product Name Screen Shot][product-screenshot]](https://example.com) -->
 
-<img src="readme/html.png" alt="drawing" width="60%"/>
+<img src="readme/codeDrawing.png" alt="drawing" width="60%"/>
 
 <!-- [![HTML Screen Shot][html-screenshot]](https://example.com) -->
 
-<h3> Bob is rescued by ChronlyHMS! </h3>
+<h3> Bob is rescued by INPUT-DURATION! </h3>
 
-The objective is a minimised vanilla javascript plugin that reproduces the behaviour of the input type=time on Chrome.  This way at least two of the major browsers are supported, Safari and Chrome, on desktop and mobile operating systems. 
+The objective is a minimised javascript plugin that reproduces the behaviour of the input type=time on Chrome.  This way at least two of the major browsers are supported, Safari and Chrome, on desktop and mobile operating systems. 
 
-<i>Does this loose any functionality?</i>  No!  document.querySelector('#bob').value  has a getter and setter!  So values can be set and retrieved by ID.
+<i>Does this loose any functionality?</i>  No!  document.querySelector('#bob').value  has a getter and setter!  So values can be set and retrieved by ID or attribute in HTML.
 
 
 
-<img src="readme/safariBad.png" alt="drawing" width="60%"/>
+<img src="readme/safariBad.png" alt="drawing" width="80%"/>
 <!-- [![Safari Screen Shot][safari-screenshot]](https://example.com) -->
 
-Yes! It seems CRAZY in 2022 that there is not a native 'time only' input for HTML.  What I mean is there is no user input control for time rendered independantly of date or time of day.  Yea, crazy, but now ChronlyHMS is a javascript plugin that creates a UX input control for a value of time simply as hours, minutes, seconds --<b>only</b>! <br> Ever thought, why is it difficult to 'code' a countdown timer? Why can't it be done with one control? Just look at google's timer and other coundown timers! All use multiple inputs, usually designed for integers.
+Yes! It seems CRAZY in 2022 that there is not a native 'time only' input for HTML.  What I mean is there is no user input control for time rendered independantly of date or time of day.  Yea, crazy, but now input-duration is a javascript plugin that creates a UX input control for a value of time simply as hours, minutes, seconds --<b>only</b>! <br> Ever thought, why is it difficult to 'code' a countdown timer? Why can't it be done with one control? Just look at google's timer and other coundown timers! All use multiple inputs, usually designed for integers.
 
-The very worst is Safari on desktop and mobile undermine those snazzy input type=time efforts and update the input depending on OS settings for desktop or provide a control with restricted capability... Shouldn't a user be able to 'scientifically' specify a period of time with one control?  <br>The closest HTML5 input type- time when configured with UX for hours to millisecs is very finicky and rendered differently on Chrome and Safari <b>and</b> mobile is different from laptop, so I've simplified that!
+The very worst is Safari on desktop and mobile, which undermine any input type=time coding efforts and update the input based on OS settings!  Shouldn't a user be able to 'scientifically' specify a period of time with one control?  <br>  Maybe it's just me, but the chrome / google timer is 14 separate elements ... those guys must be paid by the hour.   The closest HTML5 input type- time when configured with UX for hours to millisecs is very finicky and is rendered differently on Chrome than Safari. <b>Mobile</b> is different from laptop<br> ... so I've simplified that!
 
 
 
@@ -137,7 +137,7 @@ The very worst is Safari on desktop and mobile undermine those snazzy input type
 
 
 
-There are a few plugins (links to come) that remediate the lack of continuity, but even time controls with the plugin treat time as a date (ex 24hr max).  So it seems the current state is the most relable UX is multi input type number (more links to come ).  The best example is the Google countdown timer.  And that's wrong because time is a basic unit that should be separate from calendar complexities.  That got me thinking, why isn't there an input control for it implemented across browsers??  I needed one, so coded ChronlyHMS.
+There were a few plugins that remediated the lack of continuity, but even those controls treated time as a date (ex 24hr max).  So it seems the current state is the most relable UX is multi input type number.  The worst example is the Google countdown timer.  That way is wrong because time is a basic unit that should be separate from calendar complexities.  That got me thinking, why isn't there an input control for it implemented across browsers??  I needed one, so coded input-duration.
 
 Here's why:
 * Time is hours minutes and seconds (and millisecs) and needn't be associated with part of a day or a date
@@ -157,14 +157,15 @@ Feel free to vote for WhatWG inclusion of a into the HTML spec! (link comming so
 
 ### Built With
 
-This section should lists any major frameworks/libraries used to for this project. Any add-ons/plugins are in the acknowledgements section.
+
 
 * [Node.js](https://nodejs.org/)
-* [Webpack](https://webpack.js.org/)
 * [Gitpod](https://www.gitpod.io/)
 * [Testing Powered By SauceLabs](https://saucelabs.com)
 * [Selenium](https://www.selenium.dev/)
 
+input-duration is a module and works with webpack. Any add-ons/plugins used in dev are in the acknowledgements section.
+
 <p align="right">(<a href="#top">back to top</a>)</p>
 
 
@@ -172,7 +173,7 @@ This section should lists any major frameworks/libraries used to for this projec
 <!-- GETTING STARTED -->
 ## Getting Started
 
-There are no pre-requisites for using ChronlyHMS if you're not compiling/ packaging you javascript.  If you are packaging:
+There are no pre-requisites for using input-duration if you're not compiling/ packaging you javascript.  If you are packaging:
 
 ### Prerequisites
 
@@ -183,9 +184,6 @@ This is an example of how to get started with npm and webpack, other frameworks
   npm init -y
   npm install webpack webpack-cli --save-dev
   ```
-  * Webpack requires configuration for packaging ChronlyHMS CSS
-  see [Webpack CSS Loader](https://webpack.js.org/loaders/css-loader/)
-  
 
 ### Installation
 
@@ -194,19 +192,25 @@ _This template doesn't rely on any external dependencies or services._
 
 1. Install from NPM
  ```sh
-  npm i chronlyhms
+  npm i input-duration
  ```
-2. import ChronlyHMS javascript and css
+2. import input-duration in javascript
  ```sh
- import ChronlyHMS from 'chronlyhms';
- import 'chronlyhms/src/chrono.css'
+
+ import id from 'input-duration';
+
 ```
   
 Without packaging:
 
 1. Add script:
  ```sh
- <script src="https://cdn.jsdelivr.net/npm/chronlyhms@1.0.65/dist/chronoBundle.min.js"></script>
+
+<script type="module">
+
+import chronlyhms from 'https://cdn.jsdelivr.net/npm/input-duration/+esm'
+        
+ </script>
   
  ```
 
@@ -218,25 +222,31 @@ Without packaging:
 <!-- USAGE EXAMPLES -->
 ## Usage
 
-ChronlyHMS requires an input element with the attribute 'data-univHMS'.  There's no more code than that needed.  
+input-duration requires a <input-duration> element .  There's no more HTML than that.  
 ```sh
-<input id='bob' data-univHMS></input>
+
+<input-duration id='bob'></input-duration>
+
 ```
 
-If you would like ChronlyHMS to update inputs that are placed on DOM with javascipt (ex. after chronlyhms script is added), then with your js: 
-1) add a data attribute to the input 
+If you would like to get or set values or to disable input-duration elemet, javascipt can do that: 
+
 ```sh
-data-univHMS [data-univHMS='']
+
+document.querySelector('#bob').value = '44:04:04.444'
+
 ``` 
 
-2) call the Chronly boot method
+and
 
 ```sh
-window.ChronlyHMS.boot()
+
+document.querySelector('#bob').disable()
+
 ```
 so the inputs are modified.
 
-_For more documentation, please refer to the jscocs on  [ChronlyHMS Docs](https://stephanluis.github.io/chronlyhms/)_
+_For more documentation, please refer to the jscocs on  [input-duration Docs](https://stephanluis.github.io/input-duration/)_
 
 <p align="right">(<a href="#top">back to top</a>)</p>
 
@@ -254,7 +264,7 @@ _For more documentation, please refer to the jscocs on  [ChronlyHMS Docs](https:
 - [ ] Multi-language documentation (Google translate of this page?)
     - [ ] Chinese
     - [ ] Spanish
-- [ ] Is it worth having a remove function, restoring the original input?
+- [ ] min and max values (sorry for the moment you'll have to do those yourself in js)
 
 See the [open issues](https://github.com/StephanLuis/chronlyhms/issues) for a full list of proposed features (and known issues).