Talk:CSV to HTML translation: Difference between revisions
Content added Content deleted
(screenshots for the extra credit) |
(use Caja to embed html safely) |
||
| Line 19: | Line 19: | ||
:::::: And this one 7,0K (7087 octets.) |
:::::: And this one 7,0K (7087 octets.) |
||
:::::: But well do not hesitate to remove any of these screenshots. [[User:Blue Prawn|Blue Prawn]] 02:48, 14 November 2010 (UTC) |
:::::: But well do not hesitate to remove any of these screenshots. [[User:Blue Prawn|Blue Prawn]] 02:48, 14 November 2010 (UTC) |
||
:: Displaying someone else's HTML without excessive stripping or vulnerability is just what [http://code.google.com/p/google-caja/ Caja] is for. Web-service and Java interfaces are available. —[[User:Kevin Reid|Kevin Reid]] 23:16, 14 November 2010 (UTC) |
|||
Revision as of 23:16, 14 November 2010
Output rendering
Is there any way to show the rendered HTML rather than the raw HTML (without the wiki engine getting in the way? --Paddy3118 15:22, 13 November 2010 (UTC)
- Apart from a screenshot? I don't know. I'm obviously wary of providing a raw HTML channel for fear of arbitrary code. (I suppose loading it into a DOM stripping just about any attribute might work, but the result will obviously not be pretty.) --Michael Mol 16:05, 13 November 2010 (UTC)
- A screenshot could be a good idea, while I guess every contributor would display the HTML code in a different browser. But while images take space, is rosettacode's hosting able to host all these images? Blue Prawn 19:34, 13 November 2010 (UTC)
- As far as bandwidth? I don't know. It really depends on what kind of traffic we get, I suppose. Disk space? RC currently has 30MB of image data in the /images folder, so I'm not particularly worried about it right now. (I do prefer liberal application of tools like pngcrush, though.) As far as variations on implementation...I'm wondering what the current state of offscreen, no-X, no-Win32 render-it-to-a-file is for HTML. That's a plausible way to go about this kind of thing, too. --Michael Mol 22:05, 13 November 2010 (UTC)
- Here are two screenshots with the "links" web browser:
- 2,8K (2866 octets)
- 2,4K (2408 octets)
- (pngcrunsh saved 24 octets on the blackbox one.)
- Blue Prawn 00:54, 14 November 2010 (UTC)
- Heh...I didn't think of that. Using captured output of a text-mode browser to output text suitable for presentation in a fixed-width environment. I might be able to shoehorn that into a MW extension. --Michael Mol 01:51, 14 November 2010 (UTC)
- Other screenshots for the extra credit.
- With a more conventional browser:
- This image takes 9,0K.
- And this one 7,0K (7087 octets.)
- But well do not hesitate to remove any of these screenshots. Blue Prawn 02:48, 14 November 2010 (UTC)
- Heh...I didn't think of that. Using captured output of a text-mode browser to output text suitable for presentation in a fixed-width environment. I might be able to shoehorn that into a MW extension. --Michael Mol 01:51, 14 November 2010 (UTC)
- As far as bandwidth? I don't know. It really depends on what kind of traffic we get, I suppose. Disk space? RC currently has 30MB of image data in the /images folder, so I'm not particularly worried about it right now. (I do prefer liberal application of tools like pngcrush, though.) As far as variations on implementation...I'm wondering what the current state of offscreen, no-X, no-Win32 render-it-to-a-file is for HTML. That's a plausible way to go about this kind of thing, too. --Michael Mol 22:05, 13 November 2010 (UTC)
- Displaying someone else's HTML without excessive stripping or vulnerability is just what Caja is for. Web-service and Java interfaces are available. —Kevin Reid 23:16, 14 November 2010 (UTC)
- A screenshot could be a good idea, while I guess every contributor would display the HTML code in a different browser. But while images take space, is rosettacode's hosting able to host all these images? Blue Prawn 19:34, 13 November 2010 (UTC)
