There seems to be some interest in the community in getting link rendering working. Pat perhaps you could describe how to do it, rather than do it yourself, and someone like Vega could actually implement it.
Porting any Google Wave code related to links that is not yet open source is something you could do that the community can't and would be very valuable. A. On 6 December 2010 02:40, Pat Coleman <[email protected]> wrote: > In the olden days, we had three types of link - link/auto (Linky), > link/manual (manually entered to a url) and link/wave (special wave links > that are handled differently). > Now we've moved towards only one type of link (link/manual), with manual > logic to handle when a user clicks on waveid:// > After the open source move, none of the link rendering code ever got > registered (although some survived the move) > > That said, there's a lot more doodad logic for things like editing links > and how to handle wave-links - as a first shot, I can add just support for > simple render-link-as-anchor-tag > in StaggeTwo i.e. so you can see and click on links but can't edit them. If > you like I can also writeup how to go about adding link editing stuff (to > the annotation handler and to the toolbar) > but that'd be extra work with stuff that hasn't yet been ported accross. > > Additionally, there's all the wave link handling logic which is a bit > trickier assuming that each client has a different way of viewing links - > not sure the best approach here. > > > > -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
