Hi Sebastian I try to let open as much as I think the user can customize, but you are right, it is hard to get the full picture of all possible use-cases... But when I think it can be dangerous, error prone or confusing, I prefer to restrict... (I may sometime be a little bit strict, however a simple request and I unlock if I see no drawbacks...)
Looking at the code again, even #newRequestHandler is more designed to be for internal purpose, I will leave it protected (as you demonstrate a possible use-case earlier! ;)) Thanks & best regards, Sebastien. On Sat, Sep 28, 2013 at 12:04 AM, seba.wag...@gmail.com < seba.wag...@gmail.com> wrote: > Hi Sebastien, > > I can check that. But I don't think we need it to be open. > > We basically reworked all of our code so that there is no more requirement > to display the Calendar in a different timezone then the timezone of the > browser/OS. > > However from an integration point of view I would be very careful on how > much you want to restrict the usage of your API. Having only one designed > way to use is good, but it is quite hard to really have an overview about > all available use-cases to judge what is the best scenario for an API to > use. The more people adapt your libary, the bigger the success, the bigger > the chances you find more active contributor that improve the quality and > features :) > > Thanks for heads up! > Sebastian >
