Zachary, I will take a look at implemeting this today.
Based on a cursory glance. It looks like it would be useful to be able to pass a 'type' to the search request so that it returned only gadgets or robots, but not a mix of both, which is what it sounds like it would do currently. Ali On 30 Apr 2013 04:59, "Zachary “Gamer_Z.” Yaro" <zmy...@gmail.com> wrote: > A little over a month ago, I announced the first release of the Wave > Extensions Gallery search > API<http://wavygallery.appspot.com/docs/api/v0/search>. > Not long after that, I released the WEG Loader for > Rizzoma< > https://chrome.google.com/webstore/detail/mlojdiioofflgaofeccckonhekefgopa > > > Chrome > extension, which used the WEG search API to put WEG gadgets in Rizzoma's > gadgets menu. It would be great to see WEG gadgets also be searchable from > the WIAB gadgets dialog. > > WIAB already has a gadget searching UI. It would require essentially no UI > changes to implement this. All that would change is what happens with the > search query behind the scenes. Instead of searching within a hard-coded > JSON file, send a request to the WEG search API and parse the JSON > response. > > The advantages of using the WEG API over the current method are a) the > gadget URLs, icons, and metadata will always be up-to-date, and b) WIAB > instances will not all need to store their own hard-coded gadget lists. > > Unfortunately, I am not proficient enough with GWT or familiar enough with > the WIAB client to implement this myself. Are any WIAB developers able and > willing to attempt this? Feel free to contact me with any ways I can > modify the WEG or its APIs to make this easier for you. > > —Zachary “Gamer_Z.” Yaro > > P.S. I also added an entry for this feature request in the Apache Wave > JIRA<https://issues.apache.org/jira/browse/WAVE-390> > . >
