Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment  
Arkantos

Avatar / Picture

Registered:
Posts: 457
Reply with quote  #1 
For those who are interested in creating custom client software to run with Artemis, I'm planning on publishing ArtClientLib as a Maven artifact. This is something I've never fiddled with before so it may take a little while, but when completed it will mean that you'll be able to simply update your pom.xml file to import ArtClientLib into your project.

At the same time, I'm considering renaming the project. ArtClientLib was originally created by a different author, and was only capable of acting as a client. Since then I've made huge changes to the project, including adding the ability for it to act as a server. This allows you to create man-in-the-middle setups that can inject custom behavior into the game. As such, the "client" part of the ArtClientLib name is something of a misnomer now, as it can do more than just act as a client. I'm not sure if I want to bother renaming the project or not, and what to name it if I did; I'd welcome your thoughts.
Arkantos

Avatar / Picture

Registered:
Posts: 457
Reply with quote  #2 
I'm thinking I probably will change the name, as in order to publish the Maven artifact I will have to give it a group ID, and as I don't have any control over the dhleong.net domain, I probably shouldn't use net.dhleong for the group ID. And if I'm changing the group ID, then I should change my package names to match, and if I'm doing that, I might as well rename the whole dang thing.

The name I'm leaning towards is Interface for Artemis Networking, or IAN, mainly because it makes sense, describes what it is, and the acronym nicely forms a name.
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.