Re: [Once development] Programming tasks

[Wouter W. <wca...@dd...>]

Thomas Clive Richards wrote:

>>Hi,
>>    
>>
>
>hey!
>  
>
>>I sent an email to wouter, but I guess he's really busy at the moment.
>>I've looked over the code and crystal space, but I don't think I'll
>>ever really know what I'm doing until I actually do something. Is
>>there anything simple that you guys need coded, because I'll start
>>there.
>>
>>
>>    
>>
>
>Wouter not replying to emails is a problem, as he's currently the only
>one who knows the ins and outs of the code; I certainly don't!
>  
>
Woops, sorry about that. If my lack of email-reply-speed is a problem 
for the project, then in due time it may be wise to appoint someone else 
in charge of the code?
[I am simply unable to reply quickly to email, I don't think I can 
change that (my employer)].

>I do however have a small feature request, and it's so simple i think
>even *i* could code it ;)
>
>it'd be good to have some command line switches, including:
>
>-p n --port=n	#this specifies which port the server listens on. at the moment
>this port is set on line 212 of ocserver.cpp. when this flag is set, the
>server should listen on port `n`
>-h --help	#list a help text of options (currently only these two), and
>exit.
>  
>
Note that crystalspace can help you read the commandline options.

>I'll get onto wouter about giving you something more rewarding to do ;)
>
>sorry about this ;)
>
>  
>
Ok the next milestone to reach is mostly inside the server:
- a player when he connects needs to be subscribed to 'interesting' entities
- updates of those entities need to be kept track of
   - the objects need to keep their changenumber updates of changes (a 
Changed() method).
   - the subscriptionlists need to be kept uptodate - code for 
subscriptions is already there in part.
- the updates in subscriptionlists need to be sent to a player over the 
network connection.
  objects can already be serialized.
- the client needs to keep track of objects received. (deleting on a 
delete/unsubscribe-message, creating on a subscribed-message, and 
updating objects when they get sent).

When this works, then you can connect and notice changes to objects.
After that the next milestone will be to make the content-file transfer 
functionality, so the client can download artwork files (and display 
them). The client needs to cache the artwork (per Area a folder) in 
clientdata/.

I'd suggest to give any programmer that asks CVS access (because 
anonymous access is too funky). Tullisti, can you do this? Note that 
SF.net may need 8 hours or so to pick up the access-grant.

And then the tasks above can be worked on by anyone who wants to.
I fixed cvs so it compiles, thanks Matthew.

Best regards,
       Wouter