Store Notes as Markdown into folders with hierarchy

Many note apps let you save the entire database as individual files within a folder hierarchy. Floaters could also save and load with this format instead of the .floaters file format for users that would want to use other apps with their data.
Tom Iwaniec about 1 month ago
  • 5 days ago

    ## **Concept**: Saving Notes and Metadata in a File-Based Structure

    I really appreciate the idea of saving notes in a file-based hierarchy, specifically using Markdown files for the content. And saving all meta information related to each note in a hidden `.floaters`.

    **Format for Meta Information**

    To enhance interoperability and transparency, a standardized exchange format like JSON could help. This would allow both users and third-party applications to:

    - easily view and understand the meta information (such as background color, transparency, monitor placement, group assignment, etc.),
    - alter or update these settings manually if necessary.

    **Indexing for Performance**

    To avoid the need for Floaters to constantly scan all folders and files to often or in a way to short interval, a centralized indexing and catalog mechanism could be introduced into an lightweight SQL-based database file (placed in project root or offical "Documents" folder of MacOS).

    This index would:

    - keep track of all available Markdown notes and their associated meta files,
    - categorize and locate floaters efficiently,
    - minimize filesystem reads and improve the app's overall performance.

    The choice of database format and structure should be flexible, depending on the developer's preferences.