[
https://issues.apache.org/jira/browse/WAVE-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257472#comment-13257472
]
Yuri Zelikov commented on WAVE-343:
-----------------------------------
IMO the hardest task here is to decouple GWT client side code from server side
code, i.e. server side cannot use obfuscated Css classes that are available
only at the client. Luckily, Pat Coleman handled some of the issues in his
patch -
http://code.google.com/p/wave-protocol/source/detail?r=963dfe24c2e2cec8faf1f018f4833d0f72cf686a
You can also take a look at the waveinabox.net server side rendering code at
https://github.com/vega113/WaveInCloud/tree/d7e2ef9a78a567ee137f09214f82542322bd2d34/src/org/waveprotocol/box/server/rpc/render
Regarding the export feature - I think that the best solution would be to
extend Robot API so it will allow to request a rendered HTML per
blip/wavelet/wave.
The rendered HTML is waveinabox.net looks a bit different from original, but
it is due to amount of effort i could put into it and for search engine
optimization.
Exposing the wave rendered into pure HTML to the Google crawler as is -
usually causes Google to misinterpret the content. For example, it can't
distinguish between blip authors (non relevant content) to blip text (the
actual content). If you look for 2 most relevant keys for a wave where Bob is
an active participant, it would be "Edit" and "Bob" -because every blips has
the words. So I decided to remove the clutter from the rendered HTML to make
life easier for search engines.
I think it is entirely possible to generate HTML rendered wave that looks
exactly as in the web client.
> Render utility of waves in server side
> --------------------------------------
>
> Key: WAVE-343
> URL: https://issues.apache.org/jira/browse/WAVE-343
> Project: Wave
> Issue Type: Improvement
> Reporter: Vicente J. Ruiz Jurado
>
> We need some render utility in the server side for export public waves,
> embedding, etc.
> Nowadays in kune we are using some hacked code from:
> https://code.google.com/p/google-wave-splash/
> Yuri is using another different approach in waveinabox, but I see differences
> between the render wave and the original wave, for instance:
> http://waveinabox.net/render/wave/waveinabox.net/w+asV6jXTNo7A
> I think that the goal was to use the same client code in the server, so waves
> are rendered equally. See Yuri email:
> http://mail-archives.apache.org/mod_mbox/incubator-wave-dev/201105.mbox/%[email protected]%3E
> Yuri, which is the status of this task? Any advice/tip?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
