SpringLobby
Moderators: Moderators, Lobby Developers
-
Complicated
- Posts: 369
- Joined: 06 Jun 2007, 18:51
Well, I finally got it working. After installing countless Libraries....I don't even want to think about attempting to recreate the list....(most probably usless)
Anyway. I think the design is good.
I'm going to have to agree with Brain Damage that the /join command should be available from the chat window.
The only other thing that stood out to me what the exit button for all the tabs is it's own tab. It'll work, but it seems kinda weird. Could you put the tab on each window itself?
There's more, but I don't want to say anything till I see the "finished" version, since I'm sure you'll add some more to come. Good work :)
Anyway. I think the design is good.
I'm going to have to agree with Brain Damage that the /join command should be available from the chat window.
The only other thing that stood out to me what the exit button for all the tabs is it's own tab. It'll work, but it seems kinda weird. Could you put the tab on each window itself?
There's more, but I don't want to say anything till I see the "finished" version, since I'm sure you'll add some more to come. Good work :)
cong06: The /join command is going to be there in time, the only reason it's not there yet is because I want to prioritize the battles. The chat is working allready, though not yet complete. Added a ticket on trac for it, so anyone who feels like it can submit a patch for it.
The close tab was not my first choice ether, but didn't find a nive way to do it with wxWidgets just yet. If anyone can give me a general idea of what events and so on to use I would appriciate it.
If you have any sugestions to improve things, feel free to post them here, I'm working on this client in hopes that it will become something people other than just myself will like, and so sugestions are important.
The close tab was not my first choice ether, but didn't find a nive way to do it with wxWidgets just yet. If anyone can give me a general idea of what events and so on to use I would appriciate it.
If you have any sugestions to improve things, feel free to post them here, I'm working on this client in hopes that it will become something people other than just myself will like, and so sugestions are important.
That's what I figured. thought I'd bring it up in any case.tc- wrote: The close tab was not my first choice ether, but didn't find a nive way to do it with wxWidgets just yet. If anyone can give me a general idea of what events and so on to use I would appriciate it.
good luck. I'm excited for what's to come.-
clericvash
- Posts: 1394
- Joined: 05 Oct 2004, 01:05
For Lobby++ I just tied a mouse handler function to the channel notebook which closes a tab when a double-rightclick event occurs, it didn't seem possible to have special controls within tab bars a la Firefox (version 2.0 ).
).
Last edited by Kloot on 10 Jun 2007, 21:29, edited 2 times in total.
The X tab sucks UI-designwise. The GUI toolkit used should provide this function in the tab bar. I believe that Qt does, but this clearly hasn't became the standard in other toolkits yet, as dynamically changing tabs are quite new.
I like the idea of a separate exit channel button, perhaps in the top toolbar (that does not exist yet). Does anyone know if it is a good practice to have context-specific buttons in toolbars (which is equivalent to having context-specific options in the menu)? I don't remember reading a mention of this in any HIG.
I like the idea of a separate exit channel button, perhaps in the top toolbar (that does not exist yet). Does anyone know if it is a good practice to have context-specific buttons in toolbars (which is equivalent to having context-specific options in the menu)? I don't remember reading a mention of this in any HIG.
It's kinda nice to be able to close a tab without switching to it, though I guess when you're only dealing with a few chat rooms it's not as big a deal as it is with firefox, for example, and 20 different windows open.AF wrote:Because closing with a rightclick is a horrendous way of doing things from a UI design perspective.
Do what i did and add an exit channel button.
err, click a big red button and the tab goes, nobody mentioned switching to the tab then closing it.
Its a much better solution for a UI design perspective because every browser has the same thing, its convention, its a cultural norm and a common practice. I havent implemented ti in AFLobby because it requires java 6 and most users cba upgrading and dont realize the java 1.1 they installed in the 90s has been updated. Java allows any arbitrary component to be inserted into a tab.
What is there to tell the user that to exit a channel they have to right click on the tab? Should a label be added to tell them and make it better? Perhaps the space used by the label would be better used by an exit current channel button? Not everyone will have used tasclient, so we cant rely on tasclients UI norms, which are already horrendous. Tasclient is a UI design travesty, we should be learning from its mistakes not repeating them.
Keeping the double right click feature is a good diea and Ill copy that fi you dont mind, but it isnt enough by itself. Its a tasclient customization for tasclient users transfering, itll confuse the hell out of new users if something else isnt added to help.
Its a much better solution for a UI design perspective because every browser has the same thing, its convention, its a cultural norm and a common practice. I havent implemented ti in AFLobby because it requires java 6 and most users cba upgrading and dont realize the java 1.1 they installed in the 90s has been updated. Java allows any arbitrary component to be inserted into a tab.
What is there to tell the user that to exit a channel they have to right click on the tab? Should a label be added to tell them and make it better? Perhaps the space used by the label would be better used by an exit current channel button? Not everyone will have used tasclient, so we cant rely on tasclients UI norms, which are already horrendous. Tasclient is a UI design travesty, we should be learning from its mistakes not repeating them.
Keeping the double right click feature is a good diea and Ill copy that fi you dont mind, but it isnt enough by itself. Its a tasclient customization for tasclient users transfering, itll confuse the hell out of new users if something else isnt added to help.
I agreeAF wrote: we should be learning from its mistakes not repeating them.
I think the best solution is to have some kind of "leave" button as sugested by AF and also be able to dubble click. Where the "leave" button is located there could also be other buttons with other channel functions so it will not be a complete waste of space. This toolbar should be optional and some may want to remove it and stick with only dubbleclick. Maybe?
of course the more options the user has, the more bloated the program is, so let's not forget that.AF wrote:we should use it as default btu of course give the user a choice when possible.
One other thing I noticed though, while we're speaking of user options, is the ability to sort the battle list. That's kinda a nice feature in the TASClient.