[
https://issues.apache.org/jira/browse/WAVE-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886987#comment-13886987
]
Zachary “Gamer_Z.” Yaro commented on WAVE-390:
----------------------------------------------
I am still interested (from the WEG side of things). Is there anything I can
do to help without knowledge of GWT or the WIAB GWT client?
> Wave Extensions Gallery integration
> -----------------------------------
>
> Key: WAVE-390
> URL: https://issues.apache.org/jira/browse/WAVE-390
> Project: Wave
> Issue Type: Improvement
> Components: Web Client
> Reporter: Zachary “Gamer_Z.” Yaro
> Assignee: Ali Lown
> Priority: Minor
> Labels: extensions, gadgets
>
> A little over a month ago, I announced the first release of the Wave
> Extensions Gallery search API (wavygallery.appspot.com/docs/api/v0/search).
> Not long after that, I released the WEG Loader for Rizzoma 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.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)