First a big thank you to everyone who has submitted a crash or exception report, or otherwise provided feedback. I look at every single report that comes in. Often, if you've included contact information, I'll try to get in touch with you when I have a development build that I think fixes the problem.
The crash and exception reports have been split about equally between problems more closely related to the actual client-server communication, which is handled by the asLJCore library, and problems that are more related to the local computer (user interface, file system, and so on), which are not handled by asLJCore. While I think I have succeeded in eliminating all or nearly all of the reported problems of the second type, many of the issues with asLJCore have been harder to track down and fix, in large part because of some less-than-ideal design choices when I first started asLJCore.
( Collapse )
So, what exactly is the state of asLJ? I'm fairly far along in rewriting asLJCore and have been using the rewritten asLJCore myself on a regular basis for more than a week now. I have also been working on asLJ beyond just asLJCore. The next beta will be "sandboxed" and signed in a way that should work with Gatekeeper on OS X 10.8 Mountain Lion (though I am not yet testing on Mountain Lion). I expect that it will be several weeks before the next beta release, but I'm hoping to get some development builds to testers in a few weeks.