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

Scheduler Roadmap #9

Open
7 of 12 tasks
HaithemMosbahi opened this issue Jul 19, 2017 · 10 comments
Open
7 of 12 tasks

Scheduler Roadmap #9

HaithemMosbahi opened this issue Jul 19, 2017 · 10 comments

Comments

@HaithemMosbahi
Copy link
Owner

HaithemMosbahi commented Jul 19, 2017

The aim of this ticket is to prepare a todo list of the features that are going to be implemented in future releases.

Scheduler V 1.x

  • A declarative web component that wraps the fullCalendar library

  • Customize and configure the scheduler using properties

  • Dispatch events as they occur ( click on event, click on day, change view , etc )

  • Organize scheduler's events using categories

    • Show / Hide categories in the bottom of the scheduler

    • Show / Hide events when selecting / deselecting a category

    • Coloration of events based on categories

  • Add custom properties API to style the scheduler

Scheduler V 2.x

  • Add default view, create and edit templates

  • Support overriding view, create and edit templates

  • Extensible Themes

  • Add the ability to override categories template.

@HaithemMosbahi
Copy link
Owner Author

Hey man @rodzzlessa24 as we have discussed, I've just added the current state of scheduler's roadmap. I'm looking forward to your feedback. Feel free to suggest new features.
Actually, I've been thinking of keeping the 1.x version simple with only basic functionalities and moving the more advanced features like adding view and edit templates to version 2.x

@threeaccents
Copy link
Contributor

This is great man. I can get started adding the default views.

@HaithemMosbahi
Copy link
Owner Author

HaithemMosbahi commented Jul 20, 2017

Yes that would be great. I've already added view and edit element ( only element's structure ).
However, I've been thinking of moving these elements to a new branch.
As described above, I think of keeping the default views to version 2 and release a new minor version soon.
So you can start working on this feature in new branch.

@HaithemMosbahi
Copy link
Owner Author

Do you have any other features in your mind ?

@threeaccents
Copy link
Contributor

I was actually just thinking on working a bit on the new app to see if there is anything missing. One thing that we can maybe think about is not including the fullcalendar css theme by default.

@HaithemMosbahi
Copy link
Owner Author

HaithemMosbahi commented Jul 20, 2017

Yes, I agree with you. Then, we can support one or more additional themes like Default theme, Material theme, etc.
A new feature has been added : Extensible Themes

@HaithemMosbahi
Copy link
Owner Author

hey man I've just created a new branch scheduler-v2, you can use it in the development of the default views feature

@HaithemMosbahi
Copy link
Owner Author

HaithemMosbahi commented Jul 20, 2017

I'm looking forward to release a new version by the end of the week that will include organizing events using categories.
Also, we should consider improving element's testing and documentation.

@HaithemMosbahi
Copy link
Owner Author

HaithemMosbahi commented Jul 22, 2017

hey @rodzzlessa24, I've created a team on slack for this component. I think it's better to chat and discuss ideas there. I've sent you an invitation, here is the url : https://scheduler-component.slack.com/
Upadte : Well I've changed my mind and I've decided to go with gitter over slack, I think it's more suitable to github based project. I've sent you an invitation as well ^^

@threeaccents
Copy link
Contributor

@HaithemMosbahi Hey man I don't think I got the gitter invite. I've been writing to you on Slack

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants