Re: krdc ui, looking for suggestions

Ok, I think I have a pretty good layout here:  http://imagebin.ca/view/ElbGDS.html

When you push the New Connection button, it opens a new tab and focuses to the input box.  If there is already a New Connection tab, it brings that to the front and focuses the input box.  This maintains the current one click, type, one click to initiate a connection.  It also allows the most amount of screen to display bookmarks/history/browse, but only shows them when you want to make a new connection.

Initially, there will be no tabs shown.  When you start a second connection, the tabbar will appear.  When you disconnect down to one connection, it will disappear again.

I do like the idea of automatically trying all protocols after a failure.  I'm not sure if the protocol selector still makes sense if we can do this.

One really nice benefit of this layout is we can add a new connection button in the fullscreen toolbar and allow the user to open up this screen and initiate a new connection without switching out of fullscreen.

Ok, so what problems are there with this layout?  Are they only minor problems?

Tony Murray
_______________________________________________
kde-usability mailing list
kde-usability@xxxxxxx
https://mail.kde.org/mailman/listinfo/kde-usability