-
Notifications
You must be signed in to change notification settings - Fork 28
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
Extra scheduler views #64
Comments
This feature is not planned at the moment as I am going to be getting started with integrating this into MudBlazor and limiting support for this repo (it'll stay up and I'll continue to build in minimal features/bug fixes & accepting PRs). |
Ah that's great news! I was already wondering of you would be open to the idea of integrating this repo into MudBlazor. Do you have any idea when the first version will be available in MudBlazor? |
Not a clue! Just getting started on it, haven't gotten too much detail from the Mud team. |
Having this with multiple views in MudBlazor would be great. |
It's great that you want to integrate the great library directly into Mudblazor. Do you know when it will be ready? |
Hi @valincius , Cheers |
Hi @Int32Overflow and @AFAde sorry I do not have good news. I did not get very far and did not have the capacity to work on this, so I've dropped the MudBlazor integration. There are some others in the Mud Discord who are building something similar, I do not know the state of those projects, they are not officially supported at the moment. If you want to create your own implementation using Mud, please feel free to take whatever you need from here. |
Hi @valincius , Cheers |
As I stumbled upon you neat component, I noticed there is only one view available at the moment.
Other scheduler components from suites like syncfusion, telerik, devexpress etc have day, week, month views with appointment templates to customize their content and appearance.
Are you planning on adding those in the (near) future or are you open for PR's for example?
The text was updated successfully, but these errors were encountered: