AniDB RTE: Difference between revisions

m
Line 10: Line 10:
The RTE interface was developed by Microsoft and ported to other browsers by their respective vendors, much like the xmlhttprequest function that is core of AJAX.
The RTE interface was developed by Microsoft and ported to other browsers by their respective vendors, much like the xmlhttprequest function that is core of AJAX.


The content of the edited document is then sent by some way to the server, usually by an HTTP POST command, server then store the content and after display it.
The content of the edited document is then sent by some way to the server, usually by an HTTP POST command, servers then store the content and after display it.


The problem is that vendors more or less follow specifications standards with some not respecting execCommands which control how the editor works. This makes coding an rte a very complicated issue if one intends to support multiple browsers with lots of hacked in code to support/work-around browser quirks.
The problem is that vendors more or less follow specifications standards with some not respecting execCommands which control how the editor works. This makes coding an RTE a very complicated issue if one intends to support multiple browsers with lots of hacked in code to support/work-around browser quirks.


Every rte has a lot of code, which can be either client, server-sided or both, to process the input, clean it up and adapt the data to the servers requirements.
Every RTE has a lot of code, which can be either client, server-sided or both, to process the input, clean it up and adapt the data to the servers requirements.


== The AniDB case ==
== The AniDB case ==
347

edits

MediaWiki spam blocked by CleanTalk.
MediaWiki spam blocked by CleanTalk.