Skip to content

About

No description, website, or topics provided.

Resources

Stars

2 stars

Watchers

0 watching

Forks

Repository files navigation

gtasks

License: MIT Language: Rust Build Status Platform: Linux

A modern, fast, offline-first Google Tasks desktop client & terminal dashboard for Linux built with Rust.

🎯 Purpose & Application Features

gtasks is an open-source productivity application designed to provide Linux users with a fast, native desktop client (GTK4/Libadwaita) and terminal dashboard (Ratatui) for managing their Google Tasks.

Key Application Features

  • πŸ–₯️ Dual Interface: Keyboard-driven Terminal User Interface (TUI) and GTK4 Desktop GUI.
  • πŸ“΄ Offline-First Management: Local SQLite cache allowing offline reading, creation, and editing of tasks.
  • πŸ—“οΈ Natural Language Recognition: Smart date parsing (e.g., "Buy milk tomorrow").
  • 🌲 Hierarchical Organization: Nested tasks and subtask management.
  • πŸ”„ Automatic Synchronization: Seamless background delta syncing with Google Tasks.

πŸ”’ Google User Data Access & Usage

gtasks requests access to your Google Account data via the official Google Tasks API (https://www.googleapis.com/auth/tasks). Here is how we handle and protect your data:

1. Why We Request Access to Google User Data

To function as a Google Tasks client on Linux, gtasks requires access to read, create, modify, and delete tasks and task lists in your Google account based strictly on your direct actions within the app.

2. How We Use Google User Data

  • Displaying Tasks: To show your task lists, task titles, descriptions, due dates, and completion status inside the application.
  • Task Management: To create, edit, reorder, mark complete, or delete tasks on your Google account when requested by you.
  • Background Synchronization: To sync changes made offline in the local SQLite database back to your Google Tasks account once online.

3. Data Protection & Privacy Guarantees

  • Local-First & No Third-Party Servers: gtasks does not transmit your tasks, account data, or authentication tokens to any external servers managed by MCR-Project or third parties. All API communication occurs directly between your local device and Google's official servers (googleapis.com).
  • Secure Local Credential Storage: OAuth 2.0 tokens are encrypted and stored using your operating system's native secret storage (e.g., Linux Secret Service / KWallet via keyring).
  • No Selling or Advertising: Your Google user data is never sold, rented, shared, or used for advertising or marketing.
  • No AI/ML Model Training: Google Workspace user data accessed by gtasks is never used to train, develop, or improve AI or Machine Learning models.

For full details, please review our complete Privacy Policy.


πŸ—οΈ Workspace Architecture

               β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
               β”‚          Terminal UI           β”‚      Desktop GUI      β”‚
               β”‚      (Ratatui / Crossterm)     β”‚   (Relm4 / GTK4)      β”‚
               β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                                   β”‚                   β”‚
                                   β–Ό                   β–Ό
               β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
               β”‚                   gtasks_core Engine                   β”‚
               β”‚  β€’ Tokio Async Runtime      β€’ OAuth 2.0 PKCE Handler   β”‚
               β”‚  β€’ Background Sync Engine   β€’ OS Keyring Credentials   β”‚
               β”‚  β€’ NLP Date Parsing         β€’ Task Hierarchy Processor β”‚
               β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                              β”‚                        β”‚
               β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β”€β”          β”Œβ”€β”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
               β”‚ Local SQLite Cache  β”‚          β”‚ Google Tasks REST API β”‚
               β”‚  (Fast offline read)β”‚          β”‚ (Background HTTP Sync)β”‚
               β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜          β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

The repository is structured as a Rust Cargo Workspace:

  • crates/gtasks_core - Core business logic, OAuth 2.0 PKCE flow, SQLite database persistence, background sync worker, and natural language date parser.
  • crates/gtasks_tui - Terminal dashboard application powered by Ratatui & Crossterm.
  • crates/gtasks_gui - Native Linux desktop GUI built with Relm4 (GTK4 / Libadwaita).

πŸ› οΈ Prerequisites & System Requirements

To build gtasks on Linux, ensure you have the Rust toolchain installed alongside native development headers:

1. Install System Dependencies

# Ubuntu / Debian
sudo apt update
sudo apt install build-essential pkg-config libssl-dev libsecret-1-dev libgtk-4-dev libadwaita-1-dev

# Fedora
sudo dnf install @development-tools openssl-devel libsecret-devel gtk4-devel libadwaita-devel

# Arch Linux / Manjaro
sudo pacman -S base-devel openssl libsecret gtk4 libadwaita

2. Configure Google API OAuth Credentials

Create a .env file in the root directory (or copy from template) containing your Google Cloud OAuth Client ID and Secret:

GOOGLE_CLIENT_ID=your_client_id_here
GOOGLE_CLIENT_SECRET=your_client_secret_here

πŸš€ Quick Start

Building & Running

# Clone the repository
git clone https://github.com/MCR-Project/google-tasks-gui.git
cd google-tasks-gui

# Run the Terminal User Interface (TUI)
cargo run -p gtasks_tui

# Run the Desktop GUI (GTK4 / Relm4)
cargo run -p gtasks_gui

Running Tests

cargo test

⌨️ TUI Keybindings

When running gtasks_tui, use the following keyboard controls:

Key Action
Tab Switch focus between Task Lists sidebar and Tasks view
j / Down Move selection down
k / Up Move selection up
g Jump to top of list
G Jump to bottom of list
Space Toggle task completion status ([ ] / [x])
c Create new task in active list
L Create new task list (when focused on Task Lists pane)
e Edit selected task details (Title, Notes, Due Date)
d / Delete Delete selected task
r Trigger manual sync with Google Tasks API
q Quit application

🧠 Natural Language Task Entry

When creating or editing tasks, natural language expressions in task titles are automatically parsed into structured due dates:

Input Text Resulting Task Title Extracted Due Date
Buy groceries today Buy groceries Today
Finish quarterly report tomorrow Finish quarterly report Tomorrow
Sync with team next monday Sync with team Next Monday

πŸ—ΊοΈ Roadmap & Project Status

  • Phase 0: Workspace Architecture
    • Modular Cargo workspace (gtasks_core, gtasks_tui, gtasks_gui).
  • Phase 1: Secure Core & Engine
    • OAuth 2.0 PKCE authentication flow with local loopback listener.
    • Linux System Keyring integration (Secret Service / KWallet).
    • SQLite local database cache (task_lists.db).
    • Google Tasks REST API client integration.
    • Natural Language Date Parsing (NLP).
  • Phase 2: User Interfaces
    • Interactive Terminal User Interface (gtasks_tui).
    • Native Linux GTK4 Desktop GUI (gtasks_gui).
  • Phase 3: Sync & Offline Resilience
    • Offline edit queuing with dirty_bit flag tracking.
    • Background delta sync engine.
    • Soft-deletion queue & sync.
  • Phase 4: Packaging & Distribution
    • Flatpak & AUR packaging.
    • Desktop entry & icon integration.

🀝 Contributing

Contributions are very welcome! If you find a bug or have a feature suggestion, please feel free to open an issue or submit a pull request.

  1. Fork the Repository
  2. Create your Feature Branch (git checkout -b feature/amazing-feature)
  3. Commit your Changes (git commit -m 'Add some amazing-feature')
  4. Verify tests pass (cargo test)
  5. Push to the Branch (git push origin feature/amazing-feature)
  6. Open a Pull Request

πŸ”’ Privacy Policy

gtasks is a local-first application and prioritizes your data privacy. Google Tasks data and OAuth tokens are strictly stored locally on your device or in your OS Keyring and are never transmitted to any third-party servers. For details, see the complete Privacy Policy.


πŸ“„ License

This project is licensed under the MIT License - see the LICENSE file for details.

About

No description, website, or topics provided.

Resources

Stars

2 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages