Re: [Dev] [Announce] [Architecture] WSO2 Dashboard Server 2.1.0-Alpha Released!

[Nisala Nanayakkara]

Hi all,

I have scheduled a meeting on Wednesday afternoon to discuss about this
matter.

Thanks,
Nisala

On Mon, Aug 22, 2016 at 10:52 AM, Sinthuja Ragendran 
wrote:

> Hi Susinda,
>
> On Mon, Aug 22, 2016 at 10:16 AM, Susinda Perera  wrote:
>
>>
>>
>> On Sun, Aug 21, 2016 at 5:06 PM, Sinthuja Ragendran 
>> wrote:
>>
>>> Hi Nisala,
>>>
>>> So lets create a new repo for our new maven plugin, and lets include
>>> source there as per Susinda.
>>>
>>> @Susinda,
>>> Can you please elaborate bit more with what is the expected outcome when
>>> DevS based tooling using this maven plugin for DS? Because in the context,
>>> DS it self is a tool to create dashboard, gadgets, etc, therefore we don't
>>> intend to provide that sort of functionality with DevS. Therefore IMO we
>>> can maximum provide xml, js, css, jag file editors and lets them to create
>>> the structure of Capp from DevS. IMO creating such extension support will
>>> have considerable effort.
>>>
>>
>> Hi Sinthuja
>> Just had a chat with Nisala,
>> Expected outcome of DevS tooling was to make the developer's life easy on
>> creating dashboards, gadgets, layouts an themes. We have in built support
>> coming from eclipse for xml, html, css etc and we had jaggery editor with
>> code completion features. So I believe we can integrate these bits and
>> pieces and provide a IDE based tooling. As all developers are not command
>> line developers, I believe providing this kind of tooling would be useful
>> for general users.
>> As you already have maven build (packaging) tool and Capp tool for the
>> same, my suggestion is to introduce arch-type, then we can reuse use of
>> same arch-type and maven plugins to create the eclipse IDE plugin. So at
>> the end of the day we will have both command line and IDE based tooling.
>> WDYT?
>>
>
> Basically IMO IDE support is needed for creating custom gadgets and custom
> layouts. But the other parts such as creating dashboards, creating pages
> with default layouts, integrating gadgets into the dashboard pages, etc are
> provided from DS itself, and it's just drag and drop. And hence I don't
> think we need to provide same set of functionality which is already covered
> in DS, rather we need to focus on the point where users could create custom
> gadgets, and layouts which is the dev effort for the users in the context
> of DS. I don't think we can provide such DevS support feature for this
> release given the short time frame now.
>
> But anyhow lets have a discussion on this, come to our plan so that we can
> execute this on the future releases. @Nisala, please schedule a meeting
> Wednesday after noon or Thursday.
>
> Thanks,
> Sinthuja.
>
>
>> Thanks
>> Susinda
>>
>>
>>
>>
>>
>>>
>>> Thanks,
>>> Sinthuja.
>>>
>>> On Fri, Aug 19, 2016 at 5:24 PM, Nisala Nanayakkara 
>>> wrote:
>>>
 Hi,

 Thanks for prompt reply. I will arrange a meeting to discuss this
 matter.

 Thanks,
 Nisala

 On Fri, Aug 19, 2016 at 10:52 AM, Susinda Perera 
 wrote:

> Hi Nisala
>
> We may need to create a new repo and host these maven plugins. As an
> example esb uses maven-tooling-esb[1] and bps uses maven-tooling-bps[2] to
> maintain the maven plugins. As we already have the maven plugins i think 
> we
> can easily build the DevStudio based tooling with using these plugins.
> Please arrange a time to discuss this.
>
> [1] - https://github.com/wso2/maven-tooling-esb
> [2] - https://github.com/wso2/maven-tooling-bps
>
>
>
> On Thu, Aug 18, 2016 at 6:45 PM, Nisala Nanayakkara 
> wrote:
>
>> Hi,
>>
>> I have implemented maven - plugins for each artifacts in WSO2
>> Dashboard Server. So there are four maven - plugins for
>> dashboards,gadgets,layouts and themes which can be used to generate a CAR
>> file consisting with these artifacts. But we are not very much clear 
>> about
>> where we have to maintain these maven - plugins. Is it better to keep it
>> within our carbon-dashboards repository ? Or is it better to maintain 
>> these
>> as a separate repository.
>>
>> @DevStudioTeam : Can you provide recommended way of maintaining these
>> maven-plugins ?
>>
>> Thanks,
>> Nisala
>>
>> On Mon, Aug 15, 2016 at 10:51 AM, Susinda Perera 
>> wrote:
>>
>>> Do we have tooling support for this new release, like
>>> create/edit/deploy gadgets/dashboards etc. If not shall we add this to
>>> roadmap. DevS team will be able to help on this task.
>>>
>>> Thanks
>>> Susinda
>>>
>>> On Fri, Aug 12, 2016 at 8:23 PM, Megala Uthayakumar >> > wrote:
>>>
 WSO2 Dashboard Server 2.1.0-Alpha Released!

 WSO2 Dashboard Server team is pleased to announce the release of

Re: [Dev] [Announce] [Architecture] WSO2 Dashboard Server 2.1.0-Alpha Released!

[Sinthuja Ragendran]

Hi Susinda,

On Mon, Aug 22, 2016 at 10:16 AM, Susinda Perera  wrote:

>
>
> On Sun, Aug 21, 2016 at 5:06 PM, Sinthuja Ragendran 
> wrote:
>
>> Hi Nisala,
>>
>> So lets create a new repo for our new maven plugin, and lets include
>> source there as per Susinda.
>>
>> @Susinda,
>> Can you please elaborate bit more with what is the expected outcome when
>> DevS based tooling using this maven plugin for DS? Because in the context,
>> DS it self is a tool to create dashboard, gadgets, etc, therefore we don't
>> intend to provide that sort of functionality with DevS. Therefore IMO we
>> can maximum provide xml, js, css, jag file editors and lets them to create
>> the structure of Capp from DevS. IMO creating such extension support will
>> have considerable effort.
>>
>
> Hi Sinthuja
> Just had a chat with Nisala,
> Expected outcome of DevS tooling was to make the developer's life easy on
> creating dashboards, gadgets, layouts an themes. We have in built support
> coming from eclipse for xml, html, css etc and we had jaggery editor with
> code completion features. So I believe we can integrate these bits and
> pieces and provide a IDE based tooling. As all developers are not command
> line developers, I believe providing this kind of tooling would be useful
> for general users.
> As you already have maven build (packaging) tool and Capp tool for the
> same, my suggestion is to introduce arch-type, then we can reuse use of
> same arch-type and maven plugins to create the eclipse IDE plugin. So at
> the end of the day we will have both command line and IDE based tooling.
> WDYT?
>

Basically IMO IDE support is needed for creating custom gadgets and custom
layouts. But the other parts such as creating dashboards, creating pages
with default layouts, integrating gadgets into the dashboard pages, etc are
provided from DS itself, and it's just drag and drop. And hence I don't
think we need to provide same set of functionality which is already covered
in DS, rather we need to focus on the point where users could create custom
gadgets, and layouts which is the dev effort for the users in the context
of DS. I don't think we can provide such DevS support feature for this
release given the short time frame now.

But anyhow lets have a discussion on this, come to our plan so that we can
execute this on the future releases. @Nisala, please schedule a meeting
Wednesday after noon or Thursday.

Thanks,
Sinthuja.


> Thanks
> Susinda
>
>
>
>
>
>>
>> Thanks,
>> Sinthuja.
>>
>> On Fri, Aug 19, 2016 at 5:24 PM, Nisala Nanayakkara 
>> wrote:
>>
>>> Hi,
>>>
>>> Thanks for prompt reply. I will arrange a meeting to discuss this matter.
>>>
>>> Thanks,
>>> Nisala
>>>
>>> On Fri, Aug 19, 2016 at 10:52 AM, Susinda Perera 
>>> wrote:
>>>
 Hi Nisala

 We may need to create a new repo and host these maven plugins. As an
 example esb uses maven-tooling-esb[1] and bps uses maven-tooling-bps[2] to
 maintain the maven plugins. As we already have the maven plugins i think we
 can easily build the DevStudio based tooling with using these plugins.
 Please arrange a time to discuss this.

 [1] - https://github.com/wso2/maven-tooling-esb
 [2] - https://github.com/wso2/maven-tooling-bps



 On Thu, Aug 18, 2016 at 6:45 PM, Nisala Nanayakkara 
 wrote:

> Hi,
>
> I have implemented maven - plugins for each artifacts in WSO2
> Dashboard Server. So there are four maven - plugins for
> dashboards,gadgets,layouts and themes which can be used to generate a CAR
> file consisting with these artifacts. But we are not very much clear about
> where we have to maintain these maven - plugins. Is it better to keep it
> within our carbon-dashboards repository ? Or is it better to maintain 
> these
> as a separate repository.
>
> @DevStudioTeam : Can you provide recommended way of maintaining these
> maven-plugins ?
>
> Thanks,
> Nisala
>
> On Mon, Aug 15, 2016 at 10:51 AM, Susinda Perera 
> wrote:
>
>> Do we have tooling support for this new release, like
>> create/edit/deploy gadgets/dashboards etc. If not shall we add this to
>> roadmap. DevS team will be able to help on this task.
>>
>> Thanks
>> Susinda
>>
>> On Fri, Aug 12, 2016 at 8:23 PM, Megala Uthayakumar 
>> wrote:
>>
>>> WSO2 Dashboard Server 2.1.0-Alpha Released!
>>>
>>> WSO2 Dashboard Server team is pleased to announce the release of
>>> WSO2 Dashboard Server 2.1.0 Alpha. This release comes with the following
>>> bug fixes, improvements and tasks. You can download the distribution 
>>> from
>>> [1] and view the documentation at [2].
>>> Bug
>>>
>>>- [UES-990 ] - All the
>>>query params get appended to the url 

Re: [Dev] [Announce] [Architecture] WSO2 Dashboard Server 2.1.0-Alpha Released!

[Susinda Perera]

On Sun, Aug 21, 2016 at 5:06 PM, Sinthuja Ragendran 
wrote:

> Hi Nisala,
>
> So lets create a new repo for our new maven plugin, and lets include
> source there as per Susinda.
>
> @Susinda,
> Can you please elaborate bit more with what is the expected outcome when
> DevS based tooling using this maven plugin for DS? Because in the context,
> DS it self is a tool to create dashboard, gadgets, etc, therefore we don't
> intend to provide that sort of functionality with DevS. Therefore IMO we
> can maximum provide xml, js, css, jag file editors and lets them to create
> the structure of Capp from DevS. IMO creating such extension support will
> have considerable effort.
>

Hi Sinthuja
Just had a chat with Nisala,
Expected outcome of DevS tooling was to make the developer's life easy on
creating dashboards, gadgets, layouts an themes. We have in built support
coming from eclipse for xml, html, css etc and we had jaggery editor with
code completion features. So I believe we can integrate these bits and
pieces and provide a IDE based tooling. As all developers are not command
line developers, I believe providing this kind of tooling would be useful
for general users.
As you already have maven build (packaging) tool and Capp tool for the
same, my suggestion is to introduce arch-type, then we can reuse use of
same arch-type and maven plugins to create the eclipse IDE plugin. So at
the end of the day we will have both command line and IDE based tooling.
WDYT?

Thanks
Susinda





>
> Thanks,
> Sinthuja.
>
> On Fri, Aug 19, 2016 at 5:24 PM, Nisala Nanayakkara 
> wrote:
>
>> Hi,
>>
>> Thanks for prompt reply. I will arrange a meeting to discuss this matter.
>>
>> Thanks,
>> Nisala
>>
>> On Fri, Aug 19, 2016 at 10:52 AM, Susinda Perera 
>> wrote:
>>
>>> Hi Nisala
>>>
>>> We may need to create a new repo and host these maven plugins. As an
>>> example esb uses maven-tooling-esb[1] and bps uses maven-tooling-bps[2] to
>>> maintain the maven plugins. As we already have the maven plugins i think we
>>> can easily build the DevStudio based tooling with using these plugins.
>>> Please arrange a time to discuss this.
>>>
>>> [1] - https://github.com/wso2/maven-tooling-esb
>>> [2] - https://github.com/wso2/maven-tooling-bps
>>>
>>>
>>>
>>> On Thu, Aug 18, 2016 at 6:45 PM, Nisala Nanayakkara 
>>> wrote:
>>>
 Hi,

 I have implemented maven - plugins for each artifacts in WSO2 Dashboard
 Server. So there are four maven - plugins for dashboards,gadgets,layouts
 and themes which can be used to generate a CAR file consisting with these
 artifacts. But we are not very much clear about where we have to maintain
 these maven - plugins. Is it better to keep it within our carbon-dashboards
 repository ? Or is it better to maintain these as a separate repository.

 @DevStudioTeam : Can you provide recommended way of maintaining these
 maven-plugins ?

 Thanks,
 Nisala

 On Mon, Aug 15, 2016 at 10:51 AM, Susinda Perera 
 wrote:

> Do we have tooling support for this new release, like
> create/edit/deploy gadgets/dashboards etc. If not shall we add this to
> roadmap. DevS team will be able to help on this task.
>
> Thanks
> Susinda
>
> On Fri, Aug 12, 2016 at 8:23 PM, Megala Uthayakumar 
> wrote:
>
>> WSO2 Dashboard Server 2.1.0-Alpha Released!
>>
>> WSO2 Dashboard Server team is pleased to announce the release of WSO2
>> Dashboard Server 2.1.0 Alpha. This release comes with the following bug
>> fixes, improvements and tasks. You can download the distribution from [1]
>> and view the documentation at [2].
>> Bug
>>
>>- [UES-990 ] - All the
>>query params get appended to the url when navigating via hierarchical 
>> menu
>>- [UES-1016 ] - Tenant ID
>>is always super tenant ID in Gadget Generation Wizard
>>- [UES-1018 ] - DS Console
>>differs from the WSO2 theme
>>- [UES-1022 ] - Product
>>version in footer is incorrect
>>- [UES-1023 ] - Create
>>view menu rendered incorrectly
>>- [UES-1028 ] - Creating
>>gadgets in third-party store - Thumbnail image does not show
>>
>> Improvement
>>
>>- [UES-970 ] - Add download
>>functionality to gadgets listed
>>- [UES-995 ] - Having a
>>landing page for a dashboard is optional
>>- [UES-1003 ] - Modify the
>>ES extension to not allow the assets to be editable 

Re: [Dev] [Announce] [Architecture] WSO2 Dashboard Server 2.1.0-Alpha Released!

[Sinthuja Ragendran]

Hi Nisala,

So lets create a new repo for our new maven plugin, and lets include source
there as per Susinda.

@Susinda,
Can you please elaborate bit more with what is the expected outcome when
DevS based tooling using this maven plugin for DS? Because in the context,
DS it self is a tool to create dashboard, gadgets, etc, therefore we don't
intend to provide that sort of functionality with DevS. Therefore IMO we
can maximum provide xml, js, css, jag file editors and lets them to create
the structure of Capp from DevS. IMO creating such extension support will
have considerable effort.

Thanks,
Sinthuja.

On Fri, Aug 19, 2016 at 5:24 PM, Nisala Nanayakkara  wrote:

> Hi,
>
> Thanks for prompt reply. I will arrange a meeting to discuss this matter.
>
> Thanks,
> Nisala
>
> On Fri, Aug 19, 2016 at 10:52 AM, Susinda Perera  wrote:
>
>> Hi Nisala
>>
>> We may need to create a new repo and host these maven plugins. As an
>> example esb uses maven-tooling-esb[1] and bps uses maven-tooling-bps[2] to
>> maintain the maven plugins. As we already have the maven plugins i think we
>> can easily build the DevStudio based tooling with using these plugins.
>> Please arrange a time to discuss this.
>>
>> [1] - https://github.com/wso2/maven-tooling-esb
>> [2] - https://github.com/wso2/maven-tooling-bps
>>
>>
>>
>> On Thu, Aug 18, 2016 at 6:45 PM, Nisala Nanayakkara 
>> wrote:
>>
>>> Hi,
>>>
>>> I have implemented maven - plugins for each artifacts in WSO2 Dashboard
>>> Server. So there are four maven - plugins for dashboards,gadgets,layouts
>>> and themes which can be used to generate a CAR file consisting with these
>>> artifacts. But we are not very much clear about where we have to maintain
>>> these maven - plugins. Is it better to keep it within our carbon-dashboards
>>> repository ? Or is it better to maintain these as a separate repository.
>>>
>>> @DevStudioTeam : Can you provide recommended way of maintaining these
>>> maven-plugins ?
>>>
>>> Thanks,
>>> Nisala
>>>
>>> On Mon, Aug 15, 2016 at 10:51 AM, Susinda Perera 
>>> wrote:
>>>
 Do we have tooling support for this new release, like
 create/edit/deploy gadgets/dashboards etc. If not shall we add this to
 roadmap. DevS team will be able to help on this task.

 Thanks
 Susinda

 On Fri, Aug 12, 2016 at 8:23 PM, Megala Uthayakumar 
 wrote:

> WSO2 Dashboard Server 2.1.0-Alpha Released!
>
> WSO2 Dashboard Server team is pleased to announce the release of WSO2
> Dashboard Server 2.1.0 Alpha. This release comes with the following bug
> fixes, improvements and tasks. You can download the distribution from [1]
> and view the documentation at [2].
> Bug
>
>- [UES-990 ] - All the query
>params get appended to the url when navigating via hierarchical menu
>- [UES-1016 ] - Tenant ID
>is always super tenant ID in Gadget Generation Wizard
>- [UES-1018 ] - DS Console
>differs from the WSO2 theme
>- [UES-1022 ] - Product
>version in footer is incorrect
>- [UES-1023 ] - Create view
>menu rendered incorrectly
>- [UES-1028 ] - Creating
>gadgets in third-party store - Thumbnail image does not show
>
> Improvement
>
>- [UES-970 ] - Add download
>functionality to gadgets listed
>- [UES-995 ] - Having a
>landing page for a dashboard is optional
>- [UES-1003 ] - Modify the
>ES extension to not allow the assets to be editable in published asset
>- [UES-1010 ] - Add shindig
>features to get the hostName,port and tenant domain
>- [UES-1012 ] - Store the
>theme level properties to dashboard.json and retrieve these theme
>properties while rendering the page
>- [UES-1014 ] - Add new
>gadget/layout button at the end of the gadget listing and layout 
> listings
>when user designs dashboard
>- [UES-1015 ] - Dashboard
>page loading icon for embeddable gadget feature
>
> Task
>
>- [UES-1005 ] - Provide
>common repository for js libraries to use in gadgets
>- [UES-1006 ] - Dashboard
>page loading icon to show after all gadgets are loaded
>- [UES-1007 

Re: [Dev] [Announce] [Architecture] WSO2 Dashboard Server 2.1.0-Alpha Released!

[Nisala Nanayakkara]

Hi,

Thanks for prompt reply. I will arrange a meeting to discuss this matter.

Thanks,
Nisala

On Fri, Aug 19, 2016 at 10:52 AM, Susinda Perera  wrote:

> Hi Nisala
>
> We may need to create a new repo and host these maven plugins. As an
> example esb uses maven-tooling-esb[1] and bps uses maven-tooling-bps[2] to
> maintain the maven plugins. As we already have the maven plugins i think we
> can easily build the DevStudio based tooling with using these plugins.
> Please arrange a time to discuss this.
>
> [1] - https://github.com/wso2/maven-tooling-esb
> [2] - https://github.com/wso2/maven-tooling-bps
>
>
>
> On Thu, Aug 18, 2016 at 6:45 PM, Nisala Nanayakkara 
> wrote:
>
>> Hi,
>>
>> I have implemented maven - plugins for each artifacts in WSO2 Dashboard
>> Server. So there are four maven - plugins for dashboards,gadgets,layouts
>> and themes which can be used to generate a CAR file consisting with these
>> artifacts. But we are not very much clear about where we have to maintain
>> these maven - plugins. Is it better to keep it within our carbon-dashboards
>> repository ? Or is it better to maintain these as a separate repository.
>>
>> @DevStudioTeam : Can you provide recommended way of maintaining these
>> maven-plugins ?
>>
>> Thanks,
>> Nisala
>>
>> On Mon, Aug 15, 2016 at 10:51 AM, Susinda Perera 
>> wrote:
>>
>>> Do we have tooling support for this new release, like create/edit/deploy
>>> gadgets/dashboards etc. If not shall we add this to roadmap. DevS team will
>>> be able to help on this task.
>>>
>>> Thanks
>>> Susinda
>>>
>>> On Fri, Aug 12, 2016 at 8:23 PM, Megala Uthayakumar 
>>> wrote:
>>>
 WSO2 Dashboard Server 2.1.0-Alpha Released!

 WSO2 Dashboard Server team is pleased to announce the release of WSO2
 Dashboard Server 2.1.0 Alpha. This release comes with the following bug
 fixes, improvements and tasks. You can download the distribution from [1]
 and view the documentation at [2].
 Bug

- [UES-990 ] - All the query
params get appended to the url when navigating via hierarchical menu
- [UES-1016 ] - Tenant ID is
always super tenant ID in Gadget Generation Wizard
- [UES-1018 ] - DS Console
differs from the WSO2 theme
- [UES-1022 ] - Product
version in footer is incorrect
- [UES-1023 ] - Create view
menu rendered incorrectly
- [UES-1028 ] - Creating
gadgets in third-party store - Thumbnail image does not show

 Improvement

- [UES-970 ] - Add download
functionality to gadgets listed
- [UES-995 ] - Having a
landing page for a dashboard is optional
- [UES-1003 ] - Modify the
ES extension to not allow the assets to be editable in published asset
- [UES-1010 ] - Add shindig
features to get the hostName,port and tenant domain
- [UES-1012 ] - Store the
theme level properties to dashboard.json and retrieve these theme
properties while rendering the page
- [UES-1014 ] - Add new
gadget/layout button at the end of the gadget listing and layout 
 listings
when user designs dashboard
- [UES-1015 ] - Dashboard
page loading icon for embeddable gadget feature

 Task

- [UES-1005 ] - Provide
common repository for js libraries to use in gadgets
- [UES-1006 ] - Dashboard
page loading icon to show after all gadgets are loaded
- [UES-1007 ] - Fixed the
issue in PDF download feature in firefox browser
- [UES-1008 ] - Fixing
issues in running the dashboard server with samples
- [UES-1029 ] - Create
Puppet script for Dashboard Server Auto Deployment

 Reporting Issues

 Issues can be reported through the Public JIRA
  project for WSO2 Dashboard Server.


 [1]- https://github.com/wso2/product-ds/releases/download/v2
 .1.0-alpha/wso2ds-2.1.0-SNAPSHOT.zip

 [2]- https://docs.wso2.com/display/DS210/WSO2+Dashboard+Serv
 er+Documentation


 Thanks,

 Dashboard Server Team.

 --
 Megala 

Re: [Dev] [Announce] [Architecture] WSO2 Dashboard Server 2.1.0-Alpha Released!

[Susinda Perera]

Hi Nisala

We may need to create a new repo and host these maven plugins. As an
example esb uses maven-tooling-esb[1] and bps uses maven-tooling-bps[2] to
maintain the maven plugins. As we already have the maven plugins i think we
can easily build the DevStudio based tooling with using these plugins.
Please arrange a time to discuss this.

[1] - https://github.com/wso2/maven-tooling-esb
[2] - https://github.com/wso2/maven-tooling-bps



On Thu, Aug 18, 2016 at 6:45 PM, Nisala Nanayakkara  wrote:

> Hi,
>
> I have implemented maven - plugins for each artifacts in WSO2 Dashboard
> Server. So there are four maven - plugins for dashboards,gadgets,layouts
> and themes which can be used to generate a CAR file consisting with these
> artifacts. But we are not very much clear about where we have to maintain
> these maven - plugins. Is it better to keep it within our carbon-dashboards
> repository ? Or is it better to maintain these as a separate repository.
>
> @DevStudioTeam : Can you provide recommended way of maintaining these
> maven-plugins ?
>
> Thanks,
> Nisala
>
> On Mon, Aug 15, 2016 at 10:51 AM, Susinda Perera  wrote:
>
>> Do we have tooling support for this new release, like create/edit/deploy
>> gadgets/dashboards etc. If not shall we add this to roadmap. DevS team will
>> be able to help on this task.
>>
>> Thanks
>> Susinda
>>
>> On Fri, Aug 12, 2016 at 8:23 PM, Megala Uthayakumar 
>> wrote:
>>
>>> WSO2 Dashboard Server 2.1.0-Alpha Released!
>>>
>>> WSO2 Dashboard Server team is pleased to announce the release of WSO2
>>> Dashboard Server 2.1.0 Alpha. This release comes with the following bug
>>> fixes, improvements and tasks. You can download the distribution from [1]
>>> and view the documentation at [2].
>>> Bug
>>>
>>>- [UES-990 ] - All the query
>>>params get appended to the url when navigating via hierarchical menu
>>>- [UES-1016 ] - Tenant ID is
>>>always super tenant ID in Gadget Generation Wizard
>>>- [UES-1018 ] - DS Console
>>>differs from the WSO2 theme
>>>- [UES-1022 ] - Product
>>>version in footer is incorrect
>>>- [UES-1023 ] - Create view
>>>menu rendered incorrectly
>>>- [UES-1028 ] - Creating
>>>gadgets in third-party store - Thumbnail image does not show
>>>
>>> Improvement
>>>
>>>- [UES-970 ] - Add download
>>>functionality to gadgets listed
>>>- [UES-995 ] - Having a
>>>landing page for a dashboard is optional
>>>- [UES-1003 ] - Modify the ES
>>>extension to not allow the assets to be editable in published asset
>>>- [UES-1010 ] - Add shindig
>>>features to get the hostName,port and tenant domain
>>>- [UES-1012 ] - Store the
>>>theme level properties to dashboard.json and retrieve these theme
>>>properties while rendering the page
>>>- [UES-1014 ] - Add new
>>>gadget/layout button at the end of the gadget listing and layout listings
>>>when user designs dashboard
>>>- [UES-1015 ] - Dashboard
>>>page loading icon for embeddable gadget feature
>>>
>>> Task
>>>
>>>- [UES-1005 ] - Provide
>>>common repository for js libraries to use in gadgets
>>>- [UES-1006 ] - Dashboard
>>>page loading icon to show after all gadgets are loaded
>>>- [UES-1007 ] - Fixed the
>>>issue in PDF download feature in firefox browser
>>>- [UES-1008 ] - Fixing issues
>>>in running the dashboard server with samples
>>>- [UES-1029 ] - Create Puppet
>>>script for Dashboard Server Auto Deployment
>>>
>>> Reporting Issues
>>>
>>> Issues can be reported through the Public JIRA
>>>  project for WSO2 Dashboard Server.
>>>
>>>
>>> [1]- https://github.com/wso2/product-ds/releases/download/v2
>>> .1.0-alpha/wso2ds-2.1.0-SNAPSHOT.zip
>>>
>>> [2]- https://docs.wso2.com/display/DS210/WSO2+Dashboard+Serv
>>> er+Documentation
>>>
>>>
>>> Thanks,
>>>
>>> Dashboard Server Team.
>>>
>>> --
>>> Megala Uthayakumar
>>>
>>> Software Engineer
>>> Mobile : 0779967122
>>>
>>> ___
>>> Announce mailing list
>>> annou...@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/announce
>>>
>>>
>>
>>
>> --
>> *Susinda Perera*
>> Software Engineer
>> B.Sc.(Eng), 

Re: [Dev] [Announce] [Architecture] WSO2 Dashboard Server 2.1.0-Alpha Released!

[Nisala Nanayakkara]

Hi,

I have implemented maven - plugins for each artifacts in WSO2 Dashboard
Server. So there are four maven - plugins for dashboards,gadgets,layouts
and themes which can be used to generate a CAR file consisting with these
artifacts. But we are not very much clear about where we have to maintain
these maven - plugins. Is it better to keep it within our carbon-dashboards
repository ? Or is it better to maintain these as a separate repository.

@DevStudioTeam : Can you provide recommended way of maintaining these
maven-plugins ?

Thanks,
Nisala

On Mon, Aug 15, 2016 at 10:51 AM, Susinda Perera  wrote:

> Do we have tooling support for this new release, like create/edit/deploy
> gadgets/dashboards etc. If not shall we add this to roadmap. DevS team will
> be able to help on this task.
>
> Thanks
> Susinda
>
> On Fri, Aug 12, 2016 at 8:23 PM, Megala Uthayakumar 
> wrote:
>
>> WSO2 Dashboard Server 2.1.0-Alpha Released!
>>
>> WSO2 Dashboard Server team is pleased to announce the release of WSO2
>> Dashboard Server 2.1.0 Alpha. This release comes with the following bug
>> fixes, improvements and tasks. You can download the distribution from [1]
>> and view the documentation at [2].
>> Bug
>>
>>- [UES-990 ] - All the query
>>params get appended to the url when navigating via hierarchical menu
>>- [UES-1016 ] - Tenant ID is
>>always super tenant ID in Gadget Generation Wizard
>>- [UES-1018 ] - DS Console
>>differs from the WSO2 theme
>>- [UES-1022 ] - Product
>>version in footer is incorrect
>>- [UES-1023 ] - Create view
>>menu rendered incorrectly
>>- [UES-1028 ] - Creating
>>gadgets in third-party store - Thumbnail image does not show
>>
>> Improvement
>>
>>- [UES-970 ] - Add download
>>functionality to gadgets listed
>>- [UES-995 ] - Having a landing
>>page for a dashboard is optional
>>- [UES-1003 ] - Modify the ES
>>extension to not allow the assets to be editable in published asset
>>- [UES-1010 ] - Add shindig
>>features to get the hostName,port and tenant domain
>>- [UES-1012 ] - Store the
>>theme level properties to dashboard.json and retrieve these theme
>>properties while rendering the page
>>- [UES-1014 ] - Add new
>>gadget/layout button at the end of the gadget listing and layout listings
>>when user designs dashboard
>>- [UES-1015 ] - Dashboard page
>>loading icon for embeddable gadget feature
>>
>> Task
>>
>>- [UES-1005 ] - Provide common
>>repository for js libraries to use in gadgets
>>- [UES-1006 ] - Dashboard page
>>loading icon to show after all gadgets are loaded
>>- [UES-1007 ] - Fixed the
>>issue in PDF download feature in firefox browser
>>- [UES-1008 ] - Fixing issues
>>in running the dashboard server with samples
>>- [UES-1029 ] - Create Puppet
>>script for Dashboard Server Auto Deployment
>>
>> Reporting Issues
>>
>> Issues can be reported through the Public JIRA
>>  project for WSO2 Dashboard Server.
>>
>>
>> [1]- https://github.com/wso2/product-ds/releases/download/v2
>> .1.0-alpha/wso2ds-2.1.0-SNAPSHOT.zip
>>
>> [2]- https://docs.wso2.com/display/DS210/WSO2+Dashboard+Serv
>> er+Documentation
>>
>>
>> Thanks,
>>
>> Dashboard Server Team.
>>
>> --
>> Megala Uthayakumar
>>
>> Software Engineer
>> Mobile : 0779967122
>>
>> ___
>> Announce mailing list
>> annou...@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/announce
>>
>>
>
>
> --
> *Susinda Perera*
> Software Engineer
> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
> Mobile:(+94)716049075
> Blog: susinda.blogspot.com
> WSO2 Inc. http://wso2.com/
> Tel : 94 11 214 5345 Fax :94 11 2145300
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Announce] [Architecture] WSO2 Dashboard Server 2.1.0-Alpha Released!

[Susinda Perera]

Do we have tooling support for this new release, like create/edit/deploy
gadgets/dashboards etc. If not shall we add this to roadmap. DevS team will
be able to help on this task.

Thanks
Susinda

On Fri, Aug 12, 2016 at 8:23 PM, Megala Uthayakumar  wrote:

> WSO2 Dashboard Server 2.1.0-Alpha Released!
>
> WSO2 Dashboard Server team is pleased to announce the release of WSO2
> Dashboard Server 2.1.0 Alpha. This release comes with the following bug
> fixes, improvements and tasks. You can download the distribution from [1]
> and view the documentation at [2].
> Bug
>
>- [UES-990 ] - All the query
>params get appended to the url when navigating via hierarchical menu
>- [UES-1016 ] - Tenant ID is
>always super tenant ID in Gadget Generation Wizard
>- [UES-1018 ] - DS Console
>differs from the WSO2 theme
>- [UES-1022 ] - Product version
>in footer is incorrect
>- [UES-1023 ] - Create view
>menu rendered incorrectly
>- [UES-1028 ] - Creating
>gadgets in third-party store - Thumbnail image does not show
>
> Improvement
>
>- [UES-970 ] - Add download
>functionality to gadgets listed
>- [UES-995 ] - Having a landing
>page for a dashboard is optional
>- [UES-1003 ] - Modify the ES
>extension to not allow the assets to be editable in published asset
>- [UES-1010 ] - Add shindig
>features to get the hostName,port and tenant domain
>- [UES-1012 ] - Store the theme
>level properties to dashboard.json and retrieve these theme properties
>while rendering the page
>- [UES-1014 ] - Add new
>gadget/layout button at the end of the gadget listing and layout listings
>when user designs dashboard
>- [UES-1015 ] - Dashboard page
>loading icon for embeddable gadget feature
>
> Task
>
>- [UES-1005 ] - Provide common
>repository for js libraries to use in gadgets
>- [UES-1006 ] - Dashboard page
>loading icon to show after all gadgets are loaded
>- [UES-1007 ] - Fixed the issue
>in PDF download feature in firefox browser
>- [UES-1008 ] - Fixing issues
>in running the dashboard server with samples
>- [UES-1029 ] - Create Puppet
>script for Dashboard Server Auto Deployment
>
> Reporting Issues
>
> Issues can be reported through the Public JIRA
>  project for WSO2 Dashboard Server.
>
>
> [1]- https://github.com/wso2/product-ds/releases/download/
> v2.1.0-alpha/wso2ds-2.1.0-SNAPSHOT.zip
>
> [2]- https://docs.wso2.com/display/DS210/WSO2+Dashboard+Serv
> er+Documentation
>
>
> Thanks,
>
> Dashboard Server Team.
>
> --
> Megala Uthayakumar
>
> Software Engineer
> Mobile : 0779967122
>
> ___
> Announce mailing list
> annou...@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/announce
>
>


-- 
*Susinda Perera*
Software Engineer
B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
Mobile:(+94)716049075
Blog: susinda.blogspot.com
WSO2 Inc. http://wso2.com/
Tel : 94 11 214 5345 Fax :94 11 2145300
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev