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 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 folder called "Packets"... This is theoretically not a very hard change to make, and I'm sure I'll end up doing it on my own and maintaining my local copy that way if the team doesn't agree this is a good idea... but overall the community here would benefit because it's not currently possible to leisurely scroll down that file to browse all the available classes and their members, it's just too big.

John, please give this some thought. I think it would really speed things along. Thanks.

--
Ryan Gahl
Application Development Consultant
Athena Group, Inc.
Inquire: 1-920-955-1457
Blog: http://www.someElement.com

_______________________________________________
libsecondlife-dev mailing list
libsecondlife-dev@gna.org
https://mail.gna.org/listinfo/libsecondlife-dev
http://www.libsecondlife.org/




--
Tom Wilson
[EMAIL PROTECTED]
KI6ABZ
_______________________________________________
libsecondlife-dev mailing list
libsecondlife-dev@gna.org
https://mail.gna.org/listinfo/libsecondlife-dev
http://www.libsecondlife.org/

Reply via email to