+1. On Wed, Sep 30, 2009 at 7:55 AM, Srinath Perera <srin...@wso2.com> wrote:
> Hi All; > > Should we add these as JIRAs against registry? Can registry team > comment on any things here that should not fixed. IMO all other should > go in as JIRAs. > > Thanks > Srinath > > On Wed, Sep 30, 2009 at 5:33 AM, <jonat...@wso2.com> wrote: > > I'm also encountering "Unable to Browse Registry. User is not autherized > > or the connection with backend registry has been lost" frustratingly > > often. > > > > - Have others encountered this issue? Maybe something to do with the > > Amazon deployment? > > - When this error occurs, it takes me back to the registry root and the > > back button doesn't seem to work. Meaning a long process to get back to > > where I was in the tree. Could we instead try to connect the backend > > again without losing the context? > > - How about spelling "authorized" correctly? > > > > -----Original Message----- > > From: jonat...@wso2.com [mailto:jonat...@wso2.com] > > Sent: Tuesday, September 29, 2009 2:47 PM > > To: carbon-dev@wso2.org > > Subject: RE: [Carbon-dev] Comment from Jonathan on Docrepo/ Registry > > > > Nother possible improvement: > > > > When editing the value of a property, but after the login has expired, > the > > property value is not updated - yet no warning is surfaced as to why. > > > > It also is quite annoying that when the login expires, I must not only > log > > in, but navigate back to where I came from. A bounceback would be very > > nice in this case - so it takes me to the login just long enough to > > represent my credentials, and then returns me directly back into my > > workflow. > > > > -----Original Message----- > > From: jonat...@wso2.com [mailto:jonat...@wso2.com] > > Sent: Monday, September 28, 2009 4:54 PM > > To: carbon-dev@wso2.org > > Subject: RE: [Carbon-dev] Comment from Jonathan on Docrepo/ Registry > > > > More usability comments: > > > > When adding a new collection, a pop up announces "successfully added new > > collection." Shortly thereafter, the collection appears in the main > > Entries pane, but the popup must be dismissed before accessing it. Two > > ways this could be improved: > > - Lose the popup, use some non-modal indicator that the registry is > > working to add the new collection. > > - If this isn't possible, add another button to the popup to "open" the > > new collection's page directly (95% of users will probably do this next.) > > This would replace two clicks - to close the popup and then to open the > > collection. It would also mask a bit the fact that the popup has no real > > utility to the user. > > > > I don't really like the unfortunate combination of inline creation (Add > > Resource opens up a new subpane) and completing a task (a popup). The > > former indicates the interaction will be non-modal, but then the popup > > wrecks that expectation. > > > > > > -----Original Message----- > > From: carbon-dev-boun...@wso2.org [mailto:carbon-dev-boun...@wso2.org] > On > > Behalf Of Srinath Perera > > Sent: Friday, September 25, 2009 8:36 PM > > To: carbon-dev@wso2.org > > Subject: [Carbon-dev] Comment from Jonathan on Docrepo/ Registry > > > > In reality these are comments to registry, and I am forwarding this > > mail to carbon dev for our registry team to answer. > > > > I tried to browse as admin, but not see any tags. Will check with > > registry guys about this. > > > > For registry team: > > > > Following are comments from Jonathan on doc repo, but reality they > > are comments about registry. Could you guys comment? > > --Srinath > > > > > > ---------- Forwarded message ---------- > > From: <jonat...@wso2.com> > > Date: Sat, Sep 26, 2009 at 6:45 AM > > Subject: Re: [Bizdev] doc repo finalization > > - Hide quoted text - > > To: biz...@wso2.com > > > > > > Few fit-n-finish items as I come across them: > > > > - Dependency tree browser: > > > > o Always opens at the root - wouldn't it often be better to have it > > open to the current location? > > > > o Selecting a dependent resource fills in the url, user must still > > click OK. Then he must click Add in the main window. Why are two > > confirmations necessary? Either one should suffice. > > > > - Dependency tree viewer: > > > > o Paths are shortened to illegibility, despite the fact that they > > only take up half the line. If shortening must occur, do it in the > > middle of the path so the final path segment is visible. > > > > o Not sure how this is representing transitive dependencies. > > A->B->C shows as flat items instead of a hierarchy? > > > > - How to delete a tag? > > > > - If a resource has tags, comments, properties, dependencies > > - can we expand those panels by default? Instead of the user > > searching through all of them to see what's defined on the resource? > > > > - It bugs me to rename files when uploading - I can see > > removing #, but parens? Why is this restriction necessary? > > > > > > -- > > ============================ > > Srinath Perera, Ph.D. > > WSO2 Inc. http://wso2.com > > Blog: http://srinathsview.blogspot.com/ > > > > _______________________________________________ > > Carbon-dev mailing list > > Carbon-dev@wso2.org > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > _______________________________________________ > > Carbon-dev mailing list > > Carbon-dev@wso2.org > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > -- > ============================ > Srinath Perera, Ph.D. > WSO2 Inc. http://wso2.com > Blog: http://srinathsview.blogspot.com/ > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; cell: +1 650 265 8311 | +94 77 787 6880 blog: http://sanjiva.weerawarana.org/ The Open Source SOA Company
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
