Hi,

On Wed, Jun 1, 2016 at 11:09 AM, Udara Rathnayake <uda...@wso2.com> wrote:

> Hi Tanya,
>
> On Wed, Jun 1, 2016 at 10:56 AM, Tanya Madurapperuma <ta...@wso2.com>
> wrote:
>
>> Hi Udara,
>>
>> From where can we select the layout for the view? Or do we enforce using
>> the same layout for all the views of a single page?
>>
> ​We should open the layout selection panel and move to the newly created
> tab (role based view) once user select the role(s) and create the view​
> ​.​
>
> ​I think we should not restrict and enforce the same layout.
>
My question was because I assume a user has to click on (+) to create a new
view. If so I believe we have to have the UI design for getting layout
selection pane as well, because it is not same as getting it for creating a
new page.

>
>> On Tue, May 31, 2016 at 9:09 PM, Udara Rathnayake <uda...@wso2.com>
>> wrote:
>>
>>> Thanks Dakshika & Sinthuja.
>>>
>>> On Tue, May 31, 2016 at 7:10 PM, Sinthuja Ragendran <sinth...@wso2.com>
>>> wrote:
>>>
>>>> Hi Udara,
>>>>
>>>> As discussed offline we need to have following as well.
>>>>
>>>> - A name for each view so that if a user could see both views he/she
>>>> should be able switch.
>>>> - A default view should not be existing, and that should be associated
>>>> with roles selection option when the 'role based view' option is selected
>>>> in the left pane.
>>>>
>>> ​We have to revisit this a bit. Assume a scenario, where dashboard
>>> designer already have a default view.​
>>>
>>> ​At that point we should not just disable the default view and provide
>>> role selection option.
>>>
>> Even if they have a default view, they should have set a viewers role in
>> the dashboard settings page. So can't we use that role as the roles for
>> that page and get rid of default view.
>>
> Since we are bringing gadget level roles now, we might have to remove some
> gadgets from the default view in that case. This might confuse the
> designer. ​
>
>
We need to have a verdict on this. Say based on the gadget level roles
dashboard designer can see gadget A, B and C. And he is going to design a
dashboard for a viewer and that viewer is authorized to see gadget A, B and
D. But the gadget D will not be in the gadget listing for designer as he is
not authorized to see that gadget. But gadget C will be in the designers
listing even though viewer is not authorized to see the gadget C. How does
having a default view solve this problem?

> Thanks,
>> Tanya
>>
>>>
>>> - As Dakshika mentioned, the view tab settings will be required to
>>>> edit/update as well.
>>>> - During the personalization of dashboard mode, we shouldn't show the
>>>> options of editing the roles, etc for a view table, and only show the view
>>>> names in the tabs. Hence the user can't actually do any changes to the view
>>>> or anything, but he/she can add or delete gadgets, change layout, etc
>>>> according to their personal interest.
>>>>
>>>> Thanks,
>>>> Sinthuja.
>>>>
>>>>
>>>> On Tue, May 31, 2016 at 2:33 PM, Udara Rathnayake <uda...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Came up with following modifications to the existing dashboard
>>>>> designer UI to cater the $Subject.
>>>>>
>>>>> Designer can select and enable page view based on role(s) from the
>>>>> settings.
>>>>>
>>>>>
>>>>> ​
>>>>> ​Once this is enabled, we can update the dashboard designer with a
>>>>> drop down where dashboard designer can select a role and create the
>>>>> particular view. When the dashboard designer browse gadgets/widgets 
>>>>> section
>>>>> from this particular view(role based), we should only list down gadgets
>>>>> enabled for the selected role(have to come up with a gadget level config
>>>>> for this).
>>>>>
>>>>>
>>>>>
>>>>> ​ ​
>>>>> This role list can be a simple drop down (if we support one role per
>>>>> page) or can be a list with check-boxes, so we can support multiple roles
>>>>> per page view. (gadget listing for particular view should be the union of
>>>>> selected roles)
>>>>>
>>>>>
>>>>> ​
>>>>>  Designer UI after adding a role based page view,
>>>>>
>>>>>
>>>>> ​
>>>>>
>>>>> ​Appreciate your feedback on this.
>>>>> ​
>>>>>
>>>>> --
>>>>> Regards,
>>>>> UdaraR
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> *Sinthuja Rajendran*
>>>> Associate Technical Lead
>>>> WSO2, Inc.:http://wso2.com
>>>>
>>>> Blog: http://sinthu-rajan.blogspot.com/
>>>> Mobile: +94774273955
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Regards,
>>> UdaraR
>>>
>>
>>
>>
>> --
>> Tanya Madurapperuma
>>
>> Senior Software Engineer,
>> WSO2 Inc. : wso2.com
>> Mobile : +94718184439
>> Blog : http://tanyamadurapperuma.blogspot.com
>>
>
>
>
> --
> Regards,
> UdaraR
>



-- 
Tanya Madurapperuma

Senior Software Engineer,
WSO2 Inc. : wso2.com
Mobile : +94718184439
Blog : http://tanyamadurapperuma.blogspot.com
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to