Re: krdc ui, looking for suggestions

On Sunday 12 July 2009 21:50:53 Tony Murray wrote:
> Ok, I think I have a pretty good layout here:
> http://imagebin.ca/view/ElbGDS.html

Yeah, I like it! I like to revamp of the tab behavior. There has always been 
some complains about the not-very-standard-conform behavior. I think that 
should fix it.

> 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 have just fixed this behavior today in trunk. It works with the current 
interface.

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

It's probably an idea, but IMHO not part of the first step. Keep it in mind. 
And we should make this feature optional.

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

Great idea.

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

I think that layout should solve some issues. It's a quite big change also in 
view of users.

I have already a first half-way working draft  version of this UI done in the 
last hour. Still WIP.

Also, I still would like to add a "screenshot"-buttons of the last openend 
sessions, like Opera or Chrome (speed dial). Not sure how to do these best in 
Qt (getting screenshots is no problem, but layout). Any ideas on that?

Also we need to merge the "browse network model" into the RemoteDesktopsModel 
in order to drop the own tab.

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