i found and fixed a few bugs in the most recent file release (no, i haven't downloaded the cvs tree yet) ... and i simplified some of the socket code ... found some more bugs to fix, but would like to contribute the fixes back, if there's still active development ...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'd be interested in helping out. I've got very little experience on the Swing side of Java but lots (the get-paid-for kind) on the non-UI side. It'd be nice to make pretty things again.
If you do get any momentum on the project again, please email me, if not I might do it anyway :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
my momentum has slowed down, i too am one of those "lots of experience in java by getting paid for it" kind that's weak in swing ;-)
i did several fixes, and they've been uploaded into the cvs tree ... but from what i've noticed, there's a few different projects going on in that tree ... i'm using the jLiveJournal code that i modified, and it's working pretty good if you want to give it a try ...
(i fixed some crashing bugs, cleaned up some code, and added some functionality like mood, etc)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, I've _glanced_ at the 1.3.1 code and it looks like it's ready to make a decision. It can be cleaned up and become a nice small-and-fast client, come up quick, do stuff, and shutdown; OR it could undergo some significant re-implementation and become a full-featured client with non-English support, error recovery, batch edits, etc. -- i.e. a fully-working clone of the Winderz client.
There's a lot of change in the CVS tree as of last week, looks like the second option is being developed already by bchoi.
So...what's the official desire from the project admins? Personally I'd like to shoot for the Winderz clone, with the re-designs that would require, because it would sharpen my skillz, create some neat-o side-effect code (like a full command-line Java client, and a local non-Netted "server"), and help open LJ up to non-English speakers. It'd be a nice distraction for the summer too. :-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
gee, the last thoughts were done back in feb of 2002? I ran into bugs in 1.3.1 myself that I've fixed locally, but I guess there's not much point in pushing it.
the socket i couldn't get to work at all, so i wiped it with
HttpURLConnection c = (HttpURLConnection) new URL("http://www.livejournal.com/interface/flat").openConnection();
c.setRequestProperty("Host", "www.livejournal.com");
c.setRequestProperty("Content-type", "application/x-www-form-urlencoded");
c.setRequestProperty("Content-length", "" + postString.length() );
c.setRequestMethod("POST");
c.setDoOutput(true);
out = new PrintWriter(new OutputStreamWriter(c.getOutputStream()));
out.print(postString);
out.flush();
// System.out.println(c.getResponseMessage());
in = new BufferedReader(new InputStreamReader(c.getInputStream()));
--
also, in the date code, change Calendar.HOUR to Calendar.HOUR_OF_DAY
Joe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In addition, though I didn't do it at the time, all of the URL encoding code should be replaced by calling URLEncoder.encode(s, "UTF-8") on each segment. Its new as of JDK 1.3.0 and gets rid of a lot of dodgy encoding stuffs.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i found and fixed a few bugs in the most recent file release (no, i haven't downloaded the cvs tree yet) ... and i simplified some of the socket code ... found some more bugs to fix, but would like to contribute the fixes back, if there's still active development ...
I think that development may begin to pick up again. I had someone recently download the code and make *multiple* changes.
Actually the code that you have is *OLD* and was from when I first started programming in java.
I had a complete rewrite, but lost it when my laptop died.
You can write me: kenbrooks@sevensoft.net
and we'll take a look at what you are doing..
i may just start the whole thing from scratch if i have a couple of people who want to help out..
who knows..
I'd be interested in helping out. I've got very little experience on the Swing side of Java but lots (the get-paid-for kind) on the non-UI side. It'd be nice to make pretty things again.
If you do get any momentum on the project again, please email me, if not I might do it anyway :)
my momentum has slowed down, i too am one of those "lots of experience in java by getting paid for it" kind that's weak in swing ;-)
i did several fixes, and they've been uploaded into the cvs tree ... but from what i've noticed, there's a few different projects going on in that tree ... i'm using the jLiveJournal code that i modified, and it's working pretty good if you want to give it a try ...
(i fixed some crashing bugs, cleaned up some code, and added some functionality like mood, etc)
(This might post twice, sorry.)
Well, I've _glanced_ at the 1.3.1 code and it looks like it's ready to make a decision. It can be cleaned up and become a nice small-and-fast client, come up quick, do stuff, and shutdown; OR it could undergo some significant re-implementation and become a full-featured client with non-English support, error recovery, batch edits, etc. -- i.e. a fully-working clone of the Winderz client.
There's a lot of change in the CVS tree as of last week, looks like the second option is being developed already by bchoi.
So...what's the official desire from the project admins? Personally I'd like to shoot for the Winderz clone, with the re-designs that would require, because it would sharpen my skillz, create some neat-o side-effect code (like a full command-line Java client, and a local non-Netted "server"), and help open LJ up to non-English speakers. It'd be a nice distraction for the summer too. :-)
gee, the last thoughts were done back in feb of 2002? I ran into bugs in 1.3.1 myself that I've fixed locally, but I guess there's not much point in pushing it.
the socket i couldn't get to work at all, so i wiped it with
HttpURLConnection c = (HttpURLConnection) new URL("http://www.livejournal.com/interface/flat").openConnection();
c.setRequestProperty("Host", "www.livejournal.com");
c.setRequestProperty("Content-type", "application/x-www-form-urlencoded");
c.setRequestProperty("Content-length", "" + postString.length() );
c.setRequestMethod("POST");
c.setDoOutput(true);
out = new PrintWriter(new OutputStreamWriter(c.getOutputStream()));
out.print(postString);
out.flush();
// System.out.println(c.getResponseMessage());
in = new BufferedReader(new InputStreamReader(c.getInputStream()));
--
also, in the date code, change Calendar.HOUR to Calendar.HOUR_OF_DAY
Joe
In addition, though I didn't do it at the time, all of the URL encoding code should be replaced by calling URLEncoder.encode(s, "UTF-8") on each segment. Its new as of JDK 1.3.0 and gets rid of a lot of dodgy encoding stuffs.