Yes, this unittest has been painful to work with. Recently, I was
trying to run the tests when I was offline and couldn't make this test
pass. I spent some time trying to work around the problem but wasn't
successful. I've disabled the test now:
http://code.google.com/p/wave-protocol/source/detail?
I recently cloned the Hg repository to try wave out. When I compiled, most
of the ConsoleClientTest unit tests errored out with NullPointerException's,
specifically, all those that called ConsoleClientTest.connect(). When I
eventually tracked the problem down, it was because the ClientBackend was
a
Ahh, maybe then it's easier then I thought :).
But anything related with events sink is advanced topic imho. An easier
approach would be just to listen on endEditSession event, and then to
inspect the text in the edited document with regular expressions. If some
text looks like a link to annotate i
hu?
Auto-Linking was the first starter project on the list;
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=labels+%3D+StarterProject
Thats what I was trying to do.
-Thomas
On 17 July 2011 14:55, Yuri Z wrote:
> IMHO, you should be looking at diff highlighting imple
IMHO, you should be looking at diff highlighting implementation to serve as
example. Probably David Hearnden can give you more details.
But, this is advanced issue. How about taking first on the StarterProject?
2011/7/17 Thomas Wrobel
> Thanks, might have to take you up on that at some point.
>
Thanks, might have to take you up on that at some point.
For the moment I'm just looking around the code trying to work out how
it works and where the new code will need to go for the Auto-Linking
(https://issues.apache.org/jira/browse/WAVE-275?page=com.atlassian.streams.streams-jira-plugin%3Aactiv
