I am aware of previous post;
The above thread mentions that RadEditor is not really recommended for documents over 100k for text and html. Some work arounds included disabling undo/redo button, and filters. To be fair this is a problem in every html based editor I've reviewed so far, perhaps to a less extent text editors running under Chrome. Even web based editors running under chrome eventually too, succumb to latency issues as the document size increases, and Chrome has some perceived phone home ad issues that my client would rather not deal with.
My question is, if you have documents, all much bigger than 100k, perhaps an order of magnitude greater, say 1-3 meg or so and you were hoping for a web solution what can one do? I was groping around for perhaps a streaming/paging solution (where 100k or so at a time can be loaded), but RadEditor and the others don't seem to support this in their api's (I could be mistaken in this). Another solution is to break documents up into 100k bits, or as it were "chapter or section" bits, not sure my customer will go for this since it greatly complicates search and replace and the like operations that need to be done across multiple sections.
Unfortunately, unless I can find a solution this problem I will have to punt on a web solution and go win64 native application, which I would rather not do.
http://www.telerik.com/community/forums/aspnet-ajax/editor/radeditor-character-table-limit.aspx
The above thread mentions that RadEditor is not really recommended for documents over 100k for text and html. Some work arounds included disabling undo/redo button, and filters. To be fair this is a problem in every html based editor I've reviewed so far, perhaps to a less extent text editors running under Chrome. Even web based editors running under chrome eventually too, succumb to latency issues as the document size increases, and Chrome has some perceived phone home ad issues that my client would rather not deal with.
My question is, if you have documents, all much bigger than 100k, perhaps an order of magnitude greater, say 1-3 meg or so and you were hoping for a web solution what can one do? I was groping around for perhaps a streaming/paging solution (where 100k or so at a time can be loaded), but RadEditor and the others don't seem to support this in their api's (I could be mistaken in this). Another solution is to break documents up into 100k bits, or as it were "chapter or section" bits, not sure my customer will go for this since it greatly complicates search and replace and the like operations that need to be done across multiple sections.
Unfortunately, unless I can find a solution this problem I will have to punt on a web solution and go win64 native application, which I would rather not do.