AjaxLife Blog

I’ve tweaked the layout of the login screen for the next version. It now looks like this:

Specifically, I added this menu:

Which may look something like this after typing:

So now you can choose where to log in. This is working on my testing server, but not yet live.

Here are some more screenshots!

Going to add the ability to start your own group IMs tomorrow (hopefully), among other things.

Coming soon, among other things:

Other changes so far include significantly improved behaviour of those text boxes on the map (they now reflect what the map thinks you want), marking of the map beacon on the minimap (as a red mark), and assorted refactoring. Wee!

Coming once I’m done adding stuffs.

So, I’ve been semi-busily working on AjaxLife, and spending the rest of my time revising for insanely large numbers of tests. It must be report writing time.

Anyway, we have new features to come to you all shortly, most of which are inventory related:

Hovertips:

Context menus:

And, for those of you who use OS X and Fluid (the latest version, that is), we can do this:

This’ll be released as soon as that “Properties” button works.

[01:57 GMT] We’re back! Release notes as soon as I work out what they are.

[01:52 GMT] Waiting for the server to boot up…

[01:50 GMT] Deploy complete. Booting everyone left online (for the last two hours!) and restarting.

[01:29 GMT] Client deploy complete and tested. Server setup complete and tested. Server deploy in progress.

AjaxLife logins are disabled while we update things. Full release notes will be made available when I’m done.

If you can’t wait, feel free to browse through the svn commits.

The subversion repository at Google Code is no longer going to contain a “trunk” which is always stable - instead, it will contain whatever I ended up with after I finished working. When I feel happy enough with it to push it out to ajaxlife.net I’ll tag it in svn. The last version I had up there is currently tagged 0.0.1, and is identical to revision 34 of the trunk.

The net effect of this is far more frequent updates to the code, and less of me having to spend hours undoing stuff I did due to not having a copy of it.

Basically, if you want working code, look for the largest number in http://ajaxlife.googlecode.com/svn/tags/. If you want recent code, look in http://ajaxlife.googlecode.com/svn/trunk/. I’ll be dropping my own server code into the trunk shortly. The client code is so hideously broken it gets to be an exception until I have it fixed (which shouldn’t be that hard, really - it needs to be ported back to an old UI library, and it’ll all magically start working again).

I hope this makes people who want more recent code happy. Also, contributions would be welcomed, although this will involve digging through my mess of C#/JavaScript.

[EDIT] I’ve committed the server changed - see here for a list of changes.

I’m working on new AjaxLife features. Hoorah.

I’d hoped to have a new version out by last Friday, but I changed my mind about what I wanted to get into this one. As such, here are some screenshots of the upcoming features to make up for it:

See pictures!

I’m bored, so I’m going to see if I can get round this bug.
First step: reproduction. This is easy:

Step 2: Found the offending XML:

<member><name>name</name><value><i4>1</i4></value></member>

(”i4″ should be “string”)

Step 3: Give up because my internet connection’s dying.

Step 4: Roll out fix.

Step 5: Announce success.

[19:17 06/01/08] I have a Hebrew translation, courtesy of Smiley Barry. I’m waiting on more contributions before I add it in, since doing so involves deploying server code, which is tedious.

[UPDATE 09:39 06/01/08] Fixed a display bug in Firefox, the only browser that actually seems to care about such things, caused by uploading ui.css as text/javascript instead of text/css.

First, AjaxLife now uses javascript files minified and munged by the YUI compressor, then merged into a single file.

Right. Now, it would be very much appreciated if anyone capable of doing so with free time could translate AjaxLife into the language of their choosing, or update the existing translation for that language.

The language file can be found at http://static.ajaxlife.net/translate.txt - to translate it, change the text on the right, in quotes, to the translation of whatever is in it right now. The text outside these quotes must remain unchanged. Additionally, the UI assumes that the strings in some places (e.g. map buttons) will not gain in length significantly - otherwise, the buttons will overlap. Any text in the format #{word} is a placeholder - do not change this text, but place it where the text should go. The word is usually fairly self-explanatory. Please send your files to katharine@katharineberry.co.uk using UTF-8 encoding.

If you know what you’re doing, and there’s already a partial translation for your language, you can find it at http://lab.katharineberry.co.uk/ajaxlife/AjaxLife.Strings.js

Any efforts will be much appreciated.

I hate it when my text editor crashes. I really don’t have the motivation to waste my time redoing what I’ve already done. This is even more annoying if it truncates the file while saving, but crashes before writing the new one.

New search for AjaxLife will have to wait until I can be bothered to re-code it. Again.

The code now looks something like this:

AjaxLife.NewSearch = function() {

}();

*sigh*