Skip to content

TODO.md

Latest commit

 

History

History
51 lines (45 loc) · 2.23 KB

TODO.md

File metadata and controls

51 lines (45 loc) · 2.23 KB

  • Project Setup & Initial File Creation:

    • Create PLAN.md with the detailed plan.
    • Create TODO.md with a checklist version of the plan.
    • Create CHANGELOG.md to track modifications.

  • Analyze install-mac.command for Streamlining:

    • Homebrew Installation:
      • Modify the script to check if Homebrew is already installed.
      • If not installed, proceed with installation.
      • If installed, inform the user and skip Homebrew installation.
    • Wine Version (wine-crossover vs. standard Wine):
      • For the MVP, retain the use of gcenx/wine and wine-crossover.
      • Add a comment in the script and PLAN.md noting this as a potential area for future investigation.
    • Tesseract Installation:
      • Keep Tesseract installation.
    • Temporary Download Location:
      • Modify script to download se.zip to a temporary directory.
      • Ensure temporary directory is cleaned up.
    • Error Handling & Verbosity:
      • Add set -e to the script.
      • Add more echo statements for user feedback.
    • Permissions for /usr/local/bin:
      • Check if /usr/local/bin is writable.
      • Provide instructions if sudo is needed for cp.
    • Clarity of Prompts:
      • Ensure Subtitle Edit ZIP URL prompt is clear.

  • Analyze subtitleeditw Script:

    • Error Redirection (2>/dev/null):
      • Remove 2>/dev/null.
    • Integration vs. Separate File:
      • Keep as a separate file.

  • Update README.md:

    • Reflect changes in install-mac.command.
    • Clarify Homebrew installation check.
    • Add note about wine-crossover.
    • Ensure GUI/CLI instructions are accurate.
    • Mention visibility of error output.

  • Testing (Conceptual):

    • Mentally walk through script logic and README.

  • Final Review and Cleanup:

    • Review all modified files.
    • Update PLAN.md and TODO.md.
    • Update CHANGELOG.md.

  • Submit Changes:

    • Commit changes with a clear message.
    • Use a descriptive branch name.