Hi All, My bad, I missed mentioning an important thing. My intention on this mail was to get feedback on the UI structure. There are some other things to be done according to [1] . Currently , same structure (Listing per environment) is used to list the resources (Databases,Datasources,APIs etc). As my self and Shiro discussed , we are going to have a unified process when creating resources. So the plan is to create a resources in all stages if the creator of the resource has a particular permission. Will update the thread with progress soon.
[1] https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0ArxUiuGtJCq4dEhIWTB6Zm9GWDNrcGZ1Um1lUzFxTWc&usp=drive_web#gid=2 Thanks, Asanka D On Sun, Apr 20, 2014 at 8:27 AM, Shiroshica Kulatilake <[email protected]>wrote: > Hi Asanka, > > So the requirement drawn from the above comments is that for each resource > we need to show the property change across environments - hence the > grouping should be done like that - and we need to use the same approach > for all resources. > > Currently we group resources per environment so when there is a resource > say API xyz we need to go through dev, test, prod separately to find the > values - instead we have one API xyz and have the separate environments > listed against it with differing values. > > Thank you, > Shiro > > > On Sun, Apr 20, 2014 at 12:19 AM, Dmitry Sotnikov <[email protected]> wrote: > >> Dimuthu, >> >> +1 on all the points. >> >> Indeed need a unified approach, and indeed the screenshot that you >> attached is a step in that direction but needs further work to make its UX >> better. >> >> Dmitry >> >> >> On Sat, Apr 19, 2014 at 6:15 AM, Dimuthu Leelarathne >> <[email protected]>wrote: >> >>> Hi all, >>> >>> I am attaching the current UI we have for APIs. So in this screenshot, >>> it is grouped by the name and we can see the behaviour of it's value in >>> Development,Testing and Production. >>> >>> Personally, I don't like the look-and-feel of this control, but it has >>> the correct concept. We can develop a control with better look-and-feel and >>> use it across everything - APIs, DBs and Properties. >>> >>> In addition to points Dmitry highlighted, I would like to highlight >>> editing fuctionality of resources. The idea behind the editing >>> functionality improvement is "when we are editing a particular resource, we >>> should know what is the stage that we are editing and what values". Right >>> now the editing functionality is not user-friendly because we go to edit >>> page without the knowledge of the stage. Perhaps we can incorporate that >>> into the control as well. >>> >>> When we develop this control (html or methodology or tag - i don't know >>> the exact term), we can use it across all resources (APIs, DBs and >>> Properties). >>> >>> Furthermore, we only have to review one of these - either APIs, DBs or >>> Properties. Ideally everything else follows the same style and need not >>> even be reviewed. It must be that consistent! >>> >>> thanks, >>> dimuthu >>> >>> >>> >>> >>> On Sat, Apr 19, 2014 at 12:58 AM, Dmitry Sotnikov <[email protected]>wrote: >>> >>>> Asanka, >>>> >>>> From my perspective, all resource management in App Factory exists >>>> within the ALM conceptual model. The coolness of App Factory is *not*that >>>> you can list the resources (properties, APIs, databases), but that you >>>> can get them automatically switched as the application moves from dev to >>>> test to prod. >>>> >>>> This means that for all resources (properties, APIs, databases) - we >>>> need to follow the same conceptual model: >>>> >>>> Resource A: >>>> >>>> - It's work in Dev, >>>> - It's work in Test, >>>> - It's work in Prod, >>>> >>>> Resource B: >>>> >>>> - It's work in Dev, >>>> - It's work in Test, >>>> - It's work in Prod, >>>> >>>> And for them all we need to have: >>>> 1. Code samples on how to use them, >>>> 2. Ability to simply get them to be the same or separate for the >>>> different stages of ALM. >>>> >>>> To your question, the URL naming of the column is fine. >>>> >>>> Thanks! >>>> Dmitry >>>> >>>> >>>> On Fri, Apr 18, 2014 at 5:32 AM, Asanka Dissanayake >>>> <[email protected]>wrote: >>>> >>>>> Hi All, >>>>> Please find the inline image after @subject . >>>>> >>>>> >>>>> The main improvement that has been carried out is , listing APIs per >>>>> the environment. In addition to that I made a small change renaming the >>>>> "Values" column to "URL". The rationale behind that change is , Earlier >>>>> the >>>>> only value shown in that column is url (There are some other values >>>>> also,they are not shown ATM.Since this is a summary page, showing the URL >>>>> only is sufficient IMO) , so there is no point of naming the column as >>>>> "Values" and showing only the URL. >>>>> >>>>> WDYT? >>>>> >>>>> Thanks, >>>>> Asanka D >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> >>>>> *Asanka Dissanayake Software Engineer* >>>>> *WSO2 Inc. - lean . enterprise . middleware | wso2.com >>>>> <http://wso2.com/>* >>>>> >>>>> *email: [email protected] <[email protected]>, blog: >>>>> cyberwaadiya.blogspot.com >>>>> <http://cyberwaadiya.blogspot.com>, asankastechtalks.wordpress.com >>>>> <http://asankastechtalks.wordpress.com> mobile: +94 71 8373821* >>>>> >>>> >>>> >>>> >>>> -- >>>> Dmitry Sotnikov >>>> VP of Cloud; WSO2, Inc.; http://wso2.com/ >>>> email: [email protected]; cell: +1.949.303.9653; Skype: DSotnikov >>>> Lean . Enterprise . Middleware >>>> >>>> <http://wso2.com/events/> >>>> >>> >>> >>> >>> -- >>> Dimuthu Leelarathne >>> Architect & Product Lead of App Factory >>> >>> WSO2, Inc. (http://wso2.com) >>> email: [email protected] >>> Mobile : 0773661935 >>> >>> Lean . Enterprise . Middleware >>> >> >> >> >> -- >> Dmitry Sotnikov >> VP of Cloud; WSO2, Inc.; http://wso2.com/ >> email: [email protected]; cell: +1.949.303.9653; Skype: DSotnikov >> Lean . Enterprise . Middleware >> >> <http://wso2.com/events/> >> > > > > -- > Shiroshica Kulatilake > > Architect, > WSO2, Inc. http://wso2.com/ > Phone: +94 776523867 > -- *Asanka DissanayakeSoftware Engineer* *WSO2 Inc. - lean . enterprise . middleware | wso2.com <http://wso2.com/>* *email: [email protected] <[email protected]>, blog: cyberwaadiya.blogspot.com <http://cyberwaadiya.blogspot.com>, asankastechtalks.wordpress.com <http://asankastechtalks.wordpress.com> mobile: +94 71 8373821*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
