Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

JavaScript

Fullcalendar vs WDCalendar

I want to develop a really advanced api based on javascript calendar. But I'm stucked if I should go for FullCalendar(http://fullcalendar.io/) or WDCalendar(http://jquerylabs.com/wdcalendar-jquery-plugin-html/). Can anyone give me advices, or pro and cons about them so I can make a good choice? My API will have Database integration, ajax manipulation, angular-js usage and with an user interface similar to Google Calendar. Thanks for helping me.

1 Answer

No one can really tell you what to use, it's best to decide for yourself. Even with the information you've provided, it's hard for us to really understand what your projects is about.

That being said, there are several things you can look into.

Whenever you get stuck choosing one of the core technologies for a project, it's really good to explore the ecosystem around your choices. This includes (but isn't limited to) the age of a project, popularity, contributions, updates, documentation, support and so on.

A quick glance at a Google search can help you decide.

In this case, FullCalendar seems to be the way to go. It's well-documented and actively developed (last commit was 17 days ago at the time of writing this reply). People also seem to use it a lot (note the number of stars on GitHub).

wdCalendar's documentation seems sparse compared to FullCalendar's. Information on development is hard to find, and the interface looks a bit dated.

Of course, this is the way I decide which technologies to pick, it may not work for you.

In the end, if you try to keep your code modular, it won't be too hard to replace one part if it doesn't work out for you.

Thanks for the advice. Since I'm new on developing, sometimes I have a hard time deciding between technologies. :)