||[Aug. 11th, 2000|11:41 am]
- Nonblocking connect. Now only gethostbyname() blocks.
- Summary added to friends view.
To post using LoserJabber from vim:
- install LoserJabber in to the path
- set up your account in the identities (optional)
- type your post in vim
- run this vim command: %!lj -u username -
(you'll need to add your password if you skipped step 2.)
- the output will appear in your buffer.
I'm sure you could do something similar with emacs...
2000-08-13 10:23 am (UTC)
Re: a few things...
Heh. When put that way... nothing, nothing at all. *smile*.
What I meant is that I have pretty good general programming skills. I write very clean, fast, straight forward code that is easy to read, and easy to debug. I have sound design, generally building in a modular fashion, leaving plenty of room for future improvments.
I have actually written a few C programs before, and can debug easy things. I have even recently modified a C applicaiton ("motion") to my liking.
The problem that arises with applications like LoserJabber, is that I have only ever coded one GUI application (and it was in Visual Basic, which doesn't really count). So... all of the Gtk- this and Gtk- that confuses the hell out of me because I don't know C well enough to be able to follow what is going on. I understand structs, and variable declarations, and functions, and pointers and references, but don't always understand what I am looking at when I see it, and don't always know when I should use what. I have never really had to deal with memory allocation and deallocation.
The problem, again, with LoserJabber, is it is divided in 14 different files, with almost each of those having a header file. In addtion, it needs Gtk which complicates things even more.
So, to sum up. I know nothing, really nothing.
2000-08-13 09:50 pm (UTC)
Re: a few things...
(This is all kinda random, sorry.)
The best code to write is the code you need... if LoserJabber is lacking a feature, you could add it.
The "command-line-only" feature you mention, though, is probably impossible, for the reasons Brad gave.
Regarding the 14 different files, well, that's the way understandable software is written. Each file (with the exception of lj.c, the main part of the program) is an independant piece of the program.
They average at about 400 lines (history.c and friends.c bring the average up), which makes them digestable with a bit of thought.
Personally, I hate working with other people's code. It's probably my biggest limitation as a programmer.
GUI code is really painful to write, but as far as GUIs go, GTK is really quite easy. Regardless, it's probably better to learn it independently of LoserJabber. The Perl bindings for GTK are a lot of fun. They're much more logical than the C bindings.