• View the status and information about your phone/device.
• Compose and send SMS messages
• Reading, deleting, forwarding and replying to SMS messages
• Command console for interacting with the phone directly via AT commands

Download

Current Version 2.1

• Windows Installer – Setup SMS Toolkit 2.1
• Unix – SMS Toolkit for Unix
• Source Code – Source Code

Pre-requisites

The SMS Toolkit uses SMS Lib (http://smslib.org/), for Windows users I provide a compiled version of SMSLib and it’s supporting libraries (Sun Comm API and/or RxTx) This means Windows users have a choice, they can run either the Sun Comm API version (very, very highly recommended) or the RxTx version (not recommended). Unix users also have the choice but I don’t supply the files (See Installation below)

Installation

• Windows

There is a supplied installer which does all the hard work for you. Simply run the installer and follow the prompts. This will install all the pre-requisite required libraries and files, and create shortcuts to
start the app.

• Unix (Linux, Solaris, OSX)

I don’t supply any installer, for the supporting libraries (SMSLib, Sun Comm or RxTx) you will also have to supply your own. I don’t have resources to test all the combinations of Unix and the differing libraries. Installation of SMS Lib is easy, and instructions are on the SMS Lib website here – http://smslib.org/installation_java.php which also covers the installation of RxTx and the Sun Comm API.

Device Connection

First of all you need to connect your device (this is most likely to be a mobile phone, however GSM modem devices such as the MC35 are supported too). The mechanisms and means to doing this are too numerous to document here. In all cases the only thing the SMS Toolkit needs to know is the COM or Serial port the device is attached to. In the case of cable connections this will be a real physical port (e.g. COM1) in the case of Bluetooth or IrDA connections this will be a virtual port created by the Bluetooth or IrDA software.

Quick Start

First click the ‘Device’ button on the toolbar, this allows you to specify the serial port and the baud rate to connect on. Choose the port of the device (as explained above) and the baud rate can be left at 9600 or increased. I’ve never seen much difference with baud rate speeds but some devices may only support certain rates.

After this is done, click the ‘Connect’ button on the main toolbar. If everything is OK then SMS Toolkit will connect and you will see your device details on the Device tab. If there was a problem connecting then you will see an error. The most likely causes will be the port you specified was incorrect or another application is using the port.

SMS Functions

Most of the functionality is pretty obvious, but I’ll cover a few potential problems.

If when you click the ‘Refresh’ button on the inbox screen and no messages are shown, goto the SMS options and select which location you want to read from; either SIM card of your device or the internal memory of the device. Some devices store only on the SIM, some only in memory, and some use both. Try different options.

The same can happen when sending a message, if you get an error sending a message, try changing storage location in the SMS options dialog.

Console

This is intended for advanced users that wish to interact directly with their device via the AT command set.

Introduction

A ray tracer is an image rendering tool, which can generate very realistic images. It does this by modeling the physical properties of light and produces its images by casting (or tracing) rays of light through a modeled scene, as they would behave in the real world and projecting the results into an image. It is a mathematically intensive process, however by the implicit nature of the core algorithm it handles reflections, shadows and refractive transparency very well, things which other algorithms (say a scan line, z-buffered polygon renderer) would struggle with.

It is worth noting the images below were generated solely with the ray tracer and the entire project was coded from the “ground up” even down to the vector and matrix math routines as I wanted to develop my own libraries to get a better understanding of the mathematics.

Source Code & Notes

Source code? I’m not sure if you really want to be downloading this. It hasn’t been too good for my sanity, so I’m certain it won’t be to good for anyone else’s! Here it is anyway, for simple reference more than anything.

The code is a bit of a mess, most of it has comments but some of it hasn’t; some bits make sense, some bits don’t, you get the general idea… Basically I’m putting up it here for the curious and for anyone else writing a ray tracer. Bear in mind that since writing this (back in 2001 or so) I have learnt a lot about Java, so this code is a little immature shall we say.

Ray Tracer Source Code

The GUI currently does nothing, the scene is hard coded into the source and the textures code is fairly static. So a top list of stuff to do includes:

• Refractive transparency – Done, but some objects don’t have ‘real’ interiors yet. Cylinders are real pain.

• Proper camera parameterization – Done, but hard coded

• Anti-aliasing – Done, adaptive & non-adaptive

• More objects: Torus, Polygons, NURB surs, Superquadrics, Blobs etc.

• CSG

• Get the GUI doing good stuff, parser for scenes etc. (Use XML and JAXP)

• Better procedural and image based texturing

• Bump mapping and normal modification

• Loads of optimizations needed, multithreading

• Blah, blah, blah…

Update – well I should have had a look round the web before I spent time writing this as Jetty is what I should have used – ohh well! I learnt a lot about the internal workings of HTTP. In fact looking round the Jetty javadoc you’d have thought that I copied them given some of the main class names are the same – well I didn’t (in case you were wondering!) I’m leaving this up here for the curious, it’s not that my attempt is bad, just that Jetty is MUCH fuller featured

Download

Download HTTP Server 1.0

Documentation

1) To run as a standalone webserver simply copy the JAR file to where the directory where you want to serve files from, then double click the JAR file – easy as that! When it’s started a dialog should pop-up telling you the URL to access your web server

The ‘server.properties‘ file can be used to change the server settings but if it’s missing then the server runs with it’s internal defaults so it’s not required for the server to run. The default settings are

• http_tcp_port = 1975
• http_doc_root =
• http_log_dir = ‘http-logs/’
• http_log_level = ‘CONFIG’
• http_log_size = 1000000
• http_log_count = 5
• http_ka_enable = true
• http_ka_time = 15

2) Use the HTTPServer class in your own code to embed a HTTP server into your own Java project. Include the JAR file in your classpath and see the javadoc for more details on using the server.

Java Documentation

Click here for the HTTPServer package javadocs and API reference

License

This software is distributed freely under the GPL license
see http://www.gnu.org/licenses/gpl.html for details.

I’d put the source code up too, but that appears to have got lost somewhere

Download – MuVo Control Center v0.9