hpox

Members
  • Content count

    330
  • Joined

  • Last visited

Community Reputation

122 Neutral

About hpox

  • Rank
    Member
  1. 3d meets 2d simplicty?

    Sure, Facewound
  2. Since he's banned, I'm going to guess that guy was a gimmick and he rated himself up.
  3. Good post, thank you. The first view is what I was looking for yesterday when I posted this thread. The second view is totally in line with what I managed to design on my whiteboard later using my understanding of OO. I wasn't sure about all the "duplicated" domain objects on both the client and the server but with Proxy, it make sense. What's important here is a solid interface/protocol between the server and client.
  4. There's a lot of info on the net about simple straightfoward networking such as sending bytes, strings and numbers, Client to Server. But where's the info about networking in an object-oriented approach? I found some stuff but it's either too vague or too heavy. RPC is ancient, Java RMI seem insecure and CORBA is overhead happy. I just read about these solutions so my opinions are probably inacurate. Is there a way to network programming that is light and OO? I just can't seem to wrap my head around an MVC architecture and the network tools we have: Let's say it's a simple turn-based wargame. My client have a View (GUI) and a Controller. My server is the Model and it have an interface for receiving commands from the controller and have all the domain objects that represent the real-world objects of the game. The View in the client observe the domain objects (which are observable) The client call a method moveArmy(Army, TargetZone) on the Game (server-side), the Game modify the domain objects. Ok, first of all, if the objects are server-side, how can the Client have references to the objects? When the object are modified, they will have to notify the View via the Observer interface. That works perfect in a non-network, but since the View is located on the client, it's a remote object. So the client needs to serve it's View by implementing a Remote Interface or something like that? Last question. Is Object-oriented networking used in games much or is it still procedural with very tight coupling between server and clients? Obviously, the advantage of OO here is that once the network module/architecture is done, programming the game is a breeze and everything is very flexibe/extensible. I should "Just Do It!" and figure it out by making mistakes... If you have any answers, please post. I'll update with info as I figure this out. [Edited by - hpox on June 14, 2005 8:33:21 PM]
  5. IDE hell...

    Eclipse is bliss
  6. That's rich, he just pasted the assignement, not even bothering to add a message.
  7. Bravo. That's a very nice and complete design document. It's not just the beautiful graphics and presentation either! This is an amazing example of how to make a design document. I thank you very much for sharing this with us. PS: Nintendo should really contact you asap before Sony does.
  8. They get Puyo Puyo in Viet Nam while here I have to follow Unified Process to develop frickin Boggle.
  9. Quote:Original post by silverphyre673 Yes! I have homeworld 2 on my compy, but although I like it a lot, I play star fox (SNES) just as often. But aren't they both 3d games ???