LivewiresXe
Smash Hero
Venonat? Tsk tsk. For shame.
Welcome to Smashboards, the world's largest Super Smash Brothers community! Over 250,000 Smash Bros. fans from around the world have come to discuss these great games in over 19 million posts!
You are currently viewing our boards as a visitor. Click here to sign up right now and start on your path in the Smash community!
False, snorlaxVenonat >> All. Best Pogeyman, fo realz/
Haha, actually, that was me Woops, uhhh, when would be a good time for me to pick it up?@Bryant: If you're wondering where it went, you left your cell charger here.
I can do this if you know what part you want to work on. If you're looking for something straightforward, I'd suggest working on the GUI side (assuming you don't mind doing GUI code). The Java GUI classes are pretty straightforward to use, there is lots of documentation on them, and it will be pretty simple to debug (you will be able to tell right away if your buttons/menus don't do what they're supposed to ).I think I would have an easier time if I were told "Here are the classes and methods, implement them!". If that's not done though, since the work hasn't been divided up yet or anything, I'll try to cope and ask for direction if I get stuck.
Today/tomorrow are bad due to my stupid midnight-8am shift; it is going to mess up my schedule big time. Thursday is probably bad because I might be out then. Any other weekdays during the evening are fine if you have time to drop by. If your phone can hold out that long, I suggest waiting until Friday, that way you can get your charger and play smash with us!Haha, actually, that was me Woops, uhhh, when would be a good time for me to pick it up?
That sounds good, I think I would prefer to work with the GUIs. I worked with Java GUI classes in grade 12 and I'm unfamiliar with XML. I actually have no idea how idea how Swiss tournaments work either, SAUS informed me it's a type of cheese. I guess I'll find that out.I can do this if you know what part you want to work on. If you're looking for something straightforward, I'd suggest working on the GUI side (assuming you don't mind doing GUI code). The Java GUI classes are pretty straightforward to use, there is lots of documentation on them, and it will be pretty simple to debug (you will be able to tell right away if your buttons/menus don't do what they're supposed to ).
Haha, well to be honest, I think I am going on a road trip this week at some point, and unfortunately, my phone is now dead :D . Not sure when exactly I am/may be going, but if I'm around Ottawa I'll post on here and see when is good for youToday/tomorrow are bad due to my stupid midnight-8am shift; it is going to mess up my schedule big time. Thursday is probably bad because I might be out then. Any other weekdays during the evening are fine if you have time to drop by. If your phone can hold out that long, I suggest waiting until Friday, that way you can get your charger and play smash with us!
For detail id say some basic classes would suffice. Just to understand what each component is supposed to do.If anyone cares, I didn't play this week mostly due to being woken up so much because of work. Also, Dan was there and he doesn't play Brawl, and I didn't want him to sit around and be bored. Additionally, I was a little soul-crushed (props to anyone other than Ben who gets the reference) due to losing to Alan's bottom tier characters with tier ***** characters earlier that evening.
@Bryant: If you're wondering where it went, you left your cell charger here.
Swiss Program stuff
Here are the basics of the different parts of the program I'd want help with:
- Two main GUI screens. The first screen will be similar to the main one in Tio where you add/delete players. The second would be the main Swiss round screen which displays the matches, and where you enter results. There are a couple of other ones that we will need (displaying results for individual players, and for the tournament as a whole) but these shouldn't take as long to do as the main two.
I have them drawn out on paper, and all of it can be done with basic Java GUI components, so it shouldn't be too tricky. We can take a look at this on Friday and if people have some ideas on it, we can take them into account and change them a bit if I've missed something. The main work here would be creating these components and laying them out on the screen (there are Java layout objects that can be used for this).
- XML file saving/loading. I was thinking that we might as well use a standard to save and load the tournament data. Super-motivated people might even be able to use the tournament output XML to do other stuff in other programs (player statistics, head-to-head matchups for two players, etc.). XML is good to learn because it's used in a lot of places (ie: looks good on a resume!).
If anyone is interested in this part, I can help out as I've done XML parsing for a couple of projects.
- Swiss tournament algorithms. Determining how people are paired up in a given round, calculating placements, and things like that. Additionally, how to get all the necessary data from the other system components (getting values from the GUI, getting results and previous matchups from the player data, etc.). I need to work a bit more on this part, as it's the least-developed out of these subsystems. Most of it is only in my head ATM.
Work on these sections can be split up if more than three people end up working on this. For the GUI, one person could work on each main screen; for the XML files, one could work on saving, the other on loading, though they'd have to work together to make sure the same data is being saved and loaded
Ben/Orlando: What are the chances of you guys being able to make it next week? Rather than start coding the Swiss program with what I have now, I was thinking of really hammering out the design more this week. Kevin (aka Kran) didn't post here, but he's back from school now and he's interested in helping out with this as well.
One thing I need to know before I proceed is, what level of detail would you guys want before I proceed? At the moment, I know what the main components are, but I haven't gotten to the stage where I have individual classes and methods all fleshed out yet. Would you guys prefer to design your own classes, methods, etc. for whichever parts you'd work on, or do you want me to come up with all the individual classes and methods that I think we'd need? I can do that, but if you aren't interested in just being told, "Here are the classes and methods, implement them!" I can understand that. Going that far could be kind of control freak-ish, but let me know.
Sounds good. It looks like we have a couple of volunteers for XML anyways, and to be honest I wanted to work on the algorithm stuff myself This works out nicely.That sounds good, I think I would prefer to work with the GUIs. I worked with Java GUI classes in grade 12 and I'm unfamiliar with XML. I actually have no idea how idea how Swiss tournaments work either, SAUS informed me it's a type of cheese. I guess I'll find that out.
*combines with reply to Orlando*I know xml pretty well... it's just tags, but I'm very versed in writing xml parsers and writing the files/objects ... it's not hard, but I do it a lot
anyways, funerals suck, I'll be back, and I cant wait to play you guys (especially the new MK)
Yeah, I thought about these things over the weekend and I think certain classes are necessary to have in advance. I won't go so far as to decide how people split up their own sections, though.For detail id say some basic classes would suffice. Just to understand what each component is supposed to do.
I would combine the loading and saving into one job since they are almost the reverse of each other.
Im pretty much okay with any part, although Ive never used xml extensively but I wouldnt mind learning it. I will most likely be able to make it this week for atleast an hour or two so we can look over the design and discuss any ideas. Probably for some smash as well .
Everyone knows that Shedinja is the coolest bug type which in turn makes him the coolest pokemon ever ever EVER.Venonat >> All. Best Pogeyman, fo realz/
My Magikarp's Splash Attack says otherwise n00b. Plus Shedinja isn't part of the "real pokémon" (original 151). I'd let it pass if it was part of the 251 pokémon but it isn't so you suck.Everyone knows that Shedinja is the coolest bug type which in turn makes him the coolest pokemon ever ever EVER.
I don't mind this personally...anyone remember why Lylat was moved to CP in the first place? The edges? The stage tilting?Jobin's right. There's only Pokemon 1 and 2, all the rest are just, umm, side-quests. It takes more than Prof. Oak to make the games all part of the same series. Ah, the good old days of playing Silver in chemistry class...
On topic: We should add Lylat and Pokémon stadium 1 to the starter lists. All in favor/opposed?
You are challenging the wrong person to an out-camping MM. Sorry Mike, my $'s on Harold. :>Okay, I have to have a MM with Harold, MK vs whoever he picks, on PS1. I *WILL* out camp him, and show him things about that level that will prove it's not starter.
LOLHis sword won't go through the FD lip. It will on PS1.
Watch this: http://www.youtube.com/watch?v=9zPMhGvCyVg
Specifically the PS1 parts. . . against ANTHER.
Grand finalsWhere any matches recorded from this tournament?
Aka. Ariel FinalsSince it was both Losers and Grand, it should be called Grand Loser's Finals =)