Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spezi Scheduler UI #17

Open
1 task done
PSchmiedmayer opened this issue Jul 30, 2023 · 0 comments · May be fixed by #44
Open
1 task done

Spezi Scheduler UI #17

PSchmiedmayer opened this issue Jul 30, 2023 · 0 comments · May be fixed by #44
Labels
enhancement New feature or request

Comments

@PSchmiedmayer
Copy link
Member

PSchmiedmayer commented Jul 30, 2023

Problem

The current scheduler module provides API-based functionality to define and use Tasks and Events.

Solution

The Scheduler Module should add a target that provides a simple UI for displaying tasks in an application. The views should have an automated mechanism to map tasks and events to UI representations.

A nice way to achieve this would be closures that get the context provided to return a custom view that is displayed in the event-related views. An alternative would be allowing task contexts to conform to a TaskRepresentation protocol that returns a view that can be injected into the view hierarchy when a task or related event is displayed.

Additional context

The UI in the Spezi Template Application can serve as a good way to get started with the UI components in the Scheduler module.
The initial functionality should be simple and can be extended in the future once we have a good basis in a reusable module.

Code of Conduct

  • I agree to follow this project's Code of Conduct and Contributing Guidelines
@PSchmiedmayer PSchmiedmayer added the enhancement New feature or request label Jul 30, 2023
@PSchmiedmayer PSchmiedmayer pinned this issue Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Backlog
1 participant