greyscaled / bpm Goto Github PK

Description & Context

While immutable patterns are often desirable, I find myself wanting to access the BPM methods without having to construct a new object

@updownupdown Make mobile responsive down to about 380px.

Will need a base config that's extended with react stuff for the react pkg. Likely something along these lines:

{
  "root": true, // in root dir
  "parser": "@typescript-eslint/parser",
  "plugins": ["@typescript-eslint"],
  "extends": [
    "eslint:recommended",
    "plugin:@typescript-eslint/eslint-recommended",
    "plugin:@typescript-eslint/recommended",
    "plugin:import/errors",
    "plugin:import/typescript",
    "plugin:react/recommended", // react-app only
    "plugin:react-hooks/recommended", // react-app only
    "plugin:jsx-a11y/recommended" // react-app only
  ],
  "env": {
    "browser": true, // react-app only
    "node": true // lib only
  },
  "rules": {
    "@typescript-eslint/explicit-function-return-type": "off",
    "@typescript-eslint/no-unused-vars": "error",
    "@typescript-eslint/no-use-before-define": "off",
    "import/prefer-default-export": "off",
    "import/no-default-export": ["error"]
  }
}

lib/ should probably just be

{
  "extends": "../.elintrc",
  "env": {
    "node": true
  }
}

Tasks

• fb open graph tags
• twitter tags
• general meta description/author tags
• seo tags etc

1. don't show a colour when the clicktrack is not playing
2. the shades of blue are hard to distinguish on some lower-resolution mobile devices

• branch protections
• community & contributing
• license
• repository description and tags
• wiki information

Can be used in (but not limited to):

• favicon
• OG/meta tags etc (create sep issue)
• README(s) (create sep issue and use a screenshot or gif)
• repository image/icon (create sep issue)

Description & Context

Right now, the deploy script runs on each change to master. While this is convenient, it means the deployed app is usually out of sync with the latest release.

Eventually, the latest release tag should be added to the frontend and it should be synchronized with actual releases.

Add a screenshot or GIF

Having to click the decrease/increase buttons more than a handful of times is a poor UX. Instead, the buttons should be able to continuously update the BPM while they are in the pressed state.

On lower-end mobile devices, synth sounds sometimes "pop", likely due to performance implications

Would be nice to have confs/scripts that do the following:

• changes since latest tag for a particular pkg
• commits since latest tag for a particular pkg

ex:

git diff HEAD <some react-app tag> react-app/

git log --pretty=format:"* %s (%h)" <latest react-app tag>...HEAD react-app/

Description & Context

It's often desirable to analyze an existing piece of music for it's BPM. We could allow an 'analysis' mode that:

• requires the metronome to be off
• analyzes an audio file
• if a BPM can be determined, the beat's calculator displays its metrics
  • otherwise, displays a human-friendly message that the BPM was unable to be determined

Description & Context

Add version in application (likely in <header>)

I was looking over sheet music and wanted to use the BPM app (the song is tricky to keep track of, very fast arpeggios), but the sound is super loud even when I have Spotify on max, making is impossible to use. I'd add a slider at the bottom to control volume, defaults to 65% or something like that so it doesn't look like it's fully centered and a decorative element.

Description & Context

Alternatives

Tags

• @vapurrmaid/bpm@
• @vapurrmaid/bpm-react-app@

Tasks

• replace old tags with new ones
• update GH releases
• update release/automation scripts

• refactor module into class
• improve callback functionality
  • add an interface and give more context/info to the callback fns
• fix how the internal metronome modulus works - 2 successive "even" numbers (1-2-3-4-0) 4 and 0

Description & Context

BPM should be able to handle 1 decimal place