Metadata-Version: 2.4
Name: TaskTonic
Version: 0.2.0
Summary: TaskTonic is a Python framework designed to manage application complexity through a unique concurrency model.
Author-email: Peter <208develop@gmail.com>
Project-URL: Homepage, https://github.com/208develop/TaskTonicc
Project-URL: Issues, https://github.com/208develop/TaskTonic/issues
Project-URL: Documentation, https://github.com/208develop/TaskTonic/tree/master/_documents
Classifier: Programming Language :: Python :: 3
Classifier: License :: OSI Approved :: MIT License
Classifier: Operating System :: OS Independent
Requires-Python: >=3.8
Description-Content-Type: text/markdown
License-File: LICENSE
Dynamic: license-file

# What is TaskTonic?

## Philosophy & Metaphor

TaskTonic is a Python framework designed to manage application complexity through a unique concurrency model.

The core philosophy is based on the **Tonic**. Think of your running application as a glass of tonic. It comes to life
through **Sparkles**, the **bubbles** rising in a liquid.

* **The Flow:** Code is executed in small, atomic units called *Sparkles*.
* **The Fizz:** When these Sparkles flow continuously, the application "fizzes" with activity. It feels like a single,
  cohesive whole, even though it may be performing multiple logical processes simultaneously.
* **The Rule:** A Sparkle must be short-lived. If one bubble takes too long to rise (blocking code), the flow stops, and
  the fizz goes flat. In practice, this is rarely an issue, as most software processes are reactive chains of short
  events.

This architecture allows you to write highly responsive, concurrent applications (like UIs or IoT controllers) without
the race conditions and headaches of traditional multi-threading.

## Use Cases

- TaskTonic is ideal for any scenario where you need to orchestrate numerous independent components:
- Responsive User Interfaces: Keep your UI fluid while performing heavy computations in the background.
- IoT & Sensor Networks: Process a continuous stream of events and measurements from thousands of devices.
- Communication Servers: Manage thousands of concurrent connections for chat applications, game servers, or data streams.
- Complex Simulations: Build simulations (e.g., swarm behavior, traffic models) where each entity acts autonomously.
- Asynchronous Data Processing: Create robust data pipelines where information is processed in small, distinct steps.

*...or all of the above, at the same time. That's where the framework's power truly lies.*

## Documentation

No documentation, no framework. Look into the **\_documents** map and read it all.
