|
Mobiles Softwares share here your softwares for mobiles |
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
mIRGGI v.60 Update 11/08/08
Version 0.60 is now out. It fixes three reported things: bell character crashing mIRGGI (also probably helps with other crashes), closing window after disconnect won't crash and the activity squares are of different color.
mIRGGI is the first IRC client for S60 3rd Edition devices. It is also available for 2nd edition devices. It is currently in early stages because I just began writing it on 10th of March. I've been meaning to do this for a long time but haven't gotten to it. I don't like the J2ME IRC clients (one big reason is that they suck up a lot of memory on S60) and I don't like using PuTTY, especially on devices without keyboard. Also their fonts are quite ugly (I like small vector fonts, as is obvious from this release This is a hobby project and mainly targeted at my needs but I will try to find some relaxing time to enhance it. And especially the things that bother me personally will get fixed fast. There are most certainly some bugs but I have successfully used it for several hours at a time via GPRS without problems. mIRGGI has also been seen for a selected few as a terminal IRC client for Linux and Windows. Those versions haven't been updated for a loooong time and were never really released. I might do a version for Windows Mobile someday, too. mIRGGI has been tested by me on Nokia N93, E70, E61, N73, N95 and E60. Others have used it on almost every S60 3rd Edition device (N80, N73, E61i, E90 etc). 2nd edition version has been tested by me on 6260 and N70. For version history, future features, bug reporting etc check the blog. How To Use It? First, change the settings (they are automatically displayed when running mIRGGI for the first time). Input nick, username, realname and server. Press back and then connect. If you want mIRGGI to connect to channels or open query windows on startup, input them to Auto windows setting. Separate channels and nicks with commas. If you need keys for channels, you can input them too. mIRGGI supports the following channel prefixes: # & ! +. Example: #channel key,#channel2,!channel3 key2,nick1,nick2 will open #channel with a key, #channel2 without a key, !channel3 with key2 and query windows for nicks nick1 and nick2. These windows are numbered 1-4 and you can use keys 1-4 to quickswitch to them. To input text, press enter or OK button. This will bring the cursor to the input line at the bottom of the screen. Press enter or OK to send the line/command. If you don't want to type anything, pressing OK/enter on an empty line disables inputting. If the line starts with / it is considered a command, otherwise the text is sent to the channel or query target. When not inputting text, left/right change the windows. Also pressing 0-9 will jump to that window (0 is always the server window, channels and queries start from 1). Up/down will scroll the current window. At the moment, the window scrolls down when new text arrives. I know, this can be annoying sometimes. Windows are created when joining to a channel or starting a query. They are not closed if you leave a channel at this time. You can close them manually by using /close. You can use /cquery command to change the nick in the current query window if the other party changes their nick. What Commands Does It Support? Commands start with / as usual and the following commands are supported: msg, nick, join, leave, part, query, cquery, mode, me, topic, away, who, whois, whowas. Mode accepts * as the first parameter which means the current channel. All other lines starting with / are sent as-is to the server, like /quote command on some clients. So you can also send commands that are not on the list, you just might have to add : characters to certain places. mIRGGI also should be CTCP compliant as it provides responses to these required CTCP messages: CLIENTINFO, VERSION, PING. mIRGGI does not yet implement sending these. CTCP ACTIONs are shown and sent. mIRGGI supports the following character sets for encoding and decoding (anyone need per channel encoding settings? could be done someday): * ISO-8859-1 / Latin 1 * UTF-8 (Auto UTF-8 will decode UTF-8 if detected, otherwise the text will be handled as Latin 1) * Windows 1250 (Central and Eastern European) * Windows 1251 (Cyrillic) * Windows 1253 (Greek) * Windows 1254 (Turkish) * Windows 1255 (Hebrew) * Windows 1256 (Arabic) * Windows 1257 (Baltic) * Windows 1258 (Vietnamese) |
Bookmarks |
|
|