You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: