Talk:CSV to HTML translation: Difference between revisions
Content added Content deleted
(→Output rendering: Not too worried about image data for the moment. Pondering offscreen rendering.) |
|||
| Line 3: | Line 3: | ||
: 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.) --[[User:Short Circuit|Michael Mol]] 16:05, 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.) --[[User:Short Circuit|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? [[User:Blue Prawn|Blue Prawn]] 19:34, 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? [[User:Blue Prawn|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. --[[User:Short Circuit|Michael Mol]] 22:05, 13 November 2010 (UTC) |
|||
Revision as of 22:05, 13 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)
- 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)