OpenUO CVS submissions

Want to discuss changes to the UOX3 source code? Got a code-snippet you'd like to post? Anything related to coding/programming goes here!
Post Reply
Maarc
Developer
Posts: 576
Joined: Sat Mar 27, 2004 6:22 am
Location: Fleet, UK
Has thanked: 0
Been thanked: 0
Contact:

OpenUO CVS submissions

Post by Maarc »

OK, this is aimed primarily at those who have to deal with the CVS, given the topic :)

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 :)
giwo
Developer
Posts: 1780
Joined: Fri Jun 18, 2004 4:17 pm
Location: California
Has thanked: 0
Been thanked: 0

Post by giwo »

Actually, you have hit on precisely what I created OpenUO for.

My original intent was tools, rather than UOX3 itself. Thus yes, /projects/PkgInstaller/ would be perfect.

As for the cpp / csharp division, if one is creating their project with hopes/plans of it being available in multiple distributions, that is fine, otherwise, it's just an additional unnecesarry directory.


On the second topic, I would love to see a general API to help encourage tool developers to write more and better tools for UOX3.
Scott
Maarc
Developer
Posts: 576
Joined: Sat Mar 27, 2004 6:22 am
Location: Fleet, UK
Has thanked: 0
Been thanked: 0
Contact:

Post by Maarc »

OK, source for PkgInstaller and the earlyish stuff for the ToolAPI stuff is committed into the CVS now. I haven't included the sample test zip for the PkgInstaller stuff, I guess I should figure out somewhere to throw it so others can use it :)
Post Reply