Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like A clear and concise description of what you want to happen.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like A clear and concise description of what you want to happen.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

Luxoria Desktop Software (Main Release)

| |

Luxoria is a powerful all-in-one photography solution designed to streamline your workflow. Whether you are an individual photographer or part of a team, Luxoria makes it easy to manage and enhance your images, collaborate with clients, and deliver exceptional results.

📸 Introduction

Luxoria offers photographers a comprehensive solution to optimize their image workflow. Our desktop application simplifies the process of importing, organizing, editing, and exporting images, while our web platform enables easy sharing and client feedback. The platform ensures photographers can focus on their creative process while effortlessly managing their projects.

Desktop App Highlights:

• Import images directly from your camera or storage devices.

• Organize your photos into albums and collections.

• Edit with a wide range of powerful editing tools, including AI enhancements.

• Collaborate with clients to refine and finalize image selections.

Web Platform Highlights:

• Share images via a web gallery.

• Allow clients to view and select their favorite photos.

• Collect feedback directly from clients in real-time.

🛠️ Features

• Image Importation: Seamless image import from cameras or local storage.

• Smart Organization: Organize images into albums, collections, or folders based on date, location, camera settings, and more.

• Advanced Filters: Search and filter images by metadata, including date, location, and camera settings.

• Editing Tools: Utilize a variety of editing tools such as cropping, color correction, retouching, and AI-powered enhancements.

🚀 Getting Started

1. Download and Install: Download the Luxoria desktop application from our website and follow the installation steps.

2. Set Up: Import your first batch of photos and start organizing your library.

3. Explore Features: Try out the editing tools, filters, and collaborative workflows.

4. Share with Clients: Upload selected photos to the web platform and invite clients to review and provide feedback.

💡 Why Luxoria?

Luxoria is more than just a photo editing tool, it's a complete photography management platform. From the moment you capture a shot, Luxoria ensures your photos are organized, edited, and shared efficiently. With AI-powered tools, intuitive collaboration features, and an easy-to-use interface, Luxoria is designed for photographers who want to focus on creativity while streamlining their workflow.

📄 License

Luxoria is licensed under the Apache 2.0 License. See the file for more details.

Feel free to contribute or explore the codebase. Luxoria is constantly evolving, and we welcome your feedback and suggestions!

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

1. Go to '...'

2. Click on '....'

3. Scroll down to '....'

To run the Catalyst demo, first install the npm dependencies:

Next, run the development server:

Finally, open in your browser to view the website.

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

1. Go to '...'

2. Click on '....'

3. Scroll down to '....'

4. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]

• Browser [e.g. chrome, safari]

• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]

• OS: [e.g. iOS8.1]

• Browser [e.g. stock browser, safari]

• Version [e.g. 22]

Additional context Add any other context about the problem here.

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

1. Go to '...'

2. Click on '....'

3. Scroll down to '....'

4. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]

• Browser [e.g. chrome, safari]

• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]

• OS: [e.g. iOS8.1]

• Browser [e.g. stock browser, safari]

• Version [e.g. 22]

Additional context Add any other context about the problem here.

See RECAP_20_11_2024, RECAP_12_06_2025, RECAP_03_04_2025, RECAP_03_04_2025_1

Professional Photographers

See 1 & 2 & 3

Feebacks

See 4

Brisque Score Nuget

https://www.nuget.org/packages/Luxoria.Algorithm.BrisqueScore, See : 1, 2

+2700 Downloads as of 22/06/2025

Luxoria SDK

https://www.nuget.org/packages/Luxoria.SDK#readme-body-tab, See : 3

Luxoria Algorithm YoLo Detect Model in .NET

https://www.nuget.org/packages/Luxoria.Algorithm.YoLoDetectModel, See : 4

GrabCut Implementation (v1.0.0 / v1.0.1)

https://www.nuget.org/packages/Luxoria.Algorithm.YoLoDetectModel, See : 5

Luxoria (Front-End) LuxPortal Public Docker Image

https://hub.docker.com/r/luxoria/luxstudio (+736 Downloads)

LuxStudio (Back-End) LuxAPI Public Docker Image

https://hub.docker.com/r/luxoria/luxapi (+539 Downloads)

Repository

https://github.com/LuxoriaSoft/Luxoria (+971 commits)

An average of 25 unique visitors per 15 days

Online Luxoria Dev. documentation

https://docs.luxoria.bluepelicansoft.com

Issues

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like A clear and concise description of what you want to happen.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

Our Pledge

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

Our Standards

Examples of behavior that contributes to a positive environment for our community include:

• Demonstrating empathy and kindness toward other people

• Being respectful of differing opinions, viewpoints, and experiences

• Giving and gracefully accepting constructive feedback

• Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience

Examples of unacceptable behavior include:

• The use of sexualized language or imagery, and sexual attention or advances of any kind

• Trolling, insulting or derogatory comments, and personal or political attacks

• Public or private harassment

• Publishing others' private information, such as a physical or email address, without their explicit permission

Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.

Scope

This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [email protected]. All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the reporter of any incident.

Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

1. Correction

Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.

Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.

2. Warning

Community Impact: A violation through a single incident or series of actions.

Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

3. Temporary Ban

Community Impact: A serious violation of community standards, including sustained inappropriate behavior.

Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

4. Permanent Ban

Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.

Consequence: A permanent ban from any sort of public interaction within the community.

Attribution

This Code of Conduct is adapted from the , version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.

Community Impact Guidelines were inspired by .

For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

Description

This document defines the manual test protocol for building and validating Luxoria.App and its associated modules and components on three target architectures: x64, x86, and ARM64. Each module LuxImport, LuxFilter, LuxEditor, LuxExport, LuxStudio and the standard component Marketplace is built and tested individually. Developers are responsible for executing and documenting all feature tests.

Scope

• Build validation for Luxoria.App on x64, x86, ARM64.

• Module assembly and feature verification for each module and the Marketplace component.

• Manual test cases executed by module developers.

Prerequisites

• Source code checkout of Luxoria repository (latest main branch).

• Visual Studio 2022 + WinUI Developpement Tool

• Windows App 10/11/1X SDK

• Windows 10/11

Build and Verification Procedures

1. Open VS 2022

2. Load Luxoria.App.sln

3. Run Luxoria.App

4. Build each module such as

• LuxImport

• LuxFilter

• LuxEditor

• LuxExport

1. Execute each testing requirements (see below for specifications)

Testing Specifications

LuxImport

TEST 1:

Open an existing Collection : OK

TEST 2:

Open a new folder, then create a new name and click on import : OK

Success : A pop-up is being displayed after the importation has been completed

Luxfilter

TEST 1:

Check Brisque Algorithm Click on Save / Sync : OK

TEST 2:

Check CLIP Model Click on Save / Sync: OK

TEST 3:

Select another model/algorithm Click on Save / Sync : OK

LuxEditor

TEST 1:

Tricks some parameters : OK

TEST 2:

Tricks some parameters Crop image : OK

TEST 3:

Tricks some parameters Crop the image Use the layer system Crop image : OK

LuxExport

TEST 1:

Export as PNG : OK

TEST 2:

Export as other format Usage of watermark : OK

TEST 3:

Export as other format Usage of watermark (icon) Usage of naming template : OK

LuxExport + LuxStudio

TEST 1:

Connect to Studio : OK

TEST 2:

Connect to Studio : OK Export to studio : OK

Bugs / Issues

For any bug found, please create an issue here : https://github.com/LuxoriaSoft/Luxoria/issues

Requirements

• Docker (min. 27.4.0)

• Docker Compose

Installation

1. Clone the repository

2. Run docker-compose up in the LuxStudio directory

3. Run dotnet tool install --global dotnet-ef in the LuxAPI directory

Introduction

This is the official documentation for the Luxoria project.

How to use

To use this documentation, simply navigate to the desired section, please navigate in the selected section to find the desired information.

Are you ready for development ?

If you are ready to start developing, please follow the .

Good practices

• Always use the latest version of the documentation.

• If you find any errors, please report them.

• If you have any suggestions, please let us know.

• If you want to contribute, please follow the .

Contributing

If you want to contribute to this documentation, please follow the .

The Standard Editing Module

✨ Features

• Non-Destructive Editing Every change is stored as adjustments/layers, your originals stay untouched.

Name: Luxoria - Pull Request Title: [L__] - (____) ... Assignees:

Description

Provide a brief summary of the changes in this PR, including any context necessary for understanding it.

Newly issue on OpenCV GrabCut Implementation

https://github.com/opencv/opencv/issues/27058

See 1

BenchmarkDotNet v0.14.0, Windows 11 (10.0.26100.2894) Apple Silicon, 6 CPU, 6 logical and 6 physical cores .NET SDK 9.0.102 [Host] : .NET 9.0.1 (9.0.124.61010), Arm64 RyuJIT AdvSIMD DEBUG DefaultJob : .NET 9.0.1 (9.0.124.61010), Arm64 RyuJIT AdvSIMD

Scientific Published Papers

Specific Panoptic Segmentation

The Standard Importation Module

✨ Features

• One-Click Collection Initialization Import entire folders to quickly build your photo database.

This template should help get you started developing with Vue 3 and TypeScript in Vite. The template uses Vue 3 <script setup> SFCs, check out the to learn more.

Learn more about the recommended Project Setup and IDE Support in the .

Date & Time: 20 November 2024 5PM06

Attendees:

• Romain B

• Luxoria Team

Date & Time: 3 April 2025 2PM

Attendees:

• Yoo, Y

• Noah GOSCINIAK

1. Executive Summary

Yoo, Young Joon shared expert insights on modern computer vision segmentation techniques. Key recommendations included U-Net variants and Fully Convolutional Network (FCN) deep learning models to address our image segmentation needs.

2. Discussion Points

Computer Vision Segmentation Overview

• Importance of precise pixel-level classification for our use cases (e.g., medical imagery, scene understanding).

U-Net Family of Models

• Architecture: Encoder–decoder with skip connections for fine-grained feature recovery.

• Variants:

  • U-Net++ (nested U-Net) for richer multi-scale feature fusion.

  • Attention U-Net to focus on relevant spatial regions.

Fully Convolutional Networks (FCNs)

• Core Idea: Replace fully connected layers with convolutional layers for end-to-end segmentation.

• Notable Models:

  • FCN-8s for coarse-to-fine upsampling.

  • DeepLab (atrous convolutions + CRF) for sharper boundaries.

Model Selection Criteria

• Data Volume & Annotation Quality

• Compute Resources & Inference Latency

• Target Application Requirements (e.g., boundary precision vs. speed)

3. Decision

Evaluate and prototype both a U-Net variant and an FCN-based model on our dataset to compare accuracy, speed, and resource utilization.

4. Next Steps & Action Items

Set up data pipeline and preprocess images for segmentation tasks Implement baseline U-Net and run initial training/validation Implement baseline FCN-8s (and DeepLab if resources allow) Compare metrics (IoU, pixel accuracy, inference time) Review results with Yoo, Young Joon and refine model selection

Introduction

This is the official documentation for the Luxoria project.

• How to contribute

• Development guidelines

Are you ready for development ?

If you are ready to start developing, please follow the .

How to contribute

To contribute to this documentation, please follow the steps below:

Step 1: Fork the repository

• Click on the Fork button at the top right corner of the repository.

Step 2: Clone the repository

• Clone the repository to your local machine using the following command:

Step 3: Create a new branch

• Create a new branch using the following command:

Step 4: Make changes

• Make the necessary changes to the documentation.

Step 5: Commit changes

• Commit the changes using the following command:

Step 6: Push changes

• Push the changes to the repository using the following command:

Step 7: Create a pull request

• Create a pull request from your forked repository to the original repository.

Date & Time: June 19, 2025 · 18:00

Attendees:

• Léo F

• Whole Luxoria Team

1. Executive Summary

Initiated the LuxStudio refactor to enhance user experience and operational robustness. Key focus areas include UI improvements, English language fixes, automated Kubernetes deployments via CircleCI, and strengthened user security with hCaptcha and a two-step registration form.

2. Discussion Points

UI & Usability Enhancements

• Revamp layouts and controls for clearer workflows

• Improve responsiveness and accessibility standards

• Standardize component library for consistency

English Language Fixes

• Audit existing UI text for grammar and clarity

• Implement i18n framework to simplify future translations

• Review error messages and tooltips for user-friendly wording

Automated Deployment (Kubernetes + CircleCI)

• Define Kubernetes manifests (Deployments, Services, Ingress) under k8s/

• Create CircleCI pipeline:

  • Build Docker image on merge to main

User Security & Registration Workflow

• Embed hCaptcha on signup and login forms

• Design double-form registration:

  1. User enters email & password

  2. System sends temporary code via email

3. Decision

Move forward with the full refactor as outlined, prioritizing UI polish and deployment automation in parallel, followed by security enhancements.

4. Next Steps & Action Items

Draft UI mockups and component spec Perform UI text audit and integrate i18n library Define Kubernetes manifests and CircleCI config prototype Implement hCaptcha on auth pages and build registration flow Conduct end-to-end tests (UI, deployment, registration security) Update user documentation and release notes

The Smart Filtering Module

✨ Features

• AI-Powered Filters Apply filters like Brisque (image quality), CLIP (semantic search), Resolution, and Sharpness to automatically evaluate assets.

• Quality & Ranking Each filter generates scores you can use to rate, flag, or organize your collection.

• Non-Destructive Evaluation Filtering only tags or scores items – your original assets remain unchanged.

• Forward Sync Send selected and scored assets forward into other modules (e.g., LuxEditor, LuxExport) with one click.

• Integrated Ratings & Flags View and manage ratings, flags, and filter scores in a dedicated side panel.

• Simple Save & Sync Persist results for future sessions or sync directly with the workspace.

📂 How It Works

1. Import Bring in your media from LuxImport or other connected modules.

2. Filter Explorer Run AI-driven filters (Brisque, CLIP, Resolution, Sharpness) to evaluate asset quality.

3. Review Scores Check Rating, Flags, and Scores in the right-side panel to identify the best candidates.

📌 Coming Soon

• More filter algorithms (noise, color harmony, aesthetics)

• Batch filter pipelines with presets

• Exportable filter profiles

📄 License

Luxoria and all standard modules are licensed under the Apache 2.0 License. See the for details.

The Standard Editing Module

✨ Features

• Non-Destructive Editing Every change is stored as adjustments/layers, your originals stay untouched.

• Core Adjustments White balance (Temperature/Tint), Exposure, Contrast, Highlights/Shadows, Whites/Blacks.

• Presence & Color Control Texture, Dehaze, Vibrance, Saturation for quick pop without overcooking.

• Pro Tone Curve Intuitive curve editor (RGB & channels) for precise tonal shaping.

• Crop & Layers Fast cropping plus layer-based workflows for organized edits.

• Subject Recognition (Mask-Ready) Kickstart local edits with one-click subject detection.

• Presets & Quick Culling One-click looks, star/flag tools, and a film-strip for rapid review.

• Inline EXIF/Metadata Viewer See camera data while you edit, no context switching.

• Reset & Compare, Undo/Redo Confidence to experiment, with instant safety nets.

• Clean, Focused UI Editor, Crop, Layers, Export tabs, everything where you expect it.

📂 How It Works

1. Open Pick photos from your Collection Importer (LuxImport)

2. Filter Thanks to LuxFilter, apply filters (quality, scores, ranking, etc.) to select the best subset

3. Adjust Start with Basic (WB, Tone, Presence), then refine with Curve or Layers.

4. Mask Manual masks for targeted edits.

📌 Coming Soon

• Customizable shortcuts and a lightweight plugin API

📄 License

Luxoria and all standard modules are licensed under the Apache 2.0 License. See the for details.

Feel free to contribute or open issues - LuxEditor evolves with your feedback!

Overview

Luxoria Standard Modules (LuxStd Modules) are a collection of core modules designed to provide essential functionalities within the Luxoria ecosystem. These modules follow a standardized architecture, ensuring seamless integration, extensibility, and interoperability with other Luxoria components.

Characteristics of LuxStd Modules

• Modular Design: Each module follows a plug-and-play architecture.

• Event-Driven: Modules communicate through event-based interactions using IEventBus.

• Extensible: Can be enhanced with additional features without breaking compatibility.

List of LuxStd Modules

1. LuxImport

• Handles the importation, indexing, and management of digital asset collections.

• Processes large datasets with asynchronous operations and progress tracking.

2. LuxFilter

• Provides a filtering pipeline for processing and scoring digital assets.

• Uses a modular filtering algorithm framework with weighted execution.

3. LuxExport

• Provides advanced export functionalities for asset collections.

• Supports multi-format output, custom file naming, and export conflict resolution.

Conclusion

LuxStd Modules form the backbone of the Luxoria ecosystem, ensuring a robust, scalable, and modular approach to handling digital assets. Their event-driven and extensible design makes them ideal for a wide range of applications within the system.

Date & Time: 12 June 2025 6PM

Attendees:

• Léo F

• Whole Luxoria Team

1. Executive Summary

Our current distribution process requires users to manually download a GitHub release, unzip it, and move files into Program Files. To streamline deployment and improve user experience, we have decided to develop a native executable installer.

2. Discussion Points

Current Installation Process

• Navigate to our GitHub repository’s “Releases” page

• Download the .zip archive of the latest version

• Extract contents locally

• Manually move the application folder into C:\Program Files\…

Pain Points

• Multiple manual steps prone to user error

• No version-check or upgrade path

• Lack of automated shortcut creation and uninstaller

• Support overhead for installation issues

Proposed Installer Solution

• Executable Installer

  • Bundle binaries, assets, and dependencies

  • Automate directory placement under Program Files

  • Create Start menu/desktop shortcuts

3. Decision

Proceed with designing and building a native Windows executable installer for our application.

4. Next Steps & Action Items

Research and select an installer framework (e.g., NSIS, Inno Setup, MSI) Develop a prototype executable installer Conduct cross-environment testing (Windows versions & permissions) Update documentation and publish installer on GitHub Releases

Personal License

Tailwind Labs Inc. grants you an on-going, non-exclusive license to use the Components and Templates.

The license grants permission to one individual (the Licensee) to access and use the Components and Templates.

You can:

• Use the Components and Templates to create unlimited End Products.

Development Guidelines

To contribute to this project, please follow the guidelines below to ensure consistency and quality in our development process.

Gitflow Workflow

Overview

LuxFilter is a modular filtering system designed for processing and scoring digital assets efficiently. It integrates with the Luxoria ecosystem and provides a pipeline-based approach to apply filtering algorithms to image data.

Features

Overview

LuxImport is a modular system designed for importing, indexing, and managing digital collections efficiently. It integrates with the Luxoria ecosystem and provides functionalities for handling structured asset collections.

Features

The Collaboration & Delivery Module

✨ Features

• Real-Time Client Collaboration Share galleries instantly and receive feedback, or comments in one web-enabled space.

Last Modification : 22/06/2025

1. Introduction

Luxoria is committed to open-source development, fostering innovation, and enabling collaboration within the developer community. After careful consideration, we have chosen the Apache License 2.0 for our repositories due to its balance of permissiveness, protection, and clarity.

2. Key Reasons for Choosing Apache 2.0

2.1. Permissive and Business-Friendly

Apache 2.0 is a permissive open-source license that allows anyone to freely use, modify, and distribute our code. This means individuals and businesses can adopt Luxoria's technologies without worrying about restrictive obligations, making it easier for our software to be widely used and integrated.

2.2. Patent Protection

A major advantage of Apache 2.0 over some other permissive licenses (such as MIT or BSD) is its explicit grant of patent rights. Contributors automatically grant a license to any patents they hold related to their contributions, which reduces the risk of patent litigation and provides more legal certainty for users of our software.

2.3. Contributor and User Protection

By using Apache 2.0, we ensure that both contributors and users are protected from unexpected legal complications. The license includes:

• A patent grant ensuring that contributors cannot later sue users for patent infringement based on their contributions.

• A liability disclaimer, protecting both Luxoria and contributors from legal claims arising from the use of the software.

2.4. Encourages Open-Source Contributions

Since Apache 2.0 does not impose copyleft requirements (unlike the GPL), developers and businesses can confidently contribute to Luxoria's repositories without concerns about needing to open-source their proprietary software that incorporates our code.

2.5. Well-Recognized and Widely Used

Apache 2.0 is a widely adopted and trusted license in the open-source community. Many large-scale projects, such as Kubernetes, TensorFlow, and Apache Software Foundation projects, use this license, which ensures familiarity and trust among developers and businesses.

3. Comparison with Other Open-Source Licenses

Choosing the right open-source license is crucial for defining how a project can be used and shared. Here’s a quick comparison of Apache 2.0 with other common open-source licenses:

4. Conclusion

The Apache License 2.0 aligns with Luxoria’s goals of fostering innovation, collaboration, and broad adoption of our open-source software. Its permissiveness, strong patent protections, and business-friendly terms make it the ideal choice for our repositories.

By choosing Apache 2.0, we empower developers while ensuring that both contributors and users benefit from a legally sound and transparent licensing framework.

5. Alignment with Luxoria’s Long-Term Strategy

Luxoria aims to become a modular and extensible platform, enabling a community of users, contributors, and partners to evolve alongside the project. The use of a permissive license like Apache 2.0 facilitates:

• Integration into proprietary or commercial products.

• Collaboration with companies that may not wish to open-source their enhancements.

• Development of an ecosystem around the project, including plugins, modules, and third-party services.

6. Legal Clarity and International Applicability

Apache 2.0 is internationally recognized and offers substantial legal clarity, notably through:

• Explicit and detailed wording that is understandable to legal teams.

• Compatibility with diverse legal frameworks (Europe, North America, etc.).

• Clear management of contributions and associated rights, essential for a multi-contributor project.

7. Governance and Contribution Model

The choice of license influences project governance. By opting for Apache 2.0, Luxoria:

• Avoids debates or friction related to copyleft (often perceived as restrictive).

• Encourages diverse contributions (code, documentation, plugins) without legal barriers.

• Retains the option to adopt a Contributor License Agreement (CLA) if needed in the future.

8. Community Feedback and Precedent

We have reviewed the practices of similar projects (e.g., Next.js, Vite, Strapi):

• Many use permissive licenses like MIT or Apache 2.0.

• Developer feedback indicates that freedom of use without constraints is a key factor for adoption.

The choice of Apache 2.0 aligns with this community-driven logic.

9. Risks Considered and Rejected Licenses

Before finalizing our decision, we evaluated several alternatives:

• GPLv3: Rejected for its "viral" effect, which is incompatible with our goal of broad distribution, including in closed environments.

• MIT: Too brief and lacks an explicit patent grant—posing a significant risk for technological innovation.

• MPL 2.0: Offers a middle ground but is more complex to understand for some contributors.

For more details on the Apache License 2.0, see: https://www.apache.org/licenses/LICENSE-2.0

Requirements

• .NET 8

• PostgreSQL

• Docker (min. 27.4.0) (optionnel pour déploiement)

• Docker Compose (optionnel pour déploiement)

Installation

1. Cloner le dépôt

2. Configurer les variables d'environnement

Crée un fichier .env à la racine du projet et ajoute :

3. Restaurer les dépendances

4. Appliquer les migrations

5. Lancer l'API

API Endpoints

Authentication

Collections

Chat (SignalR)

Hub Address: /hubs/chat

Méthodes disponibles :

• SendMessage(collectionId, senderEmail, message) → Envoie un message à tous les clients du groupe

• JoinCollection(collectionId) → Rejoint un groupe SignalR pour une collection

• LeaveCollection(collectionId) → Quitte un groupe SignalR

Running with Docker

1. Build and run the Docker containers

2. Accéder à l'API

📌

3. Accéder à MinIO

📌

Swagger Documentation

Swagger UI est disponible à l'adresse : 📌

This document describes the various events used in the Luxoria.Modules.Models.Events namespace, their purpose, and technical details.

List of Events

1. FilterCatalogEvent - Requests and retrieves a list of available filters.

2. CollectionUpdatedEvent - Notifies when a collection has been updated.

3. LogEvent - Sends a log message to the logging system.

4. RequestWindowHandleEvent - Requests the native window handle.

5. TextInputEvent - Sends a text input event.

1. FilterCatalogEvent

Purpose

The FilterCatalogEvent is used to request and retrieve a list of available filters asynchronously.

Technical Details

• Namespace: Luxoria.Modules.Models.Events

• Implements: IEvent

• Response Handling: Uses TaskCompletionSource<List<(string Name, string Description, string Version)>> to handle asynchronous responses.

Event Flow

1. A component publishes the event.

2. A subscriber (e.g., a filter manager) listens and provides the filter list.

3. The event’s TaskCompletionSource is completed with the filter list.

4. The publisher receives the list.

Code Example

2. CollectionUpdatedEvent

Purpose

The CollectionUpdatedEvent notifies subscribers when a collection has been updated.

Technical Details

• Namespace: Luxoria.Modules.Models.Events

• Implements: IEvent

• Properties:

Event Flow

1. A module publishes this event after updating a collection.

2. Subscribers (e.g., UI components) react to the update.

Code Example

3. LogEvent

Purpose

The LogEvent is used to send log messages for debugging or monitoring purposes.

Technical Details

• Namespace: Luxoria.Modules.Models.Events

• Implements: IEvent

• Properties:

Event Flow

1. Any component can publish this event to log information.

2. A logger service listens for this event and processes the message.

Code Example

4. RequestWindowHandleEvent

Purpose

The RequestWindowHandleEvent allows a component to request the native window handle.

Technical Details

• Namespace: Luxoria.Modules.Models.Events

• Implements: IEvent

• Properties:

Event Flow

1. A component publishes this event with a callback.

2. A subscriber (e.g., the main window) calls the callback with the window handle.

Code Example

5. TextInputEvent

Purpose

The TextInputEvent is used to transmit a text input from one component to another.

Technical Details

• Namespace: Luxoria.Modules.Models.Events

• Implements: IEvent

• Properties:

Event Flow

1. A component publishes this event with a text message.

2. A subscriber processes the text input.

Code Example

Conclusion

This document outlines the core events used in Luxoria's event-driven architecture. Each event plays a crucial role in communication between components, improving modularity and scalability.

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

   "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.

   "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.

   "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

   "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.

   "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.

   "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

   "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).

   "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.

   "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."

   "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:

   (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and

   (b) You must cause any modified files to carry prominent notices stating that You changed the files; and

   (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and

   (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.

5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work.

Copyright 2024 Luxoria

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

LuxImport is a image collection management system designed for efficient indexing, asset organization, and metadata handling. It provides capabilities for importing, processing, and managing image datasets, making it an ideal solution for large-scale photography and media applications.

Architecture

LuxImport follows a modular architecture to ensure scalability, maintainability, and high performance. The key components are:

1. Core Components

• ImportService: Handles the import process, including asset hashing, metadata extraction, and database initialization.

• Manifest Repository: Manages the manifest file that keeps track of indexed assets.

• LuxConfig Repository: Stores configuration settings related to collections and assets.

• FileHasherService: Computes unique hashes for images to prevent duplication.

2. Data Flow

1. Initialization: The system checks whether the target collection exists and initializes it if necessary.

2. Indexing: Images are scanned, hashed, and added to the database with relevant metadata.

3. Storage & Retrieval: Indexed assets are stored with reference to their respective manifest files.

4. Loading Assets: Assets are loaded from storage and processed based on application requirements.

3. Technologies Used

• .NET 9: Primary Framework.

• BenchmarkDotNet: Used for performance benchmarking.

• System.Threading.Tasks: Ensures efficient async processing.

• Concurrent Collections: Optimizes parallel data processing.

Testing

LuxImport includes a robust testing strategy to ensure stability and correctness.

1. Unit Tests

• Covers core functionalities such as:

  • Initialization of import service.

  • Manifest file creation and retrieval.

  • File hashing and metadata extraction.

2. Integration Tests

• Verifies the interaction between different modules.

• Tests how the ImportService handles large datasets.

3. Performance Tests

• Uses BenchmarkDotNet to measure execution time, memory allocation, and threading behavior.

• Ensures that asset indexing, loading, and retrieval are optimized for large datasets.

4. Edge Case Handling

• Ensures stability with:

  • Empty folders

  • Corrupt image files

  • Large-scale imports

Benchmarking

Performance is a key focus of LuxImport. The system is benchmarked to analyze indexing and retrieval efficiency.

1. Benchmark Strategy

• Uses BenchmarkDotNet to measure:

  • Execution time per operation.

  • Memory allocations and garbage collection pressure.

  • Threading efficiency and lock contention.

2. Benchmark Scenarios

• Initialization: Measures the time required to set up a new collection.

• Indexing: Evaluates performance when scanning and hashing assets.

• Database Operations: Tests manifest file read/write performance.

• Asset Loading: Benchmarks retrieval times for indexed images.

3. Sample Benchmark Results

Result is in microseconds (μs). You can find detailed benchmark results in the LuxImport.Benchmark/BenchmarkDotNet.Artifacts folder. The provided benchmark results are for reference only and may vary based on the system configuration. It has been tested on an Apple Silicon M2 chip on Parallels Desktop.

With 3 different collections, 50, 100, and 200 images, the benchmark results are as follows:

Go to the for more details.

The Standard Export Module

✨ Features

• Multi-Format Output Export photos in JPEG, PNG, BMP, GIF, WebP, AVIF, TIFF, and more.

• Flexible Export Destinations Choose between Hard Drive and Web export modes, each with tailored options.

• Custom File Naming Define filename patterns with dynamic tags like {name}, {date}, {counter}, and metadata fields. Preview filenames instantly before export.

• Conflict Handling Decide how existing files are managed: Overwrite, Rename, or Skip.

• Subfolder Support Automatically organize exports into subfolders for cleaner project structure.

• Advanced File Settings Adjust format, quality, color space (sRGB, etc.), and optional file size limits for precision control.

• Watermarking (Web Export) Add text watermarks with adjustable opacity for branding and content protection.

• Presets for Reuse Save and load export presets to streamline repetitive workflows.

• Real-Time Progress Feedback Track export progress, with the ability to pause or cancel tasks safely.

📂 How It Works

1. Select Destination Choose Hard Drive or Web export mode.

2. Configure Settings Set format, quality, naming pattern, subfolders, and watermark (if applicable).

3. Preview & Confirm View sample filenames and confirm settings before export.

4. Export Run the export with live progress tracking and conflict resolution.

📌 Coming Soon

• Batch Export Reports Generate logs and summaries of exported files for documentation.

• Enhanced Metadata Tokens More dynamic options for filename generation.

• Branding Templates Predefined watermark and naming schemes for professional delivery.

📄 License

Luxoria and all standard modules are licensed under the Apache 2.0 License. See the for details.

Source Code:

Overview

LuxExport is a modular export system integrated into the Luxoria ecosystem. It allows users to export collections of images in various formats with customizable file naming, export locations, and conflict handling strategies.

Features

Table of Contents