Hi Dimuthu, Yes it is very clear. But what about if we introduce another tab saying "My Workspace" or something to do this that keeping this complete repo&build page as it is. It is not only build and repo but also there can be some more things related to personal. But not for this release.
WDYT ? thanks *Harsha Thirimanna* Senior Software Engineer; WSO2, Inc.; http://wso2.com * <http://www.apache.org/>* * email: **[email protected]* <[email protected]>* cell: +94 71 5186770* * twitter: **http://twitter.com/ <http://twitter.com/afkham_azeez>* *harshathirimann linked-in: **http: <http://lk.linkedin.com/in/afkhamazeez>**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122 <http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122>* *Lean . Enterprise . Middleware* On Fri, Apr 25, 2014 at 8:29 AM, Dimuthu Leelarathne <[email protected]>wrote: > Hi all, > > +1 for Harsha's suggestions. > > In addition, I have a drastic suggestion. With a lot of branches this UI > will be cluttered. Therefore I have a proposal that I has been working on > my head. What if we show only a single version on this page? > > We give a drop down with all the versions. And the user to select a > version that he is interested in. After selecting the version the same > information will be shown. This idea came after I started thinking about > the user stories as Dmitry suggested. > > Bottom line is at any given time, a developer will only be concentrating > on one version of the application. Think of our use case as developers. > This will eliminate the information overload. > > So additional work is only a drop down for selecting the version but rest > of the things stays the same. WDYT? > > thanks, > dimuthu > > > On Fri, Apr 25, 2014 at 8:14 AM, Harsha Thirimanna <[email protected]>wrote: > >> Hi Chanaka, >> >> 1. This git command help text should come with each and every personal >> repository version, not with master repositories. >> 2. Same style should use like "successful" to "Deployed" under >> deployment column. >> 3. Instead of using highlighted color to forked repository version >> record, keep it as same as others. But put very clear separater in between >> master and forked repositories. >> >> >> I feel other changes are very cool. >> >> thanks >> >> >> *Harsha Thirimanna* >> >> Senior Software Engineer; WSO2, Inc.; http://wso2.com >> * <http://www.apache.org/>* >> * email: **[email protected]* <[email protected]>* cell: +94 71 5186770* >> * twitter: **http://twitter.com/ <http://twitter.com/afkham_azeez>* >> *harshathirimann linked-in: **http: >> <http://lk.linkedin.com/in/afkhamazeez>**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122 >> <http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122>* >> >> *Lean . Enterprise . Middleware* >> >> >> >> On Fri, Apr 25, 2014 at 7:56 AM, Chanaka Jayasena <[email protected]>wrote: >> >>> Hi all, >>> >>> Harsha and I was discussing about the improvements that can be done to >>> the UI base on previous Usability reviews. We came up with the following >>> two screens. I am working with Harsha with the changes. >>> >>> thanks, >>> Chanaka >>> >>> -- >>> Chanaka Jayasena >>> Senior Software Engineer; WSO2, Inc.; http://wso2.com/ >>> email: [email protected]; cell: +94 77 785 5565 >>> blog: http://chanaka3d.blogspot.com >>> >> >> > > > -- > Dimuthu Leelarathne > Architect & Product Lead of App Factory > > WSO2, Inc. (http://wso2.com) > email: [email protected] > Mobile : 0773661935 > > Lean . Enterprise . Middleware >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
