?

Log in

No account? Create an account
LJ2ME 1.0.0 released - LiveJournal Client Discussions — LiveJournal [entries|archive|friends|userinfo]
LiveJournal Client Discussions

[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

LJ2ME 1.0.0 released [Jan. 26th, 2004|05:06 pm]
LiveJournal Client Discussions

lj_clients

[xfyre]
LJ2ME client version 1.0.0 released

LJ2ME is LiveJournal Client for Java 2 Micro Edition. It works (at least it should work) on any mobile device supporting Java 2 Micro Edition Platform. Client has been tested on a wide range on software emulators and hardware devices. Current compatibility sheet can be found here: (updates & corrections are welcome).

Release version include only a small number of bugfixes, in general it's the same as 0.9.9

Client features review:

# Internal support for UTF-8 encoding
# Support for all LiveJournal access modes (public, private, friends, custom)
# Support for 'backdate' and 'disable comments' options
# Load/save draft functionality
# Shared journals (community) access
# Login state is saved in device memory with groups/userpics/comminities information, so it's not required to login every time
# UI ergonomics resembles popular paradigm of Visions/Semagic Windows client
# Works correctly on most CLDC/MIDP devices (Siemens 5x series, Nokia S40 & S60 series, SonyEricsson T610, Motorola, Samsung)
# Customizable client signature in entry subject
# Optional device signature in entry footer
# Userpic support
# Draft auto-save on exit
# MD5-hashed passwords (using MD5 library by Santeri Paavolainen)
# Support for pseudo-tags *bold*, /italic/, _underline_ and %user in entry text
# Ability to load, update and remove last journal entry

Version for PalmOS also available (requires MIDP from Sun Microsystems)

Check project page for further details.
linkReply

Comments:
[User Picture]From: yincrash
2004-02-09 06:06 am (UTC)

Re: curious

j2me is fairly easy to learn if you know j2se well. the language is pretty intuitive and works well for many applications. i was also going to do this until i realized how far xfyre had gone in my own search to solve certain errors he has gotten around on most phones due to an issue with midp 1.0 not really supporting socket connections and transmitting stuff in packets under http 1.1 (which he has gotten around. apparently if you transmit a small enough number of bytes at once, most devices won't turn it into packets.) if he does make a version of midp 2.0 i'd expect it fare even better as long as people keep getting new phones that will support 2.0.

my new project is to make a client for symbian based phones, at the moment for series 60 phones. but c++ in symbian is not nearly as simple as java.
(Reply) (Parent) (Thread)
[User Picture]From: xfyre
2004-02-09 06:26 am (UTC)

Re: curious

if you mean 'chunked' data transfer, there's a very easy trick to overcome it: DON'T USE outputStream.flush()

that's all :)
(Reply) (Parent) (Thread)