[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wsf-javascript-user
Subject:    Re: [User] New dashboard and gadget store architecture for GS 2.0
From:       Nuwan Bandara <nuwan () wso2 ! com>
Date:       2012-09-19 7:39:58
Message-ID: CANbifZ4JSBWbSWhMaVsmXfwfCf=GHUUSOkTzQw8vJeeju+vdHg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/related)]

[Attachment #4 (multipart/alternative)]


Yes, we can have multiple dashboards, I am still thinking if we clone the
default dashboard to a new page and make it the second dashboard, or
to facilitate this logically.

If we clone it, the two dashboards will have two separate pages, if we do
this logically, its one page and facilitate multiple dashboards.

Any thoughts?

Regards,
/Nuwan

On Wed, Sep 19, 2012 at 12:30 PM, Tharindu Mathew <tharindu@wso2.com> wrote:

> Do we have multiple dashboards?... we have 1 and are writing another 3...
>
>
> On Wed, Sep 19, 2012 at 11:58 AM, Nuwan Bandara <nuwan@wso2.com> wrote:
>
>> Hi folks,
>>
>> With the need for a common dashboard and a store, and makeing it a part
>> of GS2.0, we came up with the following architecture. There are few key
>> ideas stated below.
>>
>>    - The gadget store and the dashboard will have a API module and a UI
>>    module.
>>       - These two modules can act independently, hence can be installed
>>       for any product separately.
>>       - GS 2.0 will by default ship both API module and the UI module,
>>       providing an api as well as the UI.
>>       - Products that need a dashboard and a gadget repository shipped
>>       by default (like BAM2.0) can also have both these modules.
>>       - Products that does not need to ship a UI component can only
>>       package the API module, so the common store or the dashboard can poll the
>>       gadget metadata specific to that product.
>>       - Gadgets specific to each product will sit in that product and
>>       will have a URL that it can be accessed. (i.e If there is a gadget written
>>       for ESB, that gadget's url will be http://
>>       {usbhost)/store/gadgets/foo.xml)
>>       - Metadata for a particular gadget will be store in the registry.
>>       a metadata object will look like,
>>
>> {
>>
>>  "id":1,
>>
>>  "name":"foo Gadget",
>>
>> "description":"this is a great gadget",
>>
>> "author":"doe",
>>
>> "url":"http://bam.com/store/gadgets/foo/foo.xml",
>>
>> "thumb":"http://bam.com/store/gadgets/foo/thumb.png",
>>
>> "prefs":{},
>>
>> }
>>
>> To clarify the architecture, please find the attached diagrams. If there
>> are concerns, and more specific requirements that we have missed, please do
>> point out.
>>
>>
>> [image: Inline image 3]-
>>
>>
>> [image: Inline image 4]
>>
>> *Thanks & Regards,
>>
>> Nuwan Bandara
>> Associate Technical Lead & Member, MC, Development Technologies
>> WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
>> blog : http://nuwanbando.com; email: nuwan@wso2.com; phone: +94 11 763
>> 9629
>> *
>> <http://www.nuwanbando.com/>
>>
>
>
>
> --
> Regards,
>
> Tharindu
>
> blog: http://mackiemathew.com/
> M: +94777759908
>
>


-- 
*Thanks & Regards,

Nuwan Bandara
Associate Technical Lead & Member, MC, Development Technologies
WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
blog : http://nuwanbando.com; email: nuwan@wso2.com; phone: +94 11 763 9629
*
<http://www.nuwanbando.com/>

[Attachment #7 (text/html)]

Yes, we can have multiple dashboards, I am still thinking if we clone the default \
dashboard to a new page and make it the second dashboard, or to facilitate this \
logically. <div><br></div><div>If we clone it, the two dashboards will have two \
separate pages, if we do this logically, its one page and facilitate multiple \
dashboards.</div>

<div><br></div><div>Any \
thoughts?</div><div><br></div><div>Regards,</div><div>/Nuwan<br><br><div \
class="gmail_quote">On Wed, Sep 19, 2012 at 12:30 PM, Tharindu Mathew <span \
dir="ltr">&lt;<a href="mailto:tharindu@wso2.com" \
target="_blank">tharindu@wso2.com</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">Do we have multiple dashboards?... we have 1 and are writing \
another 3...<div class="HOEnZb"><div class="h5"><br><br><div class="gmail_quote">

On Wed, Sep 19, 2012 at 11:58 AM, Nuwan Bandara <span dir="ltr">&lt;<a \
href="mailto:nuwan@wso2.com" target="_blank">nuwan@wso2.com</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">Hi folks,<div><br></div><div>With the need for a common \
dashboard and a store, and makeing it a part of GS2.0, we came up with the following \
architecture. There are few key ideas stated below.</div>



<div><ul><li>The gadget store and the dashboard will have a API module and a UI \
module.</li>

<ul><li>These two modules can act independently, hence can be installed for any \
product separately.</li><li>GS 2.0 will by default ship both API module and the UI \
module, providing an api as well as the UI.</li><li>Products that need a dashboard \
and a gadget repository shipped by default (like BAM2.0) can also have both these \
modules. </li>





<li>Products that does not need to ship a UI component can only package the API \
module, so the common store or the dashboard can poll the gadget metadata specific to \
that product.</li><li>Gadgets specific to each product will sit in that product and \
will have a URL that it can be accessed. (i.e If there is a gadget written for ESB, \
that gadget&#39;s url will be <font face="courier new, \
monospace">http://{usbhost)/store/gadgets/foo.xml</font>)</li>





<li>Metadata for a particular gadget will be store in the registry. a metadata object \
will look like,</li></ul></ul></div><blockquote style="margin:0 0 0 \
40px;border:none;padding:0px"><blockquote style="margin:0 0 0 \
40px;border:none;padding:0px">





<blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><div><div><font \
face="courier new, monospace">{</font></div></div></div></blockquote></blockquote><blockquote \
style="margin:0 0 0 40px;border:none;padding:0px">





<blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><div><div><font \
face="courier new, monospace"><span \
style="white-space:pre-wrap">	</span>&quot;id&quot;:1,</font></div></div></div></blockquote>


</blockquote><blockquote style="margin:0 0 0 \
40px;border:none;padding:0px"><blockquote style="margin:0 0 0 \
40px;border:none;padding:0px"><div><div><div><font face="courier new, \
monospace"><span style="white-space:pre-wrap">	</span>&quot;name&quot;:&quot;foo \
Gadget&quot;,</font></div>





</div></div></blockquote></blockquote><blockquote style="margin:0 0 0 \
40px;border:none;padding:0px"><blockquote style="margin:0 0 0 \
40px;border:none;padding:0px"><div><div><div><font face="courier new, \
monospace"><span style="white-space:pre-wrap">	</span>&quot;description&quot;:&quot;this \
is a great gadget&quot;,</font></div>





</div></div></blockquote></blockquote><blockquote style="margin:0 0 0 \
40px;border:none;padding:0px"><blockquote style="margin:0 0 0 \
40px;border:none;padding:0px"><div><div><div><font face="courier new, \
monospace"><span style="white-space:pre-wrap">	</span>&quot;author&quot;:&quot;doe&quot;,</font></div>






</div></div></blockquote></blockquote><blockquote style="margin:0 0 0 \
40px;border:none;padding:0px"><blockquote style="margin:0 0 0 \
40px;border:none;padding:0px"><div><div><div><font face="courier new, \
monospace"><span style="white-space:pre-wrap">	</span>&quot;url&quot;:&quot;<a \
href="http://bam.com/store/gadgets/foo/foo.xml" \
target="_blank">http://bam.com/store/gadgets/foo/foo.xml</a>&quot;,</font></div>





</div></div></blockquote></blockquote><blockquote style="margin:0 0 0 \
40px;border:none;padding:0px"><blockquote style="margin:0 0 0 \
40px;border:none;padding:0px"><div><div><div><font face="courier new, \
monospace"><span style="white-space:pre-wrap">	</span>&quot;thumb&quot;:&quot;<a \
href="http://bam.com/store/gadgets/foo/thumb.png" \
target="_blank">http://bam.com/store/gadgets/foo/thumb.png</a>&quot;,</font></div>





</div></div></blockquote></blockquote><blockquote style="margin:0 0 0 \
40px;border:none;padding:0px"><blockquote style="margin:0 0 0 \
40px;border:none;padding:0px"><div><div><div><font face="courier new, \
monospace"><span style="white-space:pre-wrap">	</span>&quot;prefs&quot;:{},</font></div>






</div></div></blockquote></blockquote><blockquote style="margin:0 0 0 \
40px;border:none;padding:0px"><blockquote style="margin:0 0 0 \
40px;border:none;padding:0px"><div><div><div><font face="courier new, \
monospace">}</font></div>





</div></div><div><font face="courier new, \
monospace"><br></font></div></blockquote></blockquote></blockquote><font face="arial, \
helvetica, sans-serif">To clarify the architecture, please find the attached \
diagrams. If there are concerns, and more specific requirements that we have missed, \
please do point out.</font><div>





<font face="arial, helvetica, sans-serif"><br></font></div><div><font face="arial, \
helvetica, sans-serif"><br></font></div><div><div><div><img \
src="cid:ii_139dd335c11aa0e7" alt="Inline image 3">- </div><div><br></div><div>





<br></div><div><img src="cid:ii_139dd34a15772f4f" alt="Inline image \
4"><br></div><div><br></div><font face="&#39;times new roman&#39;, serif"><i>Thanks \
&amp; Regards,<br><br><b>Nuwan Bandara</b><br>Associate Technical Lead &amp; Member, \
MC, Development Technologies<br>





WSO2 Inc. - lean . enterprise . middleware |  <a href="http://wso2.com" \
target="_blank">http://wso2.com</a> <br>blog : <a href="http://nuwanbando.com" \
target="_blank">http://nuwanbando.com</a>; email: <a href="mailto:nuwan@wso2.com" \
target="_blank">nuwan@wso2.com</a>; phone: <a href="tel:%2B94%2011%20763%209629" \
value="+94117639629" target="_blank">+94 11 763 9629</a><br>





</i></font><br><a href="http://www.nuwanbando.com/" target="_blank"></a><br>
</div></div>
</blockquote></div><br><br clear="all"><div><br></div></div></div><span \
class="HOEnZb"><font color="#888888">-- \
<br>Regards,<br><br>Tharindu<br><div><br></div><div>blog: <a \
href="http://mackiemathew.com/" target="_blank">http://mackiemathew.com/</a></div>

<div>M: <a href="tel:%2B94777759908" value="+94777759908" \
target="_blank">+94777759908</a></div>

<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><font \
face="&#39;times new roman&#39;, serif"><i>Thanks &amp; Regards,<br><br><b>Nuwan \
Bandara</b><br>Associate Technical Lead &amp; Member, MC, Development \
Technologies<br>

WSO2 Inc. - lean . enterprise . middleware |  <a href="http://wso2.com" \
target="_blank">http://wso2.com</a> <br>blog : <a href="http://nuwanbando.com" \
target="_blank">http://nuwanbando.com</a>; email: <a href="mailto:nuwan@wso2.com" \
target="_blank">nuwan@wso2.com</a>; phone: +94 11 763 9629<br>

</i></font><br><a href="http://www.nuwanbando.com/" target="_blank"></a><br>
</div>

--f46d040711ed93943404ca08f4a2--


["single.png" (image/png)]
["commondashboardv2.png" (image/png)]

_______________________________________________
User mailing list
User@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/user


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic