Re: offtopic: best way of plainng overall structure of programs/functions etc.
Re: offtopic: best way of plainng overall structure of programs/functions etc.
- Subject: Re: offtopic: best way of plainng overall structure of programs/functions etc.
- From: Kuon <email@hidden>
- Date: Sun, 05 Aug 2007 13:16:04 +0200
On 5 Aug 2007, at 1:40 AM, Stephan Huebner wrote:
Hi all,
Would love to hear suggestions how to solve this problem and once
again, sorry for the offtopic.
Hi,
I am currently working on a big project as leader programmer (an MMO
game) and if I can summarize the process:
- Trying to visualize all part of your programme (Platform
abstraction, interface, graphics, network...) and do a list.
- Then parse your list and imagine all code part, if one part is not
clear to you (in our project, we weren't sure of what to use for
interface, and we ended with lua), do an example, seek sample code if
you have no clue, document yourself.
- When you have a list of all part of your programme (a good way, in
case of a game, is to imagine the input-outputs and the user
experience, for example, imagine how you will grab mouse, where it
will go... and for the user, imagine what he will have on his screen
when playing, and isolate each components)
At this point, you should have a precise idea of the content of your
programme, and a precise idea of the form of each part (we will use
OpenGL + GLSL (we know both, have long experience with GL, so OK!),
we will use lua for interface (we did a sample integration programm,
with a sample interface on top of OpenGL, so OK!), we will use UDP
for network, to drive position of ships and all, and TCP for
informations (missions, chat...) (we got a team of dedicated network
coder, so OK!)... so, a precise form of each part and precise content
of your programme, but the form of your programme (how the interface
will drive the network...) is still rough at that point.
Here come the architecture, this is where you will put all elements
together, personally, I do it inside my brain, but this is based on
experience, and I'm unable to use paper for anything.
If this is your first serious job, I suggest you try to visualize
your programme, if you need omnigraffle, a paper, a mind map or
anything, use what fits you better. If this is a cocoa programme, you
might want to draw the interface on paper, or create it with
interface builder, imagine what the user will do, and put a piece of
logic (code if you can), behind user actions. Like, the user click
the login button, this will send a message to the network thread, and
it will try to log in, and you must, when you think about that, be
sure you will know how to implement all parts.
I know this is really a rough explanation with no real structure, but
except for the basics where you have to learn the syntax and all,
programming is all about experience and trying all things you can
imagine. Doing mistakes is important.
I hope I was able to guide you a bit, if you have any question, I
would be delighted to help.
Regards
--
Kuon
"Don't press that button."
http://goyman.com/
Blog: http://kuon.goyman.com/
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden