Hi Vidura,
Could you please elaborate more on why you are not going to use existing
UES pub/sub mechanism? What are the shortcomings it has and how do you plan
to overcome them with your new implementation?
Thanks,
Dunith
On Tue, Feb 17, 2015 at 1:55 PM, Vidura Mudalige vidu...@wso2.com wrote:
Hi Gayan,
Yes it is correct that current pub/sub implementation is quite flexible for
developers. But our main focus is to improve dashboard designer for
non-developers.
Using timestamp is okay for this example. But there can be various
scenarios that we have to use different kind of data such
Hi Tanya,
If we are to directly use gadgets pub/sub support as it is, then we should
know publisher's channels, data format etc. in advance. Hence, we will
identify widely used formats and adhere to them, which will be pluggable.
As an example, let's say we need to have a widget/gadget to select
Hi,
On Tue, Feb 17, 2015 at 10:05 AM, Vidura Mudalige vidu...@wso2.com wrote:
HI all,
We are planning to improve the dashboard of UES to support bootstrap and
pub/sub.
What are the improvements that you are planning for pub/sub? Because UES
already have pub/sub support.
Current
Hi Vidura,
+1 for flexible UI layouts. Most of the times I have walked away from the
gridster layout when developing dashboards since it is not that much
flexible. However I am ok with the current pub/sub implementation. It is
quite flexible.
On Tue, Feb 17, 2015 at 11:52 AM, Vidura Mudalige
