One of the things that has come to light, as far as I can see, is the need for more tools, more reusable code, and so on.
I have finished a first pass attempt at the PkgInstaller (currently C# only, anyone who wants it I can happily provide it to, source + exe + example), and I will need others to test it. But it seems to do the job.
Anyway, I realise we don't want the OpenUO CVS cluttered up too much, but is it worth putting tools such as PkgInstaller (and any others that might be developed) into the CVS under it's own branch? IE rather than just projects/uox3, you could have something more like:
projects/uox3
projects/PkgInstaller
projects/ToolAPI
and so on.
I'm happy enough to throw my work in there, *if* that is what people want. And by separating it somewhat from uox3 (side by side, not inside), it means people can only update the parts they need to. Thoughts? Ideas? Suggestions?
If this is accepted (no means guaranteed), I would also suggest that, for tools like PkgInstaller, that we adopt something like this:
projects/PkgInstaller/csharp
projects/PkgInstaller/cpp
etc
So if there are multiple platforms/multiple implementations, they sit side by side, rather than spread into multiple other locations.
Also, as part of PkgInstaller, I have a UOXData project/DLL (C# currently) that could be reused by other tool developers. It contains, essentially, an abstract implementation of things like Script/ScriptSection and World/WorldSection, to help with reading/parsing such things.
Anyway, just some thoughts. Take it as you will