Comments | alivejournal: More progress

be_matt in alivejournal

More progress

May 29, 2004 08:26

Well, I've got the client to have multiple, currently hard coded, servers. You also have the option to type your own... The ititial state is now correct - the "remember settings" flag now seems to actually restore the settings properly. It was working in the GUI, but the internal stuff wasn't in place ( Read more... )

Comments 10

methid_tim June 18 2004, 03:50:40 UTC

Hey! Development still going on for the BeOS client? Keep up the good work!

be_matt June 23 2004, 02:06:29 UTC

Yep, though it's progressing slowly :-( Real life is seriously getting in the way due to illness, job and personal life being hectic at the moment.

Expect a new release after I've merged my code with Sean's and also looked at a few odd bugs I have to sort out before a release... Real Soon Now (tm)

grahams June 30 2004, 05:58:01 UTC

BTW, I forgot to mention that if you want to create your own website for your ALJ development I can put a link to it at the old page (so people get forwarded to you).

? fyysik July 16 2004, 03:59:25 UTC

Can you expalin a bit about "UTF-switch" ?
I don't get it.
Also i found place which affects disappearing text after "=" sign but logic there isn't yet clear for me

Re: ? fyysik July 16 2004, 05:33:43 UTC

Problem is that i cannot compile it under BONE anymore:(
Did it before, as you understand, but now falling in hell with redefinitions of socket functions due circular depemdemcies in all that time.h select.h socket.h etc.
Wondering if Simeon or Sean can recall how to compile it under BONE

Re: ? be_matt July 16 2004, 15:01:38 UTC

The UTF-8 switch will just allow the user to select whether they post with the old LJ ascii encoding or the UTF-8 one. It's more or less a case of adding a param with a 0 or a 1 to select the protocol (as you lnpw ;-).

As for *why* the UTF-8 encoding fails... that's really tricky. As BeOS *uses* UTF-8, it was to be some oddity with either the way BeOS uses UTF-8 or (more likely) the way UTF-8 is interpreted by the LJ server...

As for BONE - the NetServer version just uses BNetEndPoint IIRC, so it should work with BONE "as is". BONE has a compatibility layer for that part of NetServer, right?

Re: ? fyysik July 16 2004, 15:54:32 UTC

Netserver version works for BONE, no doubts.
Problem is i hadn't anymore netserver installation and no space to set it just for compile AJ.
But i remember i compiled it nicely some times ago, with same sources, and first UTF-8 fixed build was just BONE-build.
I'm almost recalling that i got some advise from Sean, how to do it without pain, but maybe that's Deja Vu

Thread 7