Hi Thomas,
There's nothing hard about doing auto-linking. I say just go for it.
Here are some ideas:
Call addUpdateListener() on the editor with a listener for changes.
I'm not sure where the right place to register it is, but take a look
at where SelectionExtractor is registered, which is a good
If you are talking about the modularisation separating out the client
and server, that might lead to a chicken and egg situation, as you'd
need the c/s protocol first to do that no? I'm trying to learn enough
to help with that - but as you point out even simple things seem
rather complex to an out
I'm trying too. Was struggleing to understand how the editor worked
and I wasnt yet confident enough to say I could do it.
-Thomas
On 19 July 2011 23:06, Yuri Z wrote:
> BTW Thomas, are you working on this issue? If so, can you please assign it
> to yourself in the Wave Jira?
>
>
> 2011/7/17 Thom
It is a little concerning that something that should ordinarily be so trivial
as
auto-linking is considered advanced.
I wonder if it is worth looking again at the overall architecture. From outside
it seems a hard sell, you need developers to want to get involved, both helping
WAIB grow and ea
BTW Thomas, are you working on this issue? If so, can you please assign it
to yourself in the Wave Jira?
2011/7/17 Thomas Wrobel
> hu?
> Auto-Linking was the first starter project on the list;
>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=labels+%3D+StarterPr
