cocoaforge

Many times when i click or drag a link from a chat window to a browser, Adium seems to add the suffix <br /> to the link. I'm assuming this end tag is due to the html/java nature of adium (as far as i know), but this is certainly a bug that the <br /> shows up as part of a link.

A few questions I also have regarding this:
1. Isn't the end tag </br> rather than <br />?
2. Why bother having the end tag anyway? It's optional isn't it?

Also regarding the underlying code for adium, is there any way that we can reduce the time it takes to draw? It is slightly annoying that when a chat window pops up or when someone sends a message, it takes around 2 seconds for the window to re/draw, and a further 2 to 30 seconds until i can interact with the window (make it active to see the message, or type to reply).
This gets particularly bad during high activity within adium, such as 3-4 IMs cocurrently, a group chat, multiple people changing status and mail notifications and/or error dialogs popping up, all at the same time. It often ends up that adium gets the spinning beach ball for anywhere from 10 seconds to 2+ minutes. It eventually gets frustrating when whatever i say is only sent after the topic had (long ago) moved on, which then means i have to send an explanation for the out-of-place message.

Not to be rude or anything, since i know my computer is pretty damn slow by today's standards (400mhz imac ), but can we make it so we see less spinning beach balls and more screen updates? Many thanks, much appreciated.
PS I'm not aware of any minimum requirements for Adium other than Mac OS X, so correct me if i'm wrong.

In all fairness you are eking out OS X and to ladle a bunch of graphical tasks onto the processor, since you don't have sufficient GPU support, will always bog you down. The only real solution in your case would be to disable WebKit, to disable animations and notifications and run with only minimal settings. It's not a flaw in Adium, it's your hardware.

No real GPU support + low CPU availability + likely low to medium RAM (note OS X requires 128 MB to run comfortably) = low performance.

I haven't seen the <br /> problem.. what protocol? Where are the links (message window, profile, etc)?

And yeah, I have to echo what Brian said about performance... though we are continuously working to improve Adium's responsiveness on -any- system.

bgannin wrote:note OS X requires 128 MB to run comfortably)

Actually, OS X requires 128 MB to run AT ALL. Most systems with the minimum amount of RAM run quite choppy. If you ask me, running "comfortably" would require at least 256 MB, if not 512 MB

I have the same problem .. when i click a link it open in the browser with that br tag at the end of it .. on msn .. i think i noticed it happens when someone's hit Shift-Return after the link so that the cursor is on a new line within that same message

"<br />" is the XHTML way of saying "<br>" in HTML

I never saw "</br>" before

I see these extra <br /> characters quite a lot, and I may be wrong, but I think they only appear if the link is followed by a new
line. The links are fine when they are on a single line.

For example:
would add the extra <br /> tag (on MSN, don't know about the other services)

zaudragon wrote:"<br />" is the XHTML way of saying "<br>" in HTML

I never saw "</br>" before

<br /> is XML shorthand for <br></br>. Everyone writes it as <br /> because the other way looks silly.

<br> is the way HTML Transitional likes it.

HTML has no "<br />" tag!

XHTML does have the <br /> tag however

I said that in the beginning, but you're right.

There is a "<br />" tag in XHTML

.... <br /> is the xHTML link break command. HTML 4.x and prior is just <br> and there is no closing tag. that being why there is a " /" in xHTML. new rules require that ALL tags close including img, link, etc.

just to clear it all up

It's because XHTML is just an XML wrapper for HTML.

XHTML uses the same tag format as XML.

...and if people don't close their tags in XHTML I will hunt them down and kill them in the night...

Or at least not display right

And not be "valid!"