Re: How about different input styles when posting? (HTML , TEXT, POD, ePod...)

Examples are all very well, but since this has been discussed at least a few times before, what's needed is code, and actual ideas of where in the sequence this encoding takes place, etc. (previous discussion)

If you don't know, the problem (as I gather it) is: Either we parse on input (ie when the user hits the 'Create' button), once, and store the HTML result. In which case when someone tries to edit their post, they may not recognise it, and complaints will ensue. Or, we parse on output, ie every time someone views the page, which puts more strain on the server. (Can't be cached, because there are user specific psuedo links, etc.

Then theres the whole: 'How do we parse what' discussion..

Anyhow, nice idea, but suggesting what, and not saying how, probably won't get you very far.

Personally, I'd like a whole cute little editor with buttons for italics, bold etc.. but pigs may well fly..

Comment on Re: How about different input styles when posting? (HTML , TEXT, POD, ePod...)

Replies are listed 'Best First'.
Parsing/Caching problem by radiantmatrix (Parson) on Nov 25, 2004 at 14:25 UTC
Of course, there is another option, but methinks it would be quite a bit of work (perhaps not practical). Parse on input, storing the original in a separate table, and the HTML in a "cache" table. The server load would increase a little, as there would be an extra query when a user views their own node, but not horrible. Of course, that might take a serious restructure of the code, so I'm not sure how good an idea it would be. Just something to ponder... radiantmatrix `require General::Disclaimer;` Perl is	[reply]
Re^2: How about different input styles when posting? (HTML , TEXT, POD, ePod...) by Anonymous Monk on Nov 25, 2004 at 12:49 UTC
Did you saw the codes in the end of the node? There is how.	[reply]
Re^3: How about different input styles when posting? (HTML , TEXT, POD, ePod...) by castaway (Parson) on Nov 25, 2004 at 13:34 UTC
That's just a general 'convert from A to B' (yes, I did miss it, the node was just too long to read it all) .. we're still missing a definition of how it fits in with the node creation/display business. And if you don't know the code (who does) you can go look at Everything2 to see how PM works (more or less). C.	[reply]