OK... so first thing I need to do then is peer into the message template file. Thanks for the help.Btw, awesome work by all so far. This will prove important to many people. On 10/28/06,
Jesse Nesbitt <[EMAIL PROTECTED]> wrote:
On 10/28/06, Ryan Gahl <[EMAIL PROTECTED]> wrote:> Couple of points he
On 10/28/06, Ryan Gahl <[EMAIL PROTECTED]> wrote:
Couple of points here... first of all, how many packet classes are there
really? 500+?? While that seems like a lot of files (actually it is quite a
lot)... this is a common practice for things like a data access layer (1
file/class per database t
Couple of points here... first of all, how many packet classes are there really? 500+?? While that seems like a lot of files (actually it is quite a lot)... this is a common practice for things like a data access layer (1 file/class per database table) in a multi-tiered architecture. It's certainly
I see another problem with this as well: VS wouldn't know what all the
packets were, so adding/deleting would require a manual solution file
change.
On 10/28/06, John Hurliman <[EMAIL PROTECTED]> wrote:
Ryan Gahl wrote:
> Hello all. I understand busy is busy... but I have a huge request,
> somet
Ryan Gahl wrote:
Hello all. I understand busy is busy... but I have a huge request,
something that would vastly enable people to more quickly grok working
with the various packet classes...
Please, let's consider chaning the autogeneration process to break out
the huge __Packets__.cs file int
There are WAY too many packets for this to work properly.
All of the Packet classes are *really* easy to work with, and more or
less contain the same code. Therefore, breaking it up into class files
wouldn't help.
I recomend you check out my AnimationSample if you need help creating
and sending pa
I'm also in favor of doing it Java style: one file per public class. :-) However, it would take some time and effort for whomever undertakes the task.
On 10/27/06, Ryan Gahl <[EMAIL PROTECTED]> wrote:
Hello all. I understand busy is busy... but I have a huge request, something that would vastly e
Hello all. I understand busy is busy... but I have a huge request, something that would vastly enable people to more quickly grok working with the various packet classes...Please, let's consider chaning the autogeneration process to break out the huge __Packets__.cs file into 1 file per class in a
