LiveEdit / News: Recent posts

I admit it, for a year and a half I've barely, BARELY touched LiveEdit, due to school and work (internship) obligations. However, now that my internship is over, I am returning to school, and should have more time to work on LiveEdit. There's a lot I has planned for 0.2.0, and I stopped about halfway through implementation, leaving the broken code on the SVN repository. Well, now it's time to finish those features, and finally release a version that has the bug fixes implemented!... read more

Now that SF has been running Subversion for a while, I feel it's time to migrate from my personal Subversion server (which I've been using for some time) over to SF's so everyone can look at the LiveEdit code whenever...enjoy!

With only a few final things to wrap up in 0.2.0, I have a few announcements to make. First of all, there will be no more ANSI builds (as I stated earlier). However, there *will* be a 64 bit build of 0.2.0, so those of you running 64 bit ed. are in luck. Also, a few words about settings... In order to support different profiles for each user on a multi-user system, the settings are now stored in the user's application settings directory (still NOT the registry). However, this makes LE less portable so I will either have a seprate "portable" build of LiveEdit, or do some "fancy" workarounds to make it portable ;).

Finally, I have run into API calls where 9x systems (95, 98, Me) can no longer be easily supported, thus support for them will finally be dropped. Since 9x support is no longer needed, ASCII support will be dropped as well, in favor of the Unicode character set.

I hope (and doubt) this will be an issue to any users of this program (there actually appear to be a few!). And what about the status of v0.2.0? It's finally winding down, as there are only a few things left to do. In fact, all that's left are the address book, binary file transfer (which will be easy (and more efficient) now that 9x support was dropped), and a complete redesign of the socket I/O method.... read more

While I still have to finish up a few of the features described in the last news port, I thought it would be a good idea to list some of the other things I've added to LiveEdit. If you've seen the latest screenshot, you'll notice that it now looks up both the LAN and the WAN IP (IPv4 only). Also, LiveEdit is now IP version agnostic as far as the titlebar & connections are concerned. Oh, and now you can enter a IPv4 address, IPv6 address, or a hostname (resolves to an IPv4 address only) when connecting.

There are two things well (only one of them applies to most of you), that need to be added before others. Those are: binary file transfer between connected users, and IPv6 support. A third thing that would be very nice to have is a detection mechanism for incompatibility when users connect to one another (Unicode to ANSI, and ANSI to Unicode). Since a system for sending/handling escape codes has been derived, none of them should prove to be all that difficult to impliment. All that needs to be done now is the grunt work.

The new release is finally ready. So many improvements have been made the 2nd highest version number has been incremented. For a list of changes, see the changelog in the release details.

P.S. - In the end, only 4 of the 5 planned text encodings made it to the release (UTF-7 was dropped). I doubt it will be a major issue for most users, however.

Since I've jumped on the unicode bandwagan, I decided it would also be a good idea to allow people to choose how they'd like to encode their text files when saving a buffer. The next version will include 5, yes f-i-v-e, different encodings for text files.

Lots of work has been put into making a unicode build of LiveEdit, which should be available as soon as version 0.0.0.3 is complete. Of course, ANSI builds will still be available for those on non-unicode systems (who have not yet installed the unicode layer). Note that the unicode version will *NOT* be compatible with the ANSI version. I am currently working on a detection mechanism to avoid any accidental connections between the ANSI and the unicode builds.