Skip to content

I'm Glad UtilitiesBeep is all but over. I don't want to look underneith that hood again! #7

Description

@ikyman

43d21f0

GoLang is a very clean language. UtilitiesBeep, however, is not.

The Names for the "Musical Sheet Music" and "Musical Sheet-Music+ accompanying beep Buffer" are "SheetNote" and "MusicPage", under "SheetNote" and "MusicPage", respectively.

At the time, I thought MusicPage could stand as Shorthand for Music + Page. However, I frequently mis-read it as "A Subsection (AKA a page) of a Large SheetNote". Oops!

I used "MusicPage" because I ran out of Music & Sheet-Score related terms. Could it be that this "MusicPage" object is entirely unnecessary? Golang Allows for functions to have more than one return value. Furthermore, any operations on the MusicPage's SheetMusic will be independent of any operations on the SongSegment. Heck, in order to feed both into the mCraftnBlockmLearning struct, I'd have to seperate the two anyhoo!

Having the two "Load from folder" functions (LoadTrainingOGGFolder & LoadSheetNoteFromCSV) in two seperate .gos is awkward, too.

Note that I'll still have to expose some Lower-level aspects from UtilitiesBeep. gio200slices wouldn't work without utilitiesBeep.SongSegment, after all!

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions