Comments | aslj_users: What is asLJ?

aslj_client in aslj_users

What is asLJ?

Feb 07, 2009 17:10

asLJ is a LiveJournal client for Mac OS X 10.5+

asLJ easily posts to multiple accounts and works on LJ-based sites other than livejournal.com (currently tested on LiveJournal, GreatestJournal, and InsaneJournal; should work on DeadJournal; others to be added when requested).

Download

Release notes are in aslj_client. aslj_users is for discussion about asLJ.

Comments 5

ron_newman February 9 2009, 14:59:45 UTC

Can you post a link to the source tree for this client? Thanks.

aslj_client February 10 2009, 05:13:31 UTC

Thanks for your interest, but asLJ is not open-source. While I realize that this is a deal-breaker for some people, I have made the choice to keep it closed-source, though it is my intent for it to be gratis (free-as-in-beer) software.

(The comment has been removed)

aslj_client February 10 2009, 05:14:12 UTC

This will be done in the next release, to come shortly. Without an invite code, though, I cannot test it myself.

rickybuchanan February 12 2009, 12:48:07 UTC

This looks fantastic - thank you!

Is it really written all in AppleScript? A library for AS which talks to LJ and friends would be a very useful thing. Have you any plans to share that part?

aslj_client February 12 2009, 16:46:31 UTC

It's not entirely in AppleScript, but the bulk of the code is AppleScript. It's an AS Studio application, which is to say it's created in XCode and has an interface file like any other XCode project, but then the bulk of things get linked back to script files instead of whatever other language one might use in XCode. There are pieces that I did in Objective-C because they couldn't be done well or adequately or at all in AppleScript.

The core of communicating with LiveJournal and what actually inspired me to get started on this in the first place is http://community.livejournal.com/applescript/18386.html. The code I actually use to make my LJ XML-RPC calls is here--the biggest difference is that my code allows for setting the server at runtime. Beyond this, I don't have much of a library that talks to LJ, just a wrapper function that makes the getchallenge call and then the actual call using challenge-response authorization.