On Thu, Apr 22, 2010 at 3:56 PM, Craig Andrews <candr...@integralblue.com> wrote: > The client side shorter "debounces" the keypress event, waiting 1 second > after the last keypress to do the shortening. I *think* that's enough to > avoid shortening partially-typed URLs. I'm not sure how to recognize that > a user has paused mid-URL, I'm looking for ideas.
Do a check on it, - if there is a word seperator (I think space, ")" etc) after the URL, do the processing on it. If not, it's possible it's unfinished. The problem is when you write the URL at the end of the notice http://example.com/ But then you probably hit SEND right away anyway, so the async shortening will be dead slow and you won't like it anyway, you just want the notice to be sent. Another potential very irritating thing is that if you replace the text while you type (or while you're looking) it'll be extremely frustrating. So it should probably leave the url as-is, and just slide down a: - found shortlink, we'll use *s0.no/aoeu* instead of *http://example.com/this-is-a-text/* and also update the count so that the url gets counted as fewer chars. -- Beste helsing, Odin Hørthe Omdal <odin.om...@gmail.com> http://velmont.no _______________________________________________ StatusNet-dev mailing list StatusNet-dev@lists.status.net http://lists.status.net/mailman/listinfo/statusnet-dev
