Home Page & Tutorial Refactoring

CMakeLists.txt

@@ -75,13 +75,18 @@ target_sources(${PROJECT_NAME}
         src/Model.h
 
         src/windows/AboutWindow.h
-        src/windows/WelcomeWindow.h
+        src/windows/CustomPathWindow.h
+
+        src/windows/tutorial/TutorialTargets.h
+        src/windows/tutorial/TutorialOverlay.h
+        src/windows/tutorial/TutorialWindow.h
+
         src/windows/settings/SettingsWindow.h
         src/windows/settings/GeneralSettingsTab.cpp
         src/windows/settings/LoginTab.cpp
 
-        src/widgets/ModelSelectionWidget.h
         src/widgets/ModelInfoWidget.h
+        src/widgets/ModelStyle.h
         src/widgets/ControlAreaWidget.h
         src/widgets/TrackAreaWidget.h
         src/widgets/StatusAreaWidget.h
@@ -118,7 +123,8 @@ target_sources(${PROJECT_NAME}
         src/utils/Messages.h
         src/utils/Settings.h
         src/utils/Interface.h
-        src/utils/ModelRegistry.h
+        src/utils/ModelCatalog.h
+        src/utils/ModelTags.h
         src/utils/Controls.h
         src/utils/Labels.h
         src/utils/Clients.h
@@ -185,6 +191,14 @@ juce_add_binary_data(stability_controls
         ${CMAKE_SOURCE_DIR}/src/clients/providers/stability/models/audio-to-audio.json
 )
 
+# The model taxonomy is defined once, in pyharp, where models declare their tags
+juce_add_binary_data(model_taxonomy
+    HEADER_NAME TaxonomyData.h
+    NAMESPACE TaxonomyData
+    SOURCES
+        ${CMAKE_SOURCE_DIR}/pyharp/pyharp/taxonomy.json
+)
+
 # `target_link_libraries` links libraries and JUCE modules to other libraries or executables. Here,
 # we're linking our executable target to the `juce::juce_gui_extra` module. Inter-module
 # dependencies are resolved automatically, so `juce_core`, `juce_events` and so on will also be
@@ -206,6 +220,7 @@ target_link_libraries(${PROJECT_NAME}
         juce::juce_gui_basics
         juce::juce_gui_extra
         stability_controls
+        model_taxonomy
     PUBLIC
         juce::juce_recommended_config_flags
         juce::juce_recommended_lto_flags

README.md

@@ -77,8 +77,8 @@ HARP supports a simple workflow: pick an existing model for processing or provid
 To get started:
 
 - Open HARP as a standalone application or within your DAW
-- Select an existing model using the drop-down menu at the top of the screen, or select `custom path...` and provide a URL to any HARP-compatible Gradio endpoint 
-- Load the selected model (and its corresponding interface) using the `Load` button.
+- Browse or search the models on the `Home` tab, which lists every model hosted by [TEAMuP on Hugging Face](https://huggingface.co/teamup-tech) by category, or click `Custom Path...` and provide a URL to any HARP-compatible Gradio endpoint
+- Click a model to open it (and its corresponding interface) in a tab of its own. Several models can be open at once, each in its own tab.
 - Import audio or MIDI data to process with the model either via the `Open File` button or by dragging and dropping a file into HARP
 - Adjust controls to taste in the interface
 - Click `Process` to run the model; outputs will automatically be rendered in HARP

src/Application.cpp

@@ -286,7 +286,7 @@ bool MainComponent::perform(const InvocationInfo& info)
 
         case CommandIDs::tutorial:
             DBG_AND_LOG("MainComponent::perform: \"tutorial\" command invoked.");
-            openWelcomeWindow();
+            openTutorial();
 
             break;