On Wednesday, March 27, 2013, Chris Geer wrote: > I'm struggling with the new JS API quite a bit while trying to integrate it > into my application. It's turning into a lot of trial and error about what > functions were renamed and what functions were removed or don't seem to > work. I like the new approach but I'm concerned that we've lost > capabilities and I'm not sure how we test for that.
I have seen a couple of things missing. > > My latest two struggles are: > - Registering custom popups: There used to be a method called > rave.registerPopup that would allow for a custom popup definition to be > added. That seems to have gone away and now the popups seem to be > registered privately. I'm not sure if just adding a popup as a new view is > good enough or not. > - Provider Initialization: We make big use of the initialization chain by > calling rave.registerOnProvidersInitizalizedHandler(). This method still > exists and looking at it, it seems to add the callback to an array. The one > thing I don't see when those callbacks are actually called. It used to be > called after the open social provider was complete. At the moment, those > callbacks are never triggered. > > It very well might be I'm just not understanding how things were > restructured, but if I'm having problems, I know other people will to. It's > almost like we need a migration document (especially to list methods that > no longer exist or have moved). This would be nice, but documentation on how to use the new API and in what scenarios would probably suffice. > > Chris >
