The primary aim of this thread will be improvement of the initial project plan linked above, including identification of functionalities needed in the current system and various issues which needs to be addressed.
@yehster Yep I understand! Note that I’m working on reworking this proposal for my project plan. My focus is on identifying and porting over all the current functionalities the calendar. Safe to say that I won’t be doing file by file replication of everything like originally stated in the proposal above
@teryhill Yep, I’m planning on using FullCalendar. It has great documentation, is easy to use, and based on a cursory look its event hooks would be able to handle most of the current functionalities easily.
I looked at just about every option out there, and as an extensible starting point, I think that FullCalendar is by far the best of the bunch.
@yehster I am of the opinion that the existing tables re: the external components that touch them, are less difficult to adapt to a new structure than creating a new structure for the FullCalendar base. The components of PN Calendar we actually used were not very extensive. That said, I was under the impression that FullCalendar just used a json file named “events” or something.