Hi Kavith, You can refer this post [1]<http://tanyamadurapperuma.blogspot.com/2013/12/inter-gadget-communication-with-wso2-ues.html>regarding pub-sub model in UES. But in this post both the publisher and subscriber are gadgets. AFAIU in your case publisher will not be a gadget and you will have to publish productID, productVersionId and productBuildId etc to the channel that the subscriber is listening to.
[1] http://tanyamadurapperuma.blogspot.com/2013/12/inter-gadget-communication-with-wso2-ues.html Thanks, Tanya. On Mon, Feb 17, 2014 at 8:26 AM, Ruchira Wageesha <[email protected]> wrote: > > On Mon, Feb 17, 2014 at 12:49 AM, Senaka Fernando <[email protected]> wrote: > >> Hi Ruchira, >> >> So, you pass the parameters into this page. And then, the javascript will >> use those (perhaps JS written in the header block I suppose) and >> communicate with gadgets? >> > or should the gadgets delay the loading, wait for the data to be available >> and display the updates after the page is loaded. Which is the model that >> works? >> > This is how I meant, > > - All gadgets in the dashboard will be loaded into their relevant > iframes when the page is being loaded. > - The JavaScript code we write will publish the data to those > gadgets(we might have to wait till iframes are loaded, not sure whether > pubsub librabry itself handle it properly) > - Gadgets will load the data from backends using the data passed and > draw the graphs > > >> Thanks, >> Senaka. >> >> >> On Sun, Feb 16, 2014 at 8:54 PM, Ruchira Wageesha <[email protected]>wrote: >> >>> Hi Kavith, >>> >>> I think, best option would be to use gadget pub-sub model. i.e. You >>> would have include a JavaScript code in your dashboard page, which gets the >>> project id etc. by parsing the url and publish to gadgets. Then, each >>> gadget will can receive the parameters by listening to the relevant channel >>> and load the data. >>> >>> /Ruchira >>> >>> >>> On Sun, Feb 16, 2014 at 11:10 AM, Senaka Fernando <[email protected]>wrote: >>> >>>> Hi Kavith, >>>> >>>> Particularly, the model should be such where you create a dashboard >>>> that could display stats for any project and you get a specific URL for >>>> each project instructing the dashboard what to load. >>>> >>>> As discussed with Ruchira et al, this should be possible to do. But, >>>> how this has to be done is not something well known AFAIU. >>>> >>>> Thanks, >>>> Senaka. >>>> >>>> >>>> On Sun, Feb 16, 2014 at 6:20 AM, Kavith Lokuhewage <[email protected]>wrote: >>>> >>>>> Hi, >>>>> >>>>> I am working on a QA Dashboard on UES [Please refer to the attached >>>>> screen-shot]. A similar dashboard is being built to view reports for git >>>>> commits status, test coverage status and other build status reports. >>>>> >>>>> These dash boards are linked to a Project Asset Management user >>>>> interface on Enterprise Store. When a user want to see above mentioned >>>>> dashboards for a particular build of a product, he should be able to see >>>>> it >>>>> by clicking a link on Project Asset management window on ES. >>>>> >>>>> We need to pass productID, productVersionId and productBuildId as >>>>> request parameters via the link. Is there way to forward these parameters >>>>> to micro sites. Or is there a better approach than this, to overcome this >>>>> problem? >>>>> >>>>> >>>>> Thanks. >>>>> >>>>> *Kavith Lokuhewage* >>>>> Software Engineer >>>>> WSO2 Inc. - http://wso2.com >>>>> lean . enterprise . middleware >>>>> Mobile - +9477-9-145-123 | +9471-455-6-401 >>>>> Linkedin <http://www.linkedin.com/pub/kavith-lokuhewage/49/473/419> >>>>> Twitter <https://twitter.com/KavithThiranga> >>>>> >>>> >>>> >>>> >>>> -- >>>> >>>> >>>> *[image: http://wso2.com] <http://wso2.com> Senaka Fernando* >>>> Senior Technical Lead; WSO2 Inc.; http://wso2.com >>>> >>>> >>>> >>>> * Member; Apache Software Foundation; http://apache.org >>>> <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1 >>>> 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*; >>>> >>>> >>>> *M: +94 77 322 1818 <%2B94%2077%20322%201818> Linked-In: >>>> http://linkedin.com/in/senakafernando >>>> <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware >>>> >>> >>> >>> >>> -- >>> >>> *Ruchira Wageesha**Associate Technical Lead* >>> *WSO2 Inc. - lean . enterprise . middleware | wso2.com >>> <http://wso2.com>* >>> >>> *email: [email protected] <[email protected]>, blog: >>> ruchirawageesha.blogspot.com <http://ruchirawageesha.blogspot.com>, >>> mobile: +94 77 5493444 <%2B94%2077%205493444>* >>> >> >> >> >> -- >> >> >> *[image: http://wso2.com] <http://wso2.com> Senaka Fernando* >> Senior Technical Lead; WSO2 Inc.; http://wso2.com >> >> >> >> * Member; Apache Software Foundation; http://apache.org >> <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1 >> 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*; >> >> >> *M: +94 77 322 1818 <%2B94%2077%20322%201818> Linked-In: >> http://linkedin.com/in/senakafernando >> <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware >> > > > > -- > > *Ruchira Wageesha**Associate Technical Lead* > *WSO2 Inc. - lean . enterprise . middleware | wso2.com <http://wso2.com>* > > *email: [email protected] <[email protected]>, blog: > ruchirawageesha.blogspot.com <http://ruchirawageesha.blogspot.com>, > mobile: +94 77 5493444 <%2B94%2077%205493444>* > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Tanya Madurapperuma Software Engineer, WSO2 Inc. : wso2.com Mobile : +94718184439 Blog : http://tanyamadurapperuma.blogspot.com
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
