depot - monorepo for the virus lounge

Age	Commit message (Collapse)	Author	Files	Lines
2020-04-19	Correct all G_sharp pitch classes	William Carroll	1	-7/+7
	I incorrectly modelled all of the G-sharps in my application as belonging to the G pitchClass, which resulted in a strange bug where vieChord printed "G minor Root position", but the Piano highlit a G minor. I checked the other accidentals, and it looks like everything is properly classified.
2020-04-19	Remove unused Msg's	William Carroll	1	-48/+0
	I'm sure this app contains more unused code. I would like to find some Elm tools for detecting and deleting dead code, but this isn't my current priority. My current priority is dogfooding this app until I find it genuinely useful for myself.
2020-04-19	Ensure only whitelisted chord inversions present in initial state	William Carroll	1	-2/+6
	Whoops...
2020-04-19	Display "Get ready..." message before practicing	William Carroll	1	-6/+13
	This is a temporary solution. Ideally I would like to handle this with the following: - Show the flashcard for a chord shortly after beginning a practice session - Display a small 3...2...1... countdown timer immediately after beginning a practice session I need to dig more deeply into Elm's Time module and subscriptions to better understand how to properly solve this problem. In the meantime, please tolerate this short-term solution.
2020-04-19	Restore support for whitelisted chord inversions	William Carroll	2	-44/+34
	Allow users to include or exclude chord inversions.
2020-04-19	Drop support for PracticeMode	William Carroll	2	-43/+3
	For now, I'd like to support selecting keys and whitelisting inversions.
2020-04-19	Support a FlashCard before showing the notes that comprise a chord	William Carroll	5	-5/+66
	My much anticipated feature: first prompt the user for a name of a chord, then show the user that chord. Cascading changes: I changed the "Tap to practice" overlayButton's opacity from 30% to 100% because pausing when showFlashCard is True causes the two piece TIL: You can batch Elm Subscriptions using the Sub.batch function. What I haven't learned yet: How to best handle rotating screens for mobile devices (i.e. portrait vs. landscape modes). In time... What's left? - Support sound - Support a fine-tune section of the preferences - Support tablet and web browser variants - Ask users for the "I chord" instead of asking "C major Root position" - More styling (of course)
2020-04-19	Create Tailwind module	William Carroll	5	-27/+49
	Moving the UI.tw function into Tailwind.use. Creating and consuming some functions like Tailwind.if_ and Tailwind.when to make it easier to conditionally style some of my components.
2020-04-19	Ensure the overlayButton is truly h-screen and w-screen	William Carroll	2	-112/+35
	Now the "Tap to practice" button fully covers the screen. - Dropped support for a Piano direction (for now) - Using w-full and w-1/2 for piano key "length"
2020-04-19	Responsively size UI	William Carroll	5	-12/+84
	TL;DR: scale down UI for non-mobile devices. I pulled the screen resolution for my phone, the Google Pixel 4, off of the internet. I created a device profile in Chrome to develop this application specifically for my phone. To my surprise, when I opened the app on my phone, many of elements that looked good in Google Chrome, looked askew on my phone. I needed to troubleshoot. Here's how I did that: I used Tailwind to responsively color the bg for each breakpoint to see if my device was sm, md, lg, xl (according to Tailwind's breakpoint terminology). After reading Tailwind's documentation and comparing their breakpoints with my Pixel 4's width (i.e. 1080px), I figured that my device would be lg. It's not; it's md, which I confirmed by using ngrok to load localhost:8000 on my phone and see that the background-color was "md:bg-green-600". I'm still unsure why my device is not lg, but knowing that my device was md was enough to fix many of the styling issues. My current theory is that while my screen's resolution is 1080 wide, the pixel density affects the media query for the breakpoint.
2020-04-19	Set the selectedChord to Nothing when setting a key	William Carroll	1	-0/+1
	This helps us avoid showing a chord from a key that the user did not whitelist.
2020-04-19	Prune {Select,Deselect}AllKeys actions	William Carroll	1	-19/+0
	Removing more unused code attempting to focus this app's scope.
2020-04-19	Highlight root note of each chord	William Carroll	2	-37/+70
	Refactor the Piano component to highlight the root note of each chord. If this makes things too easy, I can support this as a preference. Also: - Reduced the number of keys that the piano displays and increased the key thickness to reclaim the space - Preferred using Tailwind selectors instead of inline styling where applicable - Call List.reverse on the keys to ensure that the top-most note is a lower note than the bottom-most note TODO: - Support showing only the name of the chord and not just the notes that comprise that chord - Rewrite the function that generates the chords for a given range of notes - Consider supporting a dark mode
2020-04-18	Remove horizontal padding	William Carroll	1	-2/+2
	Google Chrome's device preview doesn't resemble what I see when I use my phone to visit this page.
2020-04-18	Create Overview for Learn Piano Chords	William Carroll	2	-2/+94
	Since I've published this, I should include an Overview page to orient potential users. This Overview could be better -- as could many things with this app -- but it's a start, and I'm seeking small wins.
2020-04-18	Remove duplicate step from README	William Carroll	1	-2/+1
	I mention setting tempo twice... whoops.
2020-04-18	Prefer "Tap" to "Press"	William Carroll	1	-1/+1
	I'm preferring the verb "tap" to "press".
2020-04-18	Debug unresponsive button press for selectKey	William Carroll	1	-2/+2
	Observed problem: Tapping "C major, A minor" key, which LPC sets by default, does not unset it. Bug: handleClick passed the relativeMinor Key but the default value in State.Model is the C Major key. We would toggled b/w [Cmajor] -> [Cmajor,Aminor], and because toggled checked if either Cmajor or Aminor was present, it was always true. Solution: Check relativeMajor to set toggled.
2020-04-18	Tidy app	William Carroll	7	-538/+498
	Now that I have a deployed an MVP of my app, I am tidying things up to support the next phase of development. TL;DR: - Moved application Model-related code into State module - Moved each View into its own module - Deleted unused ChordInspector component - Deleted unused Msg's, {Increase,Decrease}Tempo - Deleted misc unused code
2020-04-18	Ignore Main.min.js	William Carroll	1	-1/+1
	The elm2nix expression builds my code as Main.min.js. As such, I changed my index.html to require Main.min.js instead of elm.js. When I run elm-live now, I make sure that I output Main.min.js as well. I need to gitignore this to exclude it from my repository though.
2020-04-18	Orient "Press to practice" button	William Carroll	2	-22/+58
	Rotate the "Press to practice" copy to ensure that it is readable in landscape mode.
2020-04-18	"Chord Drill Sergeant" -> "Learn Piano Chords"	William Carroll	19	-14/+15
	In the spirit of "keep it simple, stupid", I am naming this application as closely to the functionality as I can imagine.
2020-04-18	Use elm2nix to (attempt to) deploy learnpianochords.app	William Carroll	4	-18/+121
	After a few failed attempts at deploying my Elm application on NixOS, I'm trying elm2nix, which some NixOS and Elm users created to attempt to solve some of the issues that I ran into earlier today. Elm tries to write to $HOME, which NixOS doesn't like. I typically prefer to avoid things like cabal2nix, elm2nix, node2nix because I don't like the workflow that they suggest, but I'm so eager to deploy this application, that I'm trying it.
2020-04-17	Nixify build for Chord Drill Sergeant	William Carroll	2	-1/+25
	Thankfully @tazjin builds Gemma (an Elm project) with Nix, so I could reference Gemma's default.nix to help me with mine. Elm problematically attempts to HTTP-fetch a list of packages to verify my project's dependencies. Because Nix builds derivations in a sandbox without network access, I need to use some escape hatches (i.e. NIX_REDIRECTS, LD_PRELOAD, SYSTEM_CERTIFICATE_PATH). Welp... it's packaged now... I'm also pointing learnpianochords.app to this project's index.html. It will be live soon! :) TODO(wpcarro): Rename "Chord Drill Sergeant" -> "Learn Piano Chords" (KISS)
2020-04-17	Simplify preferences	William Carroll	1	-32/+40
	I'd like to deploy an MVP version of this application today, so I'm dropping support for a few features to focus my efforts. I may bring these features back. TL;DR: - Temporarily drop support for "Fine Tune" tab of preferences - Sort keys by the Circle of Fifths
2020-04-17	Render a mobile-friendly piano	William Carroll	5	-116/+236
	For now since I'm the only customer and I'm primarily making this for myself, I'm styling the app specifically for my Google Pixel 4. If I find this app useful, I will consider supporting other devices. I'm using the Icons that I bought when I purchased the "Refactoring UI" book. Other news: - I bought the domain learnpianochords.app! What's left: - Style the "fine tune" tab of the preferences view - Better support non-mobile devices like the browser and tablet devices - Deploy the application to learnpianochords.app - Redesign the "key" tab of the preferences view to sort the keys according to the circle of fifths - Dogfood - Simplify until I cannot simplify anymore
2020-04-13	Begin styling efforts	William Carroll	8	-126/+264
	Start styling the Chord Drill Sergeant for mobile devices because that is that device on which I will primarily use CDS. I'm also deleting the debugger related code. I would like to support a debugger, but I'm not currently using this one, so I am going to remove it to keep things slender. - Introduce TailwindCSS, which also introduced elm-live, index.html, index.css - Add mobile-first styling for the preferences modal - Remove unused code
2020-04-13	Support generating chords for a particular key	William Carroll	4	-285/+283
	Generate chords for a given key. I believe my Theory.allChords function is taking a long time to generate all of the chord possibilities. I would like to profile this to verify this assumption. I think I can create a "staging area" for changes and only regenerate chords when "committing" the options from the "staging area". This should stress the application less. TODO: Profile application to find bottleneck.
2020-04-13	Don't render the notes on the piano	William Carroll	1	-1/+1
	I was using this to debug a feature that I no longer need to debug.
2020-04-13	Rename NoteClass -> PitchClass	William Carroll	2	-148/+151
	For the past two to three days, I've been searching for the name for the concept of "C" or "A". From what I read, notes are specific things like C0 or C4, but I wanted the name of the concept of a C. Thankfully today I discovered that this is called a pitch class.
2020-04-13	Remodel model.selectedChord as Maybe Chord	William Carroll	1	-50/+65
	Until the user presses play, we shouldn't display any chords.
2020-04-12	Whitelist and blacklist note classes	William Carroll	1	-7/+64
	Often I want to practice only C, F, and G-chords in all inversions. Next I'd like to only support the chords for various keys.
2020-04-12	Only display chords that fit on the displayed piano	William Carroll	1	-278/+293
	Only show the chords that we can fit on the piano. TODO: Debug occasional instance where we render chords that do not fit. I am unsure how to reproduce these states at the moment.
2020-04-12	Support suspended chords	William Carroll	1	-0/+30
	I'm not sure how valuable it is to study all of the inversions of the suspended chords. Maybe it is. I'll let the users decide.
2020-04-12	Whitelist and blacklist chordTypes	William Carroll	2	-105/+112
	Allow and disallow chords by the type of chords.
2020-04-12	Whitelist and blacklist chords by inversion type	William Carroll	2	-10/+84
	Add checkboxes to support various chord positions.
2020-04-12	Properly support chord inversions	William Carroll	9	-516/+1547
	While I did change a lot of functionality, I also ran `elm-format` across the codebase, which makes these changes a bit noisy. Here is the TL;DR: - Properly support chord inversions - Ensure that the piano styling changes dynamically when I change the variables like `naturalWidth` - Add start and end notes to define the size of the piano and which chords we create - Support elm-format and run it across entire project - Debug Misc.comesBefore - Introduce a ChordInspector and debugger TODO: Ensure that we only generate chords where all of the notes can be rendered on the displayed keys. TODO: Add preferences panel, so that I can do things like "Practice blues chords in C and E with chord substitutions."
2020-04-11	Support NoteClass	William Carroll	3	-124/+283
	Remodel application to support the scientific pitch notation for notes. Instead of supporting simply "C", support "C4". This change created cascading changes. After refactoring for around an hour, I restored the app to a working state. The current state is not desirable, but it compiles. More changes on the way.
2020-04-11	Support Misc module	William Carroll	1	-0/+15
	Define two functions for attempting to return an element in a list that precedes or succeeds another element. I prefer having something like Utils.List. Perhaps I will refactor.
2020-04-11	Support BPM for tempo	William Carroll	2	-10/+50
	Using BPM as the unit for tempo. TODO: Consider a higher-fidelity way to calculate BPM, although I'm not sure this is critical functionality; an interesting problem is just seducing me, and this app would be better off resisting the temptation.
2020-04-11	Track app ideas	William Carroll	1	-0/+3
	Use an org file to track random ideas or features or improvements.
2020-04-11	Prefer type alias to type	William Carroll	2	-60/+48
	Elm reminds me of Haskell. In fact, I'm using `haskell-mode` (for now) in Emacs to write my Elm code, and it works reliably. I'm not writing a Haskell app, but if I were, I would define my application Model with the following Haskell code: ```haskell data Model = Model { whitelistedChords :: [Theory.Chord] , selectedChord :: Theory.Chord , isPaused :: Bool , tempo :: Int } ``` When I first modelled my application state, I did something similar. After reading more Elm examples of SPAs, I see that people prefer using type aliases to define records. As far as I know, you cannot do this in Haskell; I believe all types are "tagged" (something about "nominal typing" comes to mind). Anyhow, Elm isn't Haskell; Haskell has cool features like type classes; Elm has cool features like human-readable error messages and exhaustiveness checking for cases. I love Haskell, and I love Elm, and you didn't ask. Anyhow, this commit refactors my records as type aliases instead of types. I think the resulting code is more readable and ergonomic.
2020-04-11	Support basic tempo	William Carroll	2	-13/+75
	Supporting Play/Pause events, and Increase/Decrease tempo. TODO: Convert milliseconds to BPM
2020-04-11	Improve the styling of the piano	William Carroll	2	-29/+58
	Create a more convincing representation of the piano. I would like to compute the left-offset based on the naturalWidth. That change is probably forthcoming.
2020-04-11	Generate all known chords and display randomly selected chords	William Carroll	4	-216/+345
	First of all, Elm's purity is beautiful. I think every language should model their error messages and develop experience after Elm. If I didn't have to download packages, I don't think I would need an internet connection to troubleshoot my program's errors. This is how helpful I find the compiler. Now that that's out of the way, here's what I've changed since we've last corresponded: - Use Elm's Browser.element to create a reactive application with state - Write a function to generate all of the chords about which CDS knows - Move some code out of Main.elm into other modules - Depend on List.Extra, Random, Random.Extra What's left: - Lots of work - Instead of clicking a button to show a new chord, use a timer - Add mobile-first styling (probably add TailwindCSS) - Persist settings in LocalStorage (and then eventually create user accounts) - Allow users to curate the list of chords they're interested in practicing - Deploy the website and dogfood it Unknowns: - How can I handle tempo? I don't expect setInterval to be enough (maybe it is)...
2020-04-10	Model data and sketch ideas for Chord Drill Sergeant	William Carroll	6	-0/+294
	Initialize an Elm application to build a MVP for the Chord Drill Sergeant application. There isn't much to see at the moment. I'm just sketching ideas. More forthcoming...
2020-04-10	Create README for Chord Drill Sergeant	William Carroll	1	-0/+47
	See the README for more information. I've wanted to use an application like this for awhile. I would like to start developing this soon.
2020-04-10	Add README for typo-po	William Carroll	1	-0/+10
	See the README for more context on typo-po. I drank a strong cup of coffee this morning, and I cannot quiet the activity in my head. I'm attempting to use READMEs in my //website/sandbox to track ideas that I would typically track using my phone's notes application. Creating a README forces me to write more than I may have written in my phone's notes. Also, since this repository is available at https://git.wpcarro.dev, I can share these ideas with friends by sending them a URL! So much for "stealth mode"... Well I guess this stress-tests my theory that ideas are less important than execution.
2020-04-10	Create README for Github Issues Service	William Carroll	1	-0/+28
	See the README for an overview of the concept. Basically I would like a simpler way to collect feature requests and bug reportss from my web apps.
2020-03-27	Run Prettier across projects	William Carroll	8	-28/+25
	Problem: Prettier was not running when I saved Emacs buffers. Why? - prettier-js-mode needs needs node; lorri exposes node to direnv; direnv exposes node to Emacs; lorri was not working as expected. Solution: Now that I'm using nix-buffer, I can properly expose node (and other dependencies) to my Emacs buffers. Now Prettier is working. Commentary: Since prettier hadn't worked for so long, I stopped thinking about it. As such, I did not include it as a dependency in boilerplate/typescript. I added it now. I retroactively ran prettier across a few of my frontend projects to unify the code styling. I may need to run... ```shell $ cd ~/briefcase $ nix-shell $ npx prettier --list-different "*/.{js,ts,jsx,tsx,html,css,json}" ``` ...to see which files I should have formatted.