Re: [Carbon-dev] Comment from Jonathan on Docrepo/ Registry

[jonathan]

Adding all my comments as JIRAs.  Overcoming my laziness in this regard is
a virtue, right ;-).

-Original Message-
From: hemap...@gmail.com [mailto:hemap...@gmail.com] On Behalf Of Srinath
Perera
Sent: Tuesday, September 29, 2009 7:26 PM
To: carbon-dev@wso2.org
Cc: jonat...@wso2.com
Subject: Re: [Carbon-dev] Comment from Jonathan on Docrepo/ Registry

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,   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:  
> 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 instea

Re: [Carbon-dev] Comment from Jonathan on Docrepo/ Registry

[Senaka Fernando]

On Thu, Oct 1, 2009 at 11:15 AM, Sanjiva Weerawarana wrote:

> On Thu, Oct 1, 2009 at 9:11 AM, Senaka Fernando  wrote:
>
>>
>> OK, I will try to get this done for 2.0.1 if possible.
>>
>
> Uh, what?? The release that's due to go last month, last week and now this
> Friday? NO WAY dude; please don't touch it!!!
>

:).. ok. +1. Let's have this done later..

Thanks,
Senaka.

>
> Code freeze must mean code freeze - otherwise we'll never release anything.
>
> Sanjiva.
> --
> 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
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Comment from Jonathan on Docrepo/ Registry

[Sanjiva Weerawarana]

On Thu, Oct 1, 2009 at 9:11 AM, Senaka Fernando  wrote:

>
> OK, I will try to get this done for 2.0.1 if possible.
>

Uh, what?? The release that's due to go last month, last week and now this
Friday? NO WAY dude; please don't touch it!!!

Code freeze must mean code freeze - otherwise we'll never release anything.

Sanjiva.
-- 
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

Re: [Carbon-dev] Comment from Jonathan on Docrepo/ Registry

[Ruwan Linton]

Senaka Fernando wrote:
>
>
> On Thu, Oct 1, 2009 at 9:02 AM, Sanjiva Weerawarana  > wrote:
>
> On Wed, Sep 30, 2009 at 8:56 PM, Senaka Fernando  > wrote:
>
> Hi Jonathan,
>
> I have fixed the spelling mistake and the session timeout not
> being reflected when adding/editing properties through the UI.
>
> However, regarding the pop-up, I believe that coming up with a
> non-modal alert, would be better but would be inconsistent
> with the remainder of the UI alerts as we display pop-up
> messages elsewhere.
>
> Therefore, what we can do is re-direct the user to the added
> resource/collection which sounds logical, as 95% of the people
> would be interested to see what gets added soon after adding
> something. But, this would be an issue for someone who keeps
> on adding several resources one after the other as he needs to
> go back-and-forth.
>
>
> Senaka, IMO in most cases you're not adding lots of collections ..
> and if you add one you want to add stuff into that collection
> next. So I think we should do what Jonathan suggested as the default.
>
>
> OK, I will try to get this done for 2.0.1 if possible.
2.0.1  Aren't we let this release go out :-(

Ruwan
>
> Thanks,
> Senaka.
>
>
> Sanjiva.
> -- 
> 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
>
>
> 
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>   


-- 
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org



___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Comment from Jonathan on Docrepo/ Registry

[Senaka Fernando]

On Thu, Oct 1, 2009 at 9:02 AM, Sanjiva Weerawarana wrote:

> On Wed, Sep 30, 2009 at 8:56 PM, Senaka Fernando  wrote:
>
>> Hi Jonathan,
>>
>> I have fixed the spelling mistake and the session timeout not being
>> reflected when adding/editing properties through the UI.
>>
>> However, regarding the pop-up, I believe that coming up with a non-modal
>> alert, would be better but would be inconsistent with the remainder of the
>> UI alerts as we display pop-up messages elsewhere.
>>
>> Therefore, what we can do is re-direct the user to the added
>> resource/collection which sounds logical, as 95% of the people would be
>> interested to see what gets added soon after adding something. But, this
>> would be an issue for someone who keeps on adding several resources one
>> after the other as he needs to go back-and-forth.
>>
>
> Senaka, IMO in most cases you're not adding lots of collections .. and if
> you add one you want to add stuff into that collection next. So I think we
> should do what Jonathan suggested as the default.
>

OK, I will try to get this done for 2.0.1 if possible.

Thanks,
Senaka.

>
> Sanjiva.
> --
> 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
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Comment from Jonathan on Docrepo/ Registry

[Senaka Fernando]

On Thu, Oct 1, 2009 at 9:00 AM, Sanjiva Weerawarana wrote:

> On Thu, Oct 1, 2009 at 8:37 AM, Srinath Perera  wrote:
>
>> > Regarding the loss in connection with the BE; this can be due to several
>> > reasons ranging from DB un-availability, loss of network connectivity,
>> > inadequate permissions etc. I'm +1 for retrying to establish the
>> connection
>> > with the BE. How about an additional "Do you want to retry to connect to
>> the
>> > BE?" option along with the error message?
>>
>> IMO we should just retry. Rule of thumb is that "do not ask questions
>> from users which they do not know answer for", and in this case, they
>> have zero information to make that decision. And if he said NO, there
>> is nothing really we can do by keeping him logged in.
>>
>
> Absolutely +1. We should only inform the user if after say 2-3 retries we
> just can't keep it up.
>

I was in doubt about having the question initially. Right now our UI
permission model is not flexible enough to disable menu items if you don't
have permissions to browse a resource on the registry. So, I guess when we
have that in place as well, this should be ideal, so that the retry would
actually happen when there is a network outage.

For the moment I will implement 2 retries (3 tries altogether), before the
error message.

BTW, how long do we need to wait per retry? Each call should complete within
60s in a default configuration, so the total time spent before the second
retry should be less that 10-15s, IMHO.

Thanks,
Senaka.

>
> Sanjiva.
> --
> 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

Re: [Carbon-dev] Comment from Jonathan on Docrepo/ Registry

[Sanjiva Weerawarana]

On Wed, Sep 30, 2009 at 8:56 PM, Senaka Fernando  wrote:

> Hi Jonathan,
>
> I have fixed the spelling mistake and the session timeout not being
> reflected when adding/editing properties through the UI.
>
> However, regarding the pop-up, I believe that coming up with a non-modal
> alert, would be better but would be inconsistent with the remainder of the
> UI alerts as we display pop-up messages elsewhere.
>
> Therefore, what we can do is re-direct the user to the added
> resource/collection which sounds logical, as 95% of the people would be
> interested to see what gets added soon after adding something. But, this
> would be an issue for someone who keeps on adding several resources one
> after the other as he needs to go back-and-forth.
>

Senaka, IMO in most cases you're not adding lots of collections .. and if
you add one you want to add stuff into that collection next. So I think we
should do what Jonathan suggested as the default.

Sanjiva.
-- 
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

Re: [Carbon-dev] Comment from Jonathan on Docrepo/ Registry

[Sanjiva Weerawarana]

On Thu, Oct 1, 2009 at 8:37 AM, Srinath Perera  wrote:

> > Regarding the loss in connection with the BE; this can be due to several
> > reasons ranging from DB un-availability, loss of network connectivity,
> > inadequate permissions etc. I'm +1 for retrying to establish the
> connection
> > with the BE. How about an additional "Do you want to retry to connect to
> the
> > BE?" option along with the error message?
>
> IMO we should just retry. Rule of thumb is that "do not ask questions
> from users which they do not know answer for", and in this case, they
> have zero information to make that decision. And if he said NO, there
> is nothing really we can do by keeping him logged in.
>

Absolutely +1. We should only inform the user if after say 2-3 retries we
just can't keep it up.

Sanjiva.
-- 
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

Re: [Carbon-dev] Comment from Jonathan on Docrepo/ Registry

[Srinath Perera]

> Regarding the loss in connection with the BE; this can be due to several
> reasons ranging from DB un-availability, loss of network connectivity,
> inadequate permissions etc. I'm +1 for retrying to establish the connection
> with the BE. How about an additional "Do you want to retry to connect to the
> BE?" option along with the error message?

IMO we should just retry. Rule of thumb is that "do not ask questions
from users which they do not know answer for", and in this case, they
have zero information to make that decision. And if he said NO, there
is nothing really we can do by keeping him logged in.
--Srinath



>
> Bouncing back to where you were after a session timeout is a key improvement
> that we are hoping to add. This is also required by notifications etc, as
> the current model doesn't allow sending any link within an e-mail
> notification since it becomes meaningless unless you are logged in.
>
> Thanks,
> Senaka.
>
> On Wed, Sep 30, 2009 at 8:03 AM, Sanjiva Weerawarana 
> wrote:
>>
>> +1.
>>
>> On Wed, Sep 30, 2009 at 7:55 AM, Srinath Perera  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,   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
>

Re: [Carbon-dev] Comment from Jonathan on Docrepo/ Registry

[Senaka Fernando]

Hi Jonathan,

I have fixed the spelling mistake and the session timeout not being
reflected when adding/editing properties through the UI.

However, regarding the pop-up, I believe that coming up with a non-modal
alert, would be better but would be inconsistent with the remainder of the
UI alerts as we display pop-up messages elsewhere.

Therefore, what we can do is re-direct the user to the added
resource/collection which sounds logical, as 95% of the people would be
interested to see what gets added soon after adding something. But, this
would be an issue for someone who keeps on adding several resources one
after the other as he needs to go back-and-forth.

So, IMHO both of the proposed improvements have pros and cons.

Regarding the loss in connection with the BE; this can be due to several
reasons ranging from DB un-availability, loss of network connectivity,
inadequate permissions etc. I'm +1 for retrying to establish the connection
with the BE. How about an additional "Do you want to retry to connect to the
BE?" option along with the error message?

Bouncing back to where you were after a session timeout is a key improvement
that we are hoping to add. This is also required by notifications etc, as
the current model doesn't allow sending any link within an e-mail
notification since it becomes meaningless unless you are logged in.

Thanks,
Senaka.

On Wed, Sep 30, 2009 at 8:03 AM, Sanjiva Weerawarana wrote:

> +1.
>
>
> On Wed, Sep 30, 2009 at 7:55 AM, Srinath Perera  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,   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 popu

Re: [Carbon-dev] Comment from Jonathan on Docrepo/ Registry

[Sanjiva Weerawarana]

+1.

On Wed, Sep 30, 2009 at 7:55 AM, Srinath Perera  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,   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:  
> > 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 il

Re: [Carbon-dev] Comment from Jonathan on Docrepo/ Registry

[Srinath Perera]

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,   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:  
> 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

Re: [Carbon-dev] Comment from Jonathan on Docrepo/ Registry

[jonathan]

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:  
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

Re: [Carbon-dev] Comment from Jonathan on Docrepo/ Registry

[jonathan]

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:  
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

Re: [Carbon-dev] Comment from Jonathan on Docrepo/ Registry

[jonathan]

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:  
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