SaaS-FrameWork 0.1.1__tar.gz → 0.1.3__tar.gz

{saas_framework-0.1.1 → saas_framework-0.1.3}/MANIFEST.in

@@ -1,16 +1,16 @@
-include README.md
-include pyproject.toml
-recursive-include components *.py
-recursive-exclude * __pycache__ *.py[cod]
-prune .github
-prune .pytest_cache
-prune .pytest_tmp
-prune _base
-prune build
-prune catalog
-prune *.egg-info
-prune dist
-prune docs
-prune tests
-prune use_cases
-exclude files.zip
+include README.md
+include pyproject.toml
+recursive-include components *.py
+recursive-exclude * __pycache__ *.py[cod]
+prune .github
+prune .pytest_cache
+prune .pytest_tmp
+prune _base
+prune build
+prune catalog
+prune *.egg-info
+prune dist
+prune Diretrizes
+prune tests
+prune use_cases
+exclude files.zip

{saas_framework-0.1.1 → saas_framework-0.1.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: SaaS-FrameWork
-Version: 0.1.1
+Version: 0.1.3
 Summary: SaaS-FrameWork - sistema de componentes reutilizaveis para apps SaaS construido com Python e Flet
 Author-email: Almir Duarte <almir.jg@gmail.com>
 License-Expression: MIT
@@ -13,6 +13,8 @@ Classifier: Topic :: Software Development :: User Interfaces
 Requires-Python: >=3.13
 Description-Content-Type: text/markdown
 Requires-Dist: flet==0.84.0
+Provides-Extra: web
+Requires-Dist: flet-web==0.84.0; extra == "web"
 Provides-Extra: dev
 Requires-Dist: flet==0.84.0; extra == "dev"
 Requires-Dist: pytest<10,>=9.1; extra == "dev"
@@ -86,7 +88,7 @@ The following folders are repository assets and are intentionally excluded from
 
 - `catalog/`: local visual catalog and inspection tool.
 - `use_cases/`: executable examples for development and documentation.
-- `docs/`: component documentation and generated structure images.
+- `Diretrizes/`: project guidelines — prompts, design/component documentation, management artifacts, and QA evidence.
 - `_base/`: preserved reference material.
 
 This separation is enforced in `pyproject.toml` through `tool.setuptools.packages.find`.
@@ -98,15 +100,15 @@ Adding a public component requires all of the following:
 - entry in `components/metadata.py`
 - public export in `components/__init__.py`
 - use case `use_cases/UC_<Name>_01.py`
-- documentation `docs/components/Documentação/DEx_<Name>.md`
-- four structure images in `docs/components/images/`
+- documentation `Diretrizes/design/components/Documentação/DEx_<Name>.md`
+- four structure images in `Diretrizes/design/components/images/`
 
 The repository governance tests fail when this contract is broken.
 
 ## Folder Structure
 
 ```text
-DEx-FW_4/
+SaaS-Framework/
 |-- _base/                         preserved original reference
 |-- components/
 |   |-- buttons/
@@ -126,8 +128,14 @@ DEx-FW_4/
 |   |-- UC_TreeView_01.py
 |   `-- UC_ColorThemes_01.py
 |-- catalog/
-|   `-- main.py
-|-- docs/
+|   `-- catalog.py
+|-- Diretrizes/
+|   |-- Dados/                     data artifacts (DDL, DML, scripts)
+|   |-- Prompt/                    prompt files
+|   |-- design/                    design references and component docs/images
+|   |   `-- components/
+|   |-- gestao/                    roadmap, policies, and management reports
+|   `-- qa/                        QA evidence
 |-- AGENTS.md
 |-- pyproject.toml
 `-- README.md
@@ -149,18 +157,18 @@ Documented local virtual environment:
 C:\Python\venv\.venv_313_FW
 ```
 
-Run the catalog:
+Run the catalog as desktop app:
 
 ```cmd
 call C:\Python\venv\.venv_313_FW\Scripts\activate.bat
-flet run catalog/main.py
+flet run catalog/catalog.py
 ```
 
-Run as web catalog:
+Run as web catalog only when browser validation is required:
 
 ```cmd
 call C:\Python\venv\.venv_313_FW\Scripts\activate.bat
-flet run --web --port 8550 catalog/main.py
+flet run --web --port 8550 catalog/catalog.py
 ```
 
 Run a use case:
@@ -219,12 +227,12 @@ The script builds the package, checks the artifacts, and uploads to TestPyPI or
 With the documented Flet environment:
 
 ```cmd
-C:\Python\venv\.venv_313_FW\Scripts\python.exe -c "import catalog.main as c; print(c.PROJECT_VERSION)"
+C:\Python\venv\.venv_313_FW\Scripts\python.exe -c "import catalog.constants as c; print(c.PROJECT_VERSION)"
 ```
 
 ## Catalog
 
-The catalog entry point is `catalog/main.py`.
+The catalog entry point is `catalog/catalog.py`.
 
 It follows the project window structure:
 

{saas_framework-0.1.1 → saas_framework-0.1.3}/README.md

@@ -1,89 +1,89 @@
-# SaaS-FrameWork
+# SaaS-FrameWork
 
 Python 3.13 + Flet design framework for reusable SaaS UI components.
 
 The project provides versioned UI components, isolated use cases, and a navigable component catalog.
 
-## Versioning
-
-Library, component, and release branch versions follow the same `vv.rr.bb` rule.
-
-The library version is declared in `pyproject.toml`:
-
-```toml
-[project]
-version = "0.1.1"
-```
-
-Use cases and the catalog header read this version through `components/project.py`. Do not duplicate the project version manually in UI files.
-
-Each public component exposes its own version:
-
-```python
-COMPONENT_VERSION = "0.0.1"
-```
-
-Release branches must use the same format as the branch name:
-
-```text
-0.1.1
-```
-
-Do not prefix release branch names with `v`, `release/`, or any other text.
-
-The accepted format is:
-
-```text
-vv.rr.bb
-0.0.0 through 99.99.99
+## Versioning
+
+Library, component, and release branch versions follow the same `vv.rr.bb` rule.
+
+The library version is declared in `pyproject.toml`:
+
+```toml
+[project]
+version = "0.1.1"
 ```
 
-Segment meaning:
-
-- `vv`: version. Increment for large changes that alter visual form, public API, or how the library/component is used.
-- `rr`: release. Increment for small scoped changes, such as a specific behavior or item adjustment.
-- `bb`: bug correction. Increment when a bug is fixed.
-
-Every library or component change must increment the relevant version. Each segment is incremented by one numeral. When `bb` reaches `99`, the next `bb` increment increments `rr` and resets `bb` to `0`. When `rr` reaches `99`, the next `rr` increment increments `vv` and resets `rr` to `0`.
-
-Version helpers live in `components/versioning.py`:
-
-- `validate_version(version)`
-- `validate_branch_version(branch_name)`
-- `bump_version(version, segment="bugfix")`
-- `ComponentMeta`
-
-Catalog metadata lives in `components/metadata.py` and is the source of truth for component name, group, version, and description.
-
-## Package Boundary
-
-The distributable Python library is the `components` package.
-
-The following folders are repository assets and are intentionally excluded from the wheel:
-
-- `catalog/`: local visual catalog and inspection tool.
-- `use_cases/`: executable examples for development and documentation.
-- `docs/`: component documentation and generated structure images.
-- `_base/`: preserved reference material.
-
-This separation is enforced in `pyproject.toml` through `tool.setuptools.packages.find`.
-
-Adding a public component requires all of the following:
-
-- source file under `components/**/DEx_<Name>.py`
-- `COMPONENT_VERSION` in the source file
-- entry in `components/metadata.py`
-- public export in `components/__init__.py`
-- use case `use_cases/UC_<Name>_01.py`
-- documentation `docs/components/Documentação/DEx_<Name>.md`
-- four structure images in `docs/components/images/`
-
-The repository governance tests fail when this contract is broken.
+Use cases and the catalog header read this version through `components/project.py`. Do not duplicate the project version manually in UI files.
+
+Each public component exposes its own version:
+
+```python
+COMPONENT_VERSION = "0.0.1"
+```
+
+Release branches must use the same format as the branch name:
+
+```text
+0.1.1
+```
+
+Do not prefix release branch names with `v`, `release/`, or any other text.
+
+The accepted format is:
+
+```text
+vv.rr.bb
+0.0.0 through 99.99.99
+```
+
+Segment meaning:
+
+- `vv`: version. Increment for large changes that alter visual form, public API, or how the library/component is used.
+- `rr`: release. Increment for small scoped changes, such as a specific behavior or item adjustment.
+- `bb`: bug correction. Increment when a bug is fixed.
+
+Every library or component change must increment the relevant version. Each segment is incremented by one numeral. When `bb` reaches `99`, the next `bb` increment increments `rr` and resets `bb` to `0`. When `rr` reaches `99`, the next `rr` increment increments `vv` and resets `rr` to `0`.
+
+Version helpers live in `components/versioning.py`:
+
+- `validate_version(version)`
+- `validate_branch_version(branch_name)`
+- `bump_version(version, segment="bugfix")`
+- `ComponentMeta`
+
+Catalog metadata lives in `components/metadata.py` and is the source of truth for component name, group, version, and description.
+
+## Package Boundary
+
+The distributable Python library is the `components` package.
+
+The following folders are repository assets and are intentionally excluded from the wheel:
+
+- `catalog/`: local visual catalog and inspection tool.
+- `use_cases/`: executable examples for development and documentation.
+- `Diretrizes/`: project guidelines — prompts, design/component documentation, management artifacts, and QA evidence.
+- `_base/`: preserved reference material.
+
+This separation is enforced in `pyproject.toml` through `tool.setuptools.packages.find`.
+
+Adding a public component requires all of the following:
+
+- source file under `components/**/DEx_<Name>.py`
+- `COMPONENT_VERSION` in the source file
+- entry in `components/metadata.py`
+- public export in `components/__init__.py`
+- use case `use_cases/UC_<Name>_01.py`
+- documentation `Diretrizes/design/components/Documentação/DEx_<Name>.md`
+- four structure images in `Diretrizes/design/components/images/`
+
+The repository governance tests fail when this contract is broken.
 
 ## Folder Structure
 
 ```text
-DEx-FW_4/
+SaaS-Framework/
 |-- _base/                         preserved original reference
 |-- components/
 |   |-- buttons/
@@ -103,8 +103,14 @@ DEx-FW_4/
 |   |-- UC_TreeView_01.py
 |   `-- UC_ColorThemes_01.py
 |-- catalog/
-|   `-- main.py
-|-- docs/
+|   `-- catalog.py
+|-- Diretrizes/
+|   |-- Dados/                     data artifacts (DDL, DML, scripts)
+|   |-- Prompt/                    prompt files
+|   |-- design/                    design references and component docs/images
+|   |   `-- components/
+|   |-- gestao/                    roadmap, policies, and management reports
+|   `-- qa/                        QA evidence
 |-- AGENTS.md
 |-- pyproject.toml
 `-- README.md
@@ -126,18 +132,18 @@ Documented local virtual environment:
 C:\Python\venv\.venv_313_FW
 ```
 
-Run the catalog:
+Run the catalog as desktop app:
 
 ```cmd
 call C:\Python\venv\.venv_313_FW\Scripts\activate.bat
-flet run catalog/main.py
+flet run catalog/catalog.py
 ```
 
-Run as web catalog:
+Run as web catalog only when browser validation is required:
 
 ```cmd
 call C:\Python\venv\.venv_313_FW\Scripts\activate.bat
-flet run --web --port 8550 catalog/main.py
+flet run --web --port 8550 catalog/catalog.py
 ```
 
 Run a use case:
@@ -147,61 +153,61 @@ call C:\Python\venv\.venv_313_FW\Scripts\activate.bat
 flet run use_cases/UC_MetricCard_01.py
 ```
 
-## Validation
-
-Quick syntax validation:
+## Validation
+
+Quick syntax validation:
+
+```cmd
+python -m compileall components use_cases catalog
+```
+
+Run the automated test suite:
+
+```cmd
+C:\Python\venv\.venv_313_FW\Scripts\python.exe -m pytest -q
+```
+
+Run optional visual screenshots:
+
+```powershell
+C:\Python\venv\.venv_313_FW\Scripts\python.exe -m playwright install chromium
+$env:DEX_RUN_VISUAL_TESTS="1"
+C:\Python\venv\.venv_313_FW\Scripts\python.exe -m pytest tests/test_visual_screenshots.py -q
+```
+
+Build and validate package metadata:
 
 ```cmd
-python -m compileall components use_cases catalog
-```
-
-Run the automated test suite:
-
-```cmd
-C:\Python\venv\.venv_313_FW\Scripts\python.exe -m pytest -q
-```
-
-Run optional visual screenshots:
-
-```powershell
-C:\Python\venv\.venv_313_FW\Scripts\python.exe -m playwright install chromium
-$env:DEX_RUN_VISUAL_TESTS="1"
-C:\Python\venv\.venv_313_FW\Scripts\python.exe -m pytest tests/test_visual_screenshots.py -q
-```
-
-Build and validate package metadata:
-
-```cmd
-C:\Python\venv\.venv_313_FW\Scripts\python.exe -m build
-C:\Python\venv\.venv_313_FW\Scripts\python.exe -m twine check dist/*
-```
-
-Publish the package:
-
-```powershell
-.\tools\publish_package.ps1 --test
-.\tools\publish_package.ps1 --prod
-.\tools\publish_package.ps1 --both
-.\tools\publish_package.ps1
-```
-
-Without flags, the script asks:
-
-1. teste
-2. prod
-3. ambos
-
-The script builds the package, checks the artifacts, and uploads to TestPyPI or PyPI based on the chosen destination.
+C:\Python\venv\.venv_313_FW\Scripts\python.exe -m build
+C:\Python\venv\.venv_313_FW\Scripts\python.exe -m twine check dist/*
+```
+
+Publish the package:
+
+```powershell
+.\tools\publish_package.ps1 --test
+.\tools\publish_package.ps1 --prod
+.\tools\publish_package.ps1 --both
+.\tools\publish_package.ps1
+```
+
+Without flags, the script asks:
+
+1. teste
+2. prod
+3. ambos
+
+The script builds the package, checks the artifacts, and uploads to TestPyPI or PyPI based on the chosen destination.
 
 With the documented Flet environment:
 
 ```cmd
-C:\Python\venv\.venv_313_FW\Scripts\python.exe -c "import catalog.main as c; print(c.PROJECT_VERSION)"
+C:\Python\venv\.venv_313_FW\Scripts\python.exe -c "import catalog.constants as c; print(c.PROJECT_VERSION)"
 ```
 
 ## Catalog
 
-The catalog entry point is `catalog/main.py`.
+The catalog entry point is `catalog/catalog.py`.
 
 It follows the project window structure:
 
@@ -418,7 +424,7 @@ Controles de feedback do usuário para estados transitórios.
 ## Adding a Component
 
 1. Create the component under the correct `components/<group>/` folder.
-2. Add `COMPONENT_VERSION = "0.0.1"` for a new component.
+2. Add `COMPONENT_VERSION = "0.0.1"` for a new component.
 3. Add a docstring to the public component factory or class.
 4. Add metadata to `components/metadata.py`.
 5. Create an isolated use case in `use_cases/`.

{saas_framework-0.1.1 → saas_framework-0.1.3}/SaaS_FrameWork.egg-info/SOURCES.txt

@@ -49,6 +49,7 @@ components/inputs/DEx_SearchBar.py
 components/inputs/DEx_SearchField.py
 components/inputs/DEx_Slider.py
 components/inputs/DEx_Switch.py
+components/inputs/DEx_TagInput.py
 components/inputs/DEx_TextField.py
 components/inputs/DEx_TimePicker.py
 components/inputs/__init__.py
@@ -58,12 +59,14 @@ components/layout/DEx_AppShell.py
 components/layout/DEx_Draggable.py
 components/layout/DEx_GestureDetector.py
 components/layout/DEx_Header.py
+components/layout/DEx_Marquee.py
 components/layout/DEx_NavItem.py
 components/layout/DEx_NavigationBar.py
 components/layout/DEx_NavigationDrawer.py
 components/layout/DEx_NavigationRail.py
 components/layout/DEx_ResponsiveRow.py
 components/layout/DEx_Sidebar.py
+components/layout/DEx_Splitter.py
 components/layout/DEx_Stack.py
 components/layout/DEx_Tabs.py
 components/layout/__init__.py