Network Messaging / News: Recent posts

The IRC client for Myth, known as thIRC is in its first official release!

Although it was written for Myth, it has additional features when used in Network Messaging 2.

This is the first official release, releases prior to this have been incomplete and buggy. This is the first one that I am at a loss to find bugs or easily implement additional features.

Notes: User list is very simplistic, its just a textbox for now
You may only be in 1 channel at a time. Currently. Multi-windowed versions of thIRC are upcoming.... read more

I have finally crafted a WORKING ProtocolV1 (Network Messaging 1) client in Network Messaging 2.

The client uses a large Myth script, created in the Myth IDE to connect to a NM Service server and communicate with other clients on it, who may or may not be using Network Messaging 2.

--
Next up, an IRC client will be crafted!

I finally have a working implemtation of the Myth scripting language (http://www.sourceforge.net/projects/myth/) in Network Messaging 2!

One of the major goals of Network Messaging 2 has always been to include a robust scripting language, so much so that development all but stopped on this project until Myth was a reality.

With Myth now working, it has been implemented into Network Messaging 2. I have yet to convert any code to scripts, but the old plugin system has been scrapped and Myth has been put in.
The samples provided in the Plugins directory are the same as those provided in the Myth project, and work identifcally.... read more

I decided to upload my changes. God I'm slack.
Enjoy :)

Ok, I'm getting slack with uploading sources.
Anyway, the latest update for NetworkMessaging2 has arrived, but be warned it is still in BETA as the databases still dont work entirely properly.
Just checkout the ChangeLog :)
Also, a form template has been included for child windows, so feel free to add your own windows and features to the program. Do try to hold off though, or at least make changes script compatible (as best you can), as I intend to replace half the code with scripts.
Anyway, enjoy it, it's my pet :)

The first thing on the list was: changing the release name of Bridge.
You may have noticed that all my previous releases were called 'bride-0xxxxxx' - this was due to carelessness on my part.
Onto bigger news, the latest versions of NetworkMessaging 2 have been released!
Read the changelog for a full update :)

The very first working version of Bridge was released late last night (around 2am). Since it was so late I didnt post any news about it, but here it is now!
Combining the base of Bridge with the guts of QBridge, I formed what is now Bridge, a multi-port multi-client program that connects one system to another. An example of this is a server setup on a private network. The computer thats connects to the internet can run Bridge, forward all the ports to the computer on its network and then anyone outside of the network can access the server.
It could also be used to reroute data from one computer to another, even over the internet.
Last night I uploaded 2 versions, bridge-0.02.0001 (the very first working version) but since it had unimplemented features, I took to writing again.
So I uploaded version 0.02.0002, a revamped version with the missing features removed and a revamped interface.
Today, along with this news post, I have uploaded the most recent version - 0.02.03. This has fixed a few bugs I didnt previously notice and some memory leaks. Check the changelog for details.
If there are any problems, email me or post a message in the forums.

The first BETA of Bridge is being released so people can see its progress.
Currently, it's not much to look at, and doesn't actually route anything yet. This is due to the fact that I made it too complex from the beginning. I'm going to rewrite the class modules to act as QBridge does but in a slightly more advanced way.

In what could be the shortest programming time ever, I have created QBridge.
Currently in beta release (0.0.1), it only supports one client at a time.
It simplies accepts a connection from one computer and sends all data to another computer. This can be useful on a closed network: one computer connects to the internet and the rest are on a private network (192.168.*.*). Connections to specific ports can be made to the computer connected to the internet and that computer can route that information to a computer on its private network.
This is the precursor to Bridge, currently in development which will support multiple connects to specific ports as well as an unlimited number of ports that can be selected or unselected for routing at any time.
FYI, Bridge is still not functional after several weeks while I completed QBridge in 2 hours.

The source for Network Messaging 1 is provided for historical purposes. It has evolved as much as possible in the 2 years I was creating it at school.
The program was originally created by a team of programmers who participated in the creation of the Visual Basic Handbook. The program was originally a small client-client based chat program consisting of multiple people communicating in real-time over a network.
Only having limited chat functions and not even the ability to see who was posting, I set to work on rewriting this.
As the months passed, I added hundreds of features, including admin commands, user databases, private messaging, chatrooms, 30+ commands, and a scripting system.
The version number reflects where I got up to...it used to be version 3.26.600 or something like that, which reflects how many updates I did. I incremented the build version by about 100 every time I made an update.
The last updates where TCP/IP networking to replace the messaging system. It was a buggy and complex system to implement and I did it while I learnt TCP/IP. It used the base of the previous messaging system and didnt work too well, but it worked.
Unfortunately, this buggy implementation that consisted of several badly programmed connection windows failed and let to too many bugs.
This is the end of Network Messaging 1. For older versions, email me at dae_man2001@hotmail.com and I'll send them. This is the only way to experience the older network-only versions.
Farewell to the program I spent 2 years creating. Thanks to everyone at my school who found bugs, and created them, for me to fix.
Thanks all :D

I've updated the directory structure. The seperate DLLs have thier sourcecode in thier own directories, whilst the main program is located in Code_Main.
There is also a few source updates to the windowing system.

I'm starting version 2 of the client. The old version 1.326.xxx was buggy and unclean. Instead of going through all that code I'm starting anew.
This version highly resembles mIRC, in look and in the scripts. Please bare with me :)