fli_video 0.1.0 → 0.1.2

data/docs/generated/features-and-components.md

@@ -3,13 +3,16 @@
 ### Feature <-> DSL GPTs
 https://chat.openai.com/g/g-AyFi0UOXn-code-simplifier
 
-**Read Global Configuration**
+**Global Configuration**
 Access and apply global configuration settings for video asset management and state consistency.
 
 **Project Configuration**
-Access and apply video or episode settings and state.
+Access and apply video or episode settings and state. Infers project settings from existing project folders and files.
 
-**FileWatch Processor for File Event Commands**
+**CLI Project Commands**
+Efficiently execute and manage video project commands using a command-line interface, enhancing control and flexibility in project handling.
+
+**FileWatch Processor**
 Utilize a FileWatch processor to automate file event responses, directing new recordings to designated folders for efficient content management.
 
 **Create Project**
@@ -64,9 +67,6 @@ Build a JSON datastore of files for an entire project based on existing project,
 
 ## Future Ideas
 
-**CLI Project Management Interface**
-Efficiently execute and manage video project commands using a command-line interface, enhancing control and flexibility in project handling.
-
 **Web Command Interface for Video Project Management**
 Introduce a streamlined, web-based interface for managing video project commands, enabling efficient control and organization of project components through simple browser interactions.
 
@@ -75,15 +75,15 @@ Generate a detailed report for a specific video project, including the episodes,
 This should be extracted to an AstroJS Website or HTML template servered by a local webserver and provide viewing and navigation for all my video projects.
 
 
-## Klue Components
 
+## Klue Components
 Klue Component: `add_episode.klue`
 
 ```ruby
 component :add_episode do
   desc "Add a new episode to an existing podcast project."
 
-  pattern "Interactor"
+  pattern "Command"
 
   comments <<~TEXT
     - Facilitates the addition of a new episode to a specific podcast project.
@@ -105,8 +105,8 @@ component :add_episode do
     # ~/video-projects/a21-ac-some-podcast/01-episode-about-something/.trash
   RUBY
 end
-```
 
+```
 Klue Component: `change_chapter_name.klue`
 
 ```ruby
@@ -142,8 +142,8 @@ component :change_chapter_name do
     # 01-d-intro-CTA.mov
   RUBY
 end
-```
 
+```
 Klue Component: `create_chapter_video.klue`
 
 ```ruby
@@ -181,15 +181,15 @@ component :create_chapter_video do
     # Output: '~/video-projects/a27-ac-some-podcast/chapters/01-intro-custom.mov'
   RUBY
 end
-```
 
+```
 Klue Component: `create_project.klue`
 
 ```ruby
 component :create_project do
   desc "Setup a new video project for standalone YouTube video or Podcast."
 
-  pattern "Interactor"
+  pattern "Command"
 
   comments <<~TEXT
     - Allows the creation of a new project, specifying if it's for a YouTube video or a Podcast.
@@ -223,8 +223,8 @@ component :create_project do
     # ~/video-projects/a21-ac-some-podcast/.fv.json
     RUBY
 end
-```
 
+```
 Klue Component: `empty_trash.klue`
 
 ```ruby
@@ -252,8 +252,8 @@ component :empty_trash do
     # Empties the entire .trash folder in "~/video-projects/a27-ac-categorize-mp4-CI/.trash/
   RUBY
 end
-```
 
+```
 Klue Component: `episode_path.klue`
 
 ```ruby
@@ -334,8 +334,8 @@ component :episode_path do
     episode_path.keywords # => ["TODO"]
   RUBY
 end
-```
 
+```
 Klue Component: `global_config.klue`
 
 ```ruby
@@ -370,8 +370,8 @@ component :global_configuation do
   method :load
   method :save
 end
-```
 
+```
 Klue Component: `move_ecamm_file.klue`
 
 ```ruby
@@ -396,8 +396,8 @@ component :move_ecamm_file do
     # ~/video-projects/a20-ad-some-video/recordings/Ecamm Live Recording on 2023-08-25 at 14.51.58.mov
   RUBY
 end
-```
 
+```
 Klue Component: `move_to_trash.klue`
 
 ```ruby
@@ -414,9 +414,9 @@ component :move_to_trash do
 
   constructure(:parent_project)
 
-  method :run(:file_name)
+  method :run(:file_name = nil)
 
-  sample :move_video_to_trash, <<~RUBY
+  sample :move_named_video_to_trash, <<~RUBY
     project_path = ProjectPath.new('a27')
 
     command = move_to_trash.new(project_path)
@@ -424,14 +424,20 @@ component :move_to_trash do
     # Example of moving a specific suboptimal video take to the trash folder
     command.run('01-a-introduction.mov')
     # => "~/video-projects/a27-ac-categorize-mp4-CI/.trash/01-a-introduction.mov"
+  RUBY
+
+  sample :move_last_ecamm__video_to_trash, <<~RUBY
+    project_path = ProjectPath.new('a27')
 
+    command = move_to_trash.new(project_path)
+  
     # Example of moving the last suboptimal video take to the trash folder
     command.run
     # => "~/video-projects/a27-ac-categorize-mp4-CI/.trash/Ecamm Live Recording on 2023-08-25 at 14.51.58.mov
   RUBY
 end
-```
 
+```
 Klue Component: `open_in_finder.klue`
 
 ```ruby
@@ -460,8 +466,8 @@ component :open_in_finder do
     # Opens the folder for episode '01' of project 'a27' in Finder
   RUBY
 end
-```
 
+```
 Klue Component: `project_config.klue`
 
 ```ruby
@@ -588,8 +594,8 @@ component :project_configuration do
   }
   JSON
 end
-```
 
+```
 Klue Component: `project_meta_data_store.klue`
 
 ```ruby
@@ -621,8 +627,8 @@ component :project_meta_data_store do
     # Output: '~/video-projects/a27-ac-categorize-mp4-CI/project_metadata.json'
     RUBY
 end
-```
 
+```
 Klue Component: `project_path.klue`
 
 ```ruby
@@ -703,8 +709,8 @@ component :project_path do
     project_path.keywords # => "CI"
   RUBY
 end
-```
 
+```
 Klue Component: `recording_file_watcher.klue`
 
 ```ruby
@@ -736,8 +742,8 @@ component :filewatch_processor do
     filewatch_processor.move_file
   RUBY
 end
-```
 
+```
 Klue Component: `recording_filename.klue`
 
 ```ruby
@@ -853,8 +859,8 @@ component :recording_filename do
     filename.filename # => "01-a-introduction-NEW_TAG.mov"
   RUBY
 end
-```
 
+```
 Klue Component: `restore_from_trash.klue`
 
 ```ruby
@@ -887,8 +893,8 @@ component :restore_from_trash do
     # => "~/video-projects/a27-ac-categorize-mp4-CI/Ecamm Live Recording on 2023-08-25 at 14.51.58.mov"
   RUBY
 end
-```
 
+```
 Klue Component: `switch_focus.klue`
 
 ```ruby
@@ -916,8 +922,8 @@ component :change_focus do
     change_focus.run('a21', '02')
   RUBY
 end
-```
 
+```
 Klue Component: `text_to_speech.klue`
 
 ```ruby
@@ -950,8 +956,8 @@ component :text_to_speech do
     # Output: Transcriptions saved in '~/video-projects/a27-ac-categorize-mp4-CI/recordings/transcript/01-introduction.txt|srt|vtt|json|tsv'
   RUBY
 end
-```
 
+```
 Klue Component: `transcript_data_store.klue`
 
 ```ruby
@@ -983,5 +989,5 @@ component :transcript_data_store do
     # Output: '~/video-projects/a27-ac-categorize-mp4-CI/project_transcripts.json'
   RUBY
 end
-```
 
+```

data/docs/generated/technical-design-and-features.md

@@ -1,6 +1,20 @@
+# FliVideo
+
 ## Application Overview
 
-This document provides an overview of a specialized application designed primarily for video content creators using Ecamm Live on the Mac, and adaptable for OBS users. Tailored for projects ranging from individual YouTube videos to episodes in a podcast series, the application fits seamlessly into the workflow between video recording and editing. It streamlines the post-recording process, encompassing file organization, renaming, and assembly of video recordings, thereby enhancing the efficiency and structure of content creation.
+FliVideo is a Video Asset Managment tool created by a YouTuber `@AppyDave` for YouTubers.
+
+It provides a set of image, video and workflow management tools to help its creator 'AppyDave' to automate and systemetize the video production process.
+
+The intiial idea behind FliVideo was Zappier for YouTubers, but it is evolving with a range of capabilities around script, b-roll and presenation canvas automation.
+
+### Video Recording Managment
+
+FliVideo initially targeted video content creators using Ecamm Live on the Mac, and adaptable for OBS users.
+
+Tailored for projects ranging from individual YouTube videos to episodes in a podcast series, the application fits seamlessly into the workflow between video recording and editing. 
+
+It streamlines the post-recording process, encompassing file organization, renaming, and assembly of video recordings, thereby enhancing the efficiency and structure of content creation.
 
 ### Core Functionality
 
@@ -74,8 +88,8 @@ a29-ac-gpts-analyze-pdf-transations
 
 ### Sample project codes
 
-- `ac` - AppyCast
 - `ad` - AppyDave
+- `ac` - AppyDaveCoding
 - `fv` - FliVideo
 - `wp` - WinningPrompts
 - `c9` - Carnivore90
@@ -343,18 +357,23 @@ project-name/recordings/03-a-outro.mov
 project-name/recordings/03-b-outro-cta.mov
 project-name/recordings/03-c-outro.mov
 ```
+
+
 ## Features
 
 ### Feature <-> DSL GPTs
 https://chat.openai.com/g/g-AyFi0UOXn-code-simplifier
 
-**Read Global Configuration**
+**Global Configuration**
 Access and apply global configuration settings for video asset management and state consistency.
 
 **Project Configuration**
-Access and apply video or episode settings and state.
+Access and apply video or episode settings and state. Infers project settings from existing project folders and files.
+
+**CLI Project Commands**
+Efficiently execute and manage video project commands using a command-line interface, enhancing control and flexibility in project handling.
 
-**FileWatch Processor for File Event Commands**
+**FileWatch Processor**
 Utilize a FileWatch processor to automate file event responses, directing new recordings to designated folders for efficient content management.
 
 **Create Project**
@@ -409,12 +428,10 @@ Build a JSON datastore of files for an entire project based on existing project,
 
 ## Future Ideas
 
-**CLI Project Management Interface**
-Efficiently execute and manage video project commands using a command-line interface, enhancing control and flexibility in project handling.
-
 **Web Command Interface for Video Project Management**
 Introduce a streamlined, web-based interface for managing video project commands, enabling efficient control and organization of project components through simple browser interactions.
 
 **Project Meta Report**
 Generate a detailed report for a specific video project, including the episodes, chapters, recordings, a list of recording IDs (chapter sequence + part sequence), and the name for the next video recording, file sizes.
 This should be extracted to an AstroJS Website or HTML template servered by a local webserver and provide viewing and navigation for all my video projects.
+

data/docs/project-new.md

@@ -0,0 +1,184 @@
+# Requirements Document for Project Management Tool
+
+## 1. Overview
+This document outlines the requirements for a command-line tool and supporting backend system for creating, renaming, and managing projects across multiple business units. The tool uses sequential naming conventions and integrates with a web server API for centralized management. This system is designed for a single-user environment.
+
+## 2. Business Objectives
+- Automate project creation, renaming, and listing for multiple business units.
+- Maintain consistent naming conventions with sequential identifiers.
+- Enforce folder structures based on project types.
+- Separate business rules between local and server environments for scalability.
+
+## 3. Functional Requirements
+
+### 3.1 Command-Line Tool
+The tool provides the following commands:
+
+#### 3.1.1 Creating a New Project
+**Command:**
+```
+ad-project-new <business_unit> <project_type> "<project_name>"
+```
+**Example:**
+```
+ad-project-new appydave video "hello-world"
+```
+**Expected Outcome:**
+- Generates a new project folder.
+- Assigns a sequential identifier, e.g., `a05-hello-world`.
+- Logs the output:
+  ```yaml
+  Project created: a05-hello-world
+  ```
+
+#### 3.1.2 Renaming a Project
+**Command:**
+```
+ad-project-rename <business_unit> <project_type> <project_id> "<new_project_name>"
+```
+**Example:**
+```
+ad-project-rename appydave video a05 "rails8"
+```
+**Expected Outcome:**
+- Updates the project folder name to `a05-rails8`.
+- Logs the change:
+  ```yaml
+  Project renamed: a05-rails8
+  ```
+
+#### 3.1.3 Listing Projects
+**Command for all projects:**
+```
+ad-project-list <business_unit> <project_type>
+```
+**Command for last N projects:**
+```
+ad-project-list <business_unit> <project_type> -l <number>
+```
+**Examples:**
+
+**All Projects:**
+```
+ad-project-list appydave video
+```
+**Output:**
+```css
+a01-intro-video
+a02-tutorial
+a03-promo-video
+```
+
+**Last 3 Projects:**
+```
+ad-project-list appydave video -l 3
+```
+**Output:**
+```css
+a03-promo-video
+a02-tutorial
+a01-intro-video
+```
+
+## 4. Non-Functional Requirements
+- Must work as a single-user tool on the local environment.
+- The command-line tool will interact with the backend via RESTful APIs to ensure database consistency.
+
+## 5. Entities and Database Design
+
+### 5.1 Entities
+- **Business Unit**: Represents channels like "AppyDave" or "AITLDR".
+- **Project Type**: Defines types like "Video" or "Article".
+- **Project**: Tracks individual projects, including name and sequential identifier.
+- **Folder Structure**: Stores default folders for each project type.
+
+### 5.2 Entity Relationship Diagram (ERD)
+**ERD Diagram Description:**
+- **Business Unit** links to **Project** (one-to-many relationship).
+- **Project Type** links to **Folder Structure** (one-to-one relationship).
+- **Project** has attributes like ID, Name, and Type.
+
+(An actual diagram would be helpful here; I can generate one if needed.)
+
+## 6. System Architecture
+
+### 6.1 Web Server
+- Maintains the central database.
+- Provides RESTful APIs:
+  - `POST /projects`: Create a new project.
+  - `PUT /projects/:id`: Rename a project.
+  - `GET /projects`: List projects.
+
+### 6.2 Command-Line Tool
+- Acts as a local interface to execute commands.
+- Interacts with the web server for updates and fetching data.
+
+## 7. Example API Interactions
+
+### 7.1 Create a New Project
+**Request:**
+```
+POST /projects
+Content-Type: application/json
+
+{
+  "business_unit": "appydave",
+  "project_type": "video",
+  "project_name": "hello-world"
+}
+```
+**Response:**
+```json
+{
+  "status": "success",
+  "project_id": "a05",
+  "project_name": "a05-hello-world"
+}
+```
+
+### 7.2 Rename a Project
+**Request:**
+```
+PUT /projects/a05
+Content-Type: application/json
+
+{
+  "new_name": "rails8"
+}
+```
+**Response:**
+```json
+{
+  "status": "success",
+  "project_name": "a05-rails8"
+}
+```
+
+### 7.3 List Projects
+**Request:**
+```
+GET /projects?business_unit=appydave&project_type=video&limit=3
+```
+**Response:**
+```json
+[
+  {
+    "id": "a03",
+    "name": "promo-video"
+  },
+  {
+    "id": "a02",
+    "name": "tutorial"
+  },
+  {
+    "id": "a01",
+    "name": "intro-video"
+  }
+]
+```
+
+## 8. Corrections and Finalized Decisions
+- Sequential identifiers are three letters followed by a number (e.g., `a05`), followed by the project name.
+- Output logs should always include the project identifier for user reference.
+- Simplified to focus on a single-user environment.
+

data/docs/technical-specifications.md

@@ -2,7 +2,19 @@
 
 ## Application Overview
 
-This document provides an overview of a specialized application designed primarily for video content creators using Ecamm Live on the Mac, and adaptable for OBS users. Tailored for projects ranging from individual YouTube videos to episodes in a podcast series, the application fits seamlessly into the workflow between video recording and editing. It streamlines the post-recording process, encompassing file organization, renaming, and assembly of video recordings, thereby enhancing the efficiency and structure of content creation.
+FliVideo is a Video Asset Managment tool created by a YouTuber `@AppyDave` for YouTubers.
+
+It provides a set of image, video and workflow management tools to help its creator 'AppyDave' to automate and systemetize the video production process.
+
+The intiial idea behind FliVideo was Zappier for YouTubers, but it is evolving with a range of capabilities around script, b-roll and presenation canvas automation.
+
+### Video Recording Managment
+
+FliVideo initially targeted video content creators using Ecamm Live on the Mac, and adaptable for OBS users.
+
+Tailored for projects ranging from individual YouTube videos to episodes in a podcast series, the application fits seamlessly into the workflow between video recording and editing. 
+
+It streamlines the post-recording process, encompassing file organization, renaming, and assembly of video recordings, thereby enhancing the efficiency and structure of content creation.
 
 ### Core Functionality
 
@@ -345,3 +357,4 @@ project-name/recordings/03-a-outro.mov
 project-name/recordings/03-b-outro-cta.mov
 project-name/recordings/03-c-outro.mov
 ```
+

data/lib/fli_video/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module FliVideo
-  VERSION = '0.1.0'
+  VERSION = '0.1.2'
 end

data/package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "fli_video",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "fli_video",
-      "version": "0.1.0",
+      "version": "0.1.2",
       "devDependencies": {
         "@klueless-js/semantic-release-rubygem": "github:klueless-js/semantic-release-rubygem",
         "@semantic-release/changelog": "^6.0.3",

data/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fli_video",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "description": "FliVideo - Video Asset Management for Content Creators",
   "scripts": {
     "release": "semantic-release"

data/scripts/01-get-technical-design-and-feature-list.md

@@ -0,0 +1,5 @@
+## Prompt:
+
+Write a Ruby script to read `docs/technical-specifictions.md` and `docs/feature-list.md`, 
+and  merge their content into `docs/generated/technical-design-and-features.md` and copy it to the clipboard.
+

data/scripts/01-get-technical-design-and-feature-list.rb

@@ -0,0 +1,39 @@
+#!/usr/bin/env ruby
+
+# Method to read file contents
+def read_file(file_path)
+  begin
+    File.read(file_path)
+  rescue => e
+    puts "Error reading file #{file_path}: #{e}"
+    ""
+  end
+end
+
+# Method to write content to a file
+def write_file(file_path, *contents)
+  merged_content = contents.join("\n")
+  begin
+    # Ensure the directory exists
+    Dir.mkdir(File.dirname(file_path)) unless Dir.exist?(File.dirname(file_path))
+    File.write(file_path, merged_content)
+  rescue => e
+    puts "Error writing to file #{file_path}: #{e}"
+  end
+end
+
+# Method to copy content to clipboard
+def copy_to_clipboard(content)
+  IO.popen('pbcopy', 'w') { |clip| clip.puts content }
+end
+
+# Main execution
+technical_design = read_file('docs/technical-specifications.md')
+feature_list = read_file('docs/feature-list.md')
+output_file = 'docs/generated/technical-design-and-features.md'
+
+# Merge and write the content to the output file
+write_file(output_file, technical_design, feature_list)
+
+# Copy content to clipboard
+copy_to_clipboard("#{technical_design}\n#{feature_list}")

data/scripts/02-get-feature-list-and-components.md

@@ -0,0 +1,26 @@
+## Prompt:
+
+Write a Ruby script to read `docs/feature-list.md` and merge it with content from `.builders/klues/*.klue` files.
+Write the result to `docs/generated/features-and-components.md` and copy it to the clipboard.
+
+The Klue files should need a heading: "Klue Components"
+
+The content from each Klue file have a simple heading and be wraped with in a code block with the language set to ruby.
+
+Example:
+
+
+## Klue Components
+
+Klue Component: `add_episode.klue`
+
+```ruby
+# content of add_episode.klue goes here
+```
+
+Klue Component: `change_chapter_name.klue`
+
+```ruby
+# content of change_chapter_name.klue goes here
+```
+