Hi Dunith,

Really nice and clean UI. Is it possible to get a preview of a data set in
a table format or any sort of a view, once we select the data source. If we
have a preview,  it will be easy to get an idea about what kind of graph we
need. Again, it would be great if we have a 4th wizard step, that we can
select whether this dashboard is a private or public or which roles can see
this dashboard.

Regards,
Gihan

On Thu, Jan 29, 2015 at 7:41 AM, Dunith Dhanushka <[email protected]> wrote:

> Hi all,
>
> Myself (BAM) and Damith(CEP) working on a wizard for generating a generic
> configurable gadget. Gadgets will be implemented using D3.js and this
> feature will be shared across both BAM and CEP. As the first step, we have
> come up with mock HTML pages to represent the flow of the wizard. Please
> find the attached screenshots for that.
>
> A meeting was organized to demonstrate the wizard functionality. Please
> find the meeting notes below.
>
> Participants: Sanjiva, Srinath, Jaminda, Anjana, Suho, Chanaka, Ruchira,
> Dunith, Damith
>
> *Meeting Notes: *
>
> - Gadget generation wizard is a good approach. But at the moment the most
> important feature is the dashboard/visualization engine which can render a
> gadget from a handcoded JSON file.
>
> - The gadget that will be generated from current wizard is coupled with
> data. It should not be like that and user should be able to view a single
> dataset in many forms. That means one dataset can be represented by many
> chart types such as bar,pie, scatter chart etc.
>
> - A well known format should be defined to store the generated gadget.
>
> - Once the gadget is generated, it can be stored in ES by invoking ES
> publisher API. This where the Store concept comes into the play. By this
> way, users will be able to add pre built gadgets from the store and do
> additional customizations. (Needs further discussion)
>
> - There should be a way to store user preferences for a given gadget. This
> needs to be done in a way that gadget should store preferences for multiple
> users (Requires further discussion)
>
> - Dashboard implementation should be started in parallel as well. First
> version of that will be a HTML/JS application which communicates with
> backend via REST API.
>
>
> *Action items: *
>
> - Add more D3 chart types to the wizard by merging a project done by
> trainees. This should be immediately started and code should be refactored
> and reviewed. (In progress by Dunith​​​​​​​​​​)
> - Define a format to store the generated gadget.
> - Start the dashboard implementation.
>
> @Damith, Please add anything I missed here.
>
> Regards,
> Dunith
>
> ​​​​​​​​​​
>
> On Tue, Jan 6, 2015 at 8:53 PM, Malith Dhanushka <[email protected]> wrote:
>
>>
>>
>> On Sun, Dec 14, 2014 at 11:46 PM, Anjana Fernando <[email protected]>
>> wrote:
>>
>>> Hi,
>>>
>>> I guess, for BAM 3.0, this can be the base for our eventual KPI
>>> implementation as well. We will just need some additional functionality to
>>> provide some limits to the data/visualizations we are having, and to show
>>> it in an appropriate way, and to trigger alerts etc.. Looking forward to
>>> checking out the initial implementation of this, so probably the BAM team
>>> can enhance it with the other required features.
>>>
>>
>> Obviously, we can implement alerting on top of this. For example a user
>> can define a threshold level on a chart(graphically) and define what kind
>> of alert he needs. This will be a key part in effort of BAM KPI
>> implementation.
>>
>> Thanks,
>> Malith
>>
>>
>>> Cheers,
>>> Anjana.
>>>
>>> On Mon, Dec 8, 2014 at 7:42 PM, Srinath Perera <[email protected]> wrote:
>>>>
>>>> Currently to visualize the data, users have to write their own gadgets.
>>>> If a advanced user this is OK, but not for all. Specially, things like
>>>> drill downs need complicated planning.
>>>>
>>>> I believe it is possible to start with data in tabular form, and write
>>>> a generic Gadget that let user configure and create his own data chart with
>>>> filters and drill downs.
>>>>
>>>> Chart could look like following ( some of the controls can be hidden
>>>> under configure button)
>>>>
>>>> ​
>>>> Lets work though an example.
>>>>
>>>> 1) Key idea is that we load data to the Gadget as a table (always).
>>>> Following can be a example data.
>>>>     *Country* *Year* *GDP* *Population* *LifeExpect*  Sri Lanka 2004 20
>>>> 19435000 73  Sri Lanka 2005 24 19644000 73  Sri Lanka 2006 28 19858000
>>>> 73  Sri Lanka 2007 32 20039000 73
>>>> 2) When Gadget is loaded, it shows the data as a table. User can select
>>>> and add a data type and fields.  Following are some example.
>>>>
>>>>    1. Line - two Numerical  fields
>>>>    2. Bar - one numerical, one categorical field
>>>>    3. Scatter - two numerical fields
>>>>    4. Map - Location field + categorical or numerical field
>>>>    5. Graph - two categorical or string fields that provide links
>>>>
>>>>
>>>> 3) Let user add more information to the chart using other fields in the
>>>> table
>>>>
>>>>    1. Add  color (Categorical field) or shade (numerical field) to the
>>>>    plot (e.g. Use different color for each country)
>>>>    2. Point Size - Numerical field (e.g. Adjust the point size in the
>>>>    scatter plot according to the population)
>>>>    3. Label - any field
>>>>
>>>> 4) Then he can add filters based on a variable. Then the chart will
>>>> have sliders (for numerical data) and tick buttons (for categorical data).
>>>> When those sliders are changed they will change the chart.
>>>>
>>>> 5) Final step is define drill downs. Drill downs are done using two
>>>> columns in the table that has hierarchical relationships. (e.g. Country and
>>>> State fields, Year and month fields) . We need users to select two of those
>>>> fields and tell us about relationships and then we can code the support of
>>>> drill downs.
>>>>
>>>> When above steps are done, user save configs and save it in the DataViz
>>>> store as a visualisation, so others can pull it and use it.
>>>>
>>>> This will not cover all cases, but IMO it will cover 80% and also a
>>>> very good tool for demos etc.
>>>>
>>>> Please comment
>>>>
>>>> --Srinath
>>>>
>>>>
>>>>
>>>> --
>>>> ============================
>>>> Blog: http://srinathsview.blogspot.com twitter:@srinath_perera
>>>> Site: http://people.apache.org/~hemapani/
>>>> Photos: http://www.flickr.com/photos/hemapani/
>>>> Phone: 0772360902
>>>>
>>>
>>>
>>> --
>>> *Anjana Fernando*
>>> Senior Technical Lead
>>> WSO2 Inc. | http://wso2.com
>>> lean . enterprise . middleware
>>>
>>> _______________________________________________
>>> Architecture mailing list
>>> [email protected]
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Malith Dhanushka
>> Software Engineer - Data Technologies
>> *WSO2, Inc. : wso2.com <http://wso2.com/>*
>> *Mobile*          : +94 716 506 693
>>
>> _______________________________________________
>> Architecture mailing list
>> [email protected]
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Regards,
>
> Dunith Dhanushka,
> Senior Software Engineer - BAM,
> WSO2 Inc,
>
> Mobile - +94 71 8615744
> Blog - dunithd.wordpress.com <http://blog.dunith.com>
> Twitter - @dunithd <http://twitter.com/dunithd>
>
> _______________________________________________
> Architecture mailing list
> [email protected]
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
W.G. Gihan Anuruddha
Senior Software Engineer | WSO2, Inc.
M: +94772272595
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to