AmiMSN beta with file transfer

[MickJT]

Hello to all..

I haven't done very much since 0.6, but for all of you who want or need an MSN messenger client with support for sending and receiving files, you can get my l8st beta at http://members.iinet.net.au/~trebs/AmiMSN/

[MickJT]

Well You wouldn't be asking that question if you saw what it's coded in, hehe..

I'm primitive in my knowledge of programming languages

[MickJT]

Well.. I can do screenshots if it's necessary.. Remember micq? Like that..

Console client..

Unless you're running it in IRCd mode, well then the IRC client is the GUI.

[MickJT]

Uh, the docs are incomplete!?

The requirements section at the bottom of the .readme should tell you everything you need to have.

Let me know if i've missed anything.. As for receiving files.. Yes, bad router, blame it on the router, lol

For file transfers, you connect to the sender.

Normally routers wouldn't affect outbound connections?

[Edit] Make sure the *sender* doesn't have any firewall turned on.

[MickJT]

@Gerbinist

Thank you.. I was half expecting to be flamed for it being written in arexx, and no GUI, etc.. etc..

I assume you got file transfer going ok both ways?

[MickJT]

AWNPipe and RXMui is like learning a new language.. I tried mucking around with RexxMUI some years back and had trouble.. but perhaps now I could figure it out.

I think RexxMUI has asynchronous functions too.. Which of course is NEEDED.

I started AmiMSN thinking I could do it with AWNPipe, but then found out that it's not asynchronous and had to turn it into a console client with an IRCd mode

As for the website.. I had none until 2 hours ago It'll get better..

[Edit: CaptainHIT doesn't ring a bell.. Any other names?]
[Edit2: Hang on I was thinking of MUIRexx not RXMUI. I'll have a look at it]

[MickJT]

I'll come on overmind, and grab the .log off you.

[MickJT]

@Gav

You need rexxreqtools.library not just reqtools.library

@cgutjahr

AWNPIPE isn't asynchronous, which means that you send "con" (as in continue), and then you are forced to WAIT to see if a button has been clicked on. I don't want to wait, I want a command that tells me what buttons have been clicked on and not processed yet.

rxsocket.library allows me to see if there is any data to get,  and then get it...

What I want in AWNPIPE is to first see if a button has been clicked on, and if not, then see if if i've typed anything, and if not, then loop..

AWNPIPE is like ReadLn(), you so ReadLn(File) and it just hangs until it reads a line.. there's no CheckToSeeIfThereIsALineToReadFirst()

hehe..

Check the .rexx, and look at the usage of Lines(), I check to see if anything has been typed in the shell window and then if not, check to see if there is any data from the msn server to be read, and if not, then checks to see any commands u sent in the ircd, and if not, then loop..

If it still doesn't make sense, picture this:

You have a conversation window open, and it can't process what you are typing and can't process the messages being sent to you, because it's forever waiting for you to click on the close gadget to shut the window.. No command to simply see if you've clicked on the close gadget

Look at the .readme for CTGUI on aminet..

[MickJT]

Thought to myself: On second thought maybe AWNPIPE's output can be sent to PIPE:.. That'd fix everything.

Oh no wait, I remember already trying that.. In arexx, after you send a line to PIPE:, you're forced to use Close() before the line is written.. You can see how insanely stupid the PIPE: code in AmiMSN.rexx is, but it's the only way i've been able to do it, Open(), WriteLn() and Close() for each line sent.. It's only this way in arexx, and has got me stumped..