Hi all, I still believe that this is too much of information for creating a service. Be it mandatory, be it advanced, somethings that we store are definitely not things that are supposed to be entered by humans. Of course the repo can allow storing all of this, but that doesn't mean a human is going to type/select all of these. We need to have a chat and prune this list.
Isabelle, based on what we end up with, lets decide on the display model. Thanks, Senaka. On Tue, Feb 18, 2014 at 7:37 PM, Isabelle Mauny <[email protected]> wrote: > All, > > IMO, this has way too much vertical scrolling - the list of fields is > overwhelming in the advanced list. We need to use horizontal space, with > tabs for example, grouping the fields by themes. Mandatory stuff is on > first tab, additional data is on other tabs. > > Isabelle. > > > > ------ > Isabelle Mauny > Director, Product Management; WSO2, Inc.; http://wso2.com/ > email: [email protected] <[email protected]> - mobile: +34 616050684 > > > On Tue, Feb 18, 2014 at 4:51 PM, Chandana Napagoda <[email protected]>wrote: > >> Hi Senaka, >> >> I agree with your suggestion. As Pulasthi has proposed, we can redesign >> the screen with, required fields grouped into one section, and other >> contents collapsed in "Show Advance Settings" area. This is much similar >> to what we have used in project asset UI. >> >> Here with I have attaching an example design for add and edit view. >> >> Regards, >> Chandana >> >> >> >> On Tue, Feb 18, 2014 at 2:53 AM, Pulasthi Supun <[email protected]>wrote: >> >>> Hi All, >>> >>> How about adding a link like for example "Show Advance Settings" to >>> list all the information and only show the most required fields in the >>> default view. >>> >>> Regards, >>> Pulasthi >>> >>> >>> On Mon, Feb 17, 2014 at 12:20 PM, Senaka Fernando <[email protected]>wrote: >>> >>>> Hi Chandana, >>>> >>>> This looks good. Firstly, when we create the service asset in the >>>> store, we need to think whether it is necessary for everything that you >>>> store in the G-Reg's service asset to be listed here. I know it is useful >>>> to have an asset in the repository that can capture everything, but in >>>> terms of the UI, we should think twice as to what's needed. >>>> >>>> For example, when I'm adding a new service as a provider, or when I'm >>>> updating information about it, what do I like to be seeing/updating? If you >>>> think along these lines this UI is far too complicated to use. Can we >>>> identify what fields make sense to be on this? >>>> >>>> Thanks, >>>> Senaka. >>>> >>>> >>>> On Mon, Feb 17, 2014 at 8:50 AM, Chandana Napagoda >>>> <[email protected]>wrote: >>>> >>>>> Hi All, >>>>> >>>>> We are creating a WSO2 Enterprise Store based UI to capture Service >>>>> Information and this new UI is also based on the Configurable Governance >>>>> Artifacts(RXT). >>>>> >>>>> Here with I have attached the initial design of ES based Add Service >>>>> UI. In this design, overview section (first section of RXT) is visible and >>>>> other sections are collapsed. Either user can enter other information or >>>>> proceed with save action. In Edit view, all the sections are expanded. >>>>> Please refer the attached screenshots. >>>>> >>>>> Changes which will be made to saved RXT will be reflected to new UI as >>>>> well. >>>>> >>>>> Suggestions are welcome. >>>>> >>>>> Regards, >>>>> Chandna >>>>> -- >>>>> *Chandana Napagoda* >>>>> Senior Software Engineer >>>>> WSO2 Inc. - http://wso2.org >>>>> >>>>> *Email : [email protected] <[email protected]>**Mobile : >>>>> +94718169299 <%2B94718169299>* >>>>> >>>>> *Blog : http://cnapagoda.blogspot.com >>>>> <http://cnapagoda.blogspot.com>* >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> >>>> *[image: http://wso2.com] <http://wso2.com> Senaka Fernando* >>>> Senior Technical Lead; WSO2 Inc.; http://wso2.com >>>> >>>> >>>> >>>> * Member; Apache Software Foundation; http://apache.org >>>> <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1 >>>> 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*; >>>> >>>> >>>> *M: +94 77 322 1818 <%2B94%2077%20322%201818> Linked-In: >>>> http://linkedin.com/in/senakafernando >>>> <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware >>>> >>> >>> >>> >>> -- >>> -- >>> Pulasthi Supun >>> Software Engineer; WSO2 Inc.; http://wso2.com, >>> Email: [email protected] >>> Mobile: +94 (71) 9258281 >>> Blog : http://pulasthisupun.blogspot.com/ >>> Git hub profile: https://github.com/pulasthi >>> >> >> >> >> -- >> *Chandana Napagoda* >> Senior Software Engineer >> WSO2 Inc. - http://wso2.org >> >> *Email : [email protected] <[email protected]> **Mobile : +94718169299 >> <%2B94718169299>* >> >> *Blog : http://cnapagoda.blogspot.com <http://cnapagoda.blogspot.com>* >> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *[image: http://wso2.com] <http://wso2.com> Senaka Fernando* Senior Technical Lead; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
