TSRichViewEdit for large volumes of text and images

[tiagosis]

Hello, I use TSRichViewEdit for large volumes of text and images, it turns out that the size of the file in my database, field type LONGTEXT, is huge. This causes extreme slowness when saving and opening stored texts, how can I get around this? thanks.

[Sergey Tkachenko]

Please send me a sample document (the exact content of LONGTEXT field) to email richviewgmailcom, I'll try to see how to make it smaller.

[Sergey Tkachenko]

I did not receive a reply yet, but I can suggest some general ideas.

1. Since you use a field type that can contain only text, not binary data, I guess you save document as RTF (Rich Text Format). RTF documents are the largest. If you choose DocX or RVF (and a binary field type), data size will be much smaller.

2. If you save documents manually, call DeleteUnusedStyles(True, True, True). Always call it immediately after loading. If you use "save and exit" command, call it before saving too (DeleteUnusedStyles cannot be called in the middle of editing, because it makes data in undo buffer incorrect, and thus requires calling ClearUndo). If you use TDBSRichViewEdit, make sure that its AutoDeleteUnusedStyles = True.

3. The following options make RTF smaller:
- rvrtfDuplicateUnicode must be excluded (to avoid saving text both in Unicode and non-Unicode representations)
- rvrtfSaveBitmapDefault and rvrtfPNGInsteadOfBitmap must be included (to save bitmaps and other graphic types unsupported by RTF as PNG images)

[tiagosis]

Hello, I just sent an example text to your email. Adding some questions, yes, I use it in RTF format with the field in the database configured as LONGTEXT, it turns out that before we didn't have the need to save images, just text, and over time the need to include images arose in the text, and it works, but it generates extremely large and slow data. I have two situations that I need to resolve:
1 - reduce the size of the data as it is causing problems even when backing up the database due to its size.
2 - text manipulation in TSRichViewEdit is extremely slow both to open and to save.

[tiagosis]

I already did as you instructed me before saving the text in the database, but I believe the text size will have to be even smaller...
example of my code before saving:

var
_stream : TMemoryStream;
begin
try
_stream := TMemoryStream.Create;

SRichViewEdit1.RichViewEdit.RTFOptions := [rvrtfSaveJpegAsJpeg,
rvrtfSavePngAsPng,
rvrtfSaveBitmapDefault,
rvrtfPNGInsteadOfBitmap,
rvrtfSaveStyleSheet,
rvrtfSaveDocParameters];

SRichViewEdit1.RichViewEdit.DeleteUnusedStyles(True, True, True);
SRichViewEdit1.RichViewEdit.SaveRTFToStream(_stream,false);
_stream.Position := 0;

[Sergey Tkachenko]

Probably something wrong with your test, these settings reduced your RTF size from 298 Mb to 25 Mb.

If you decide to use RVF or DocX, I recommend converting bitmap images to PNG, because no image format conversion occurs when saving in these formats.

The procedure for conversion is below:

Code: Select all

procedure TForm3.EnumItemsProc(RVData: TCustomRVData;
  ItemNo: Integer; var UserData1: Integer; const UserData2: TRVUnicodeString;
  var ContinueEnum: Boolean);
var gr: TGraphic;
    png: TPngImage;
    Tag: TRVTag;
    VAlign: TRVVAlign;
    s: TRVUnicodeString;
begin
  if RVData.GetItem(ItemNo) is TRVGraphicItemInfo then begin
    RVData.GetPictureInfo(ItemNo,s,gr,VAlign,Tag);
    if gr is TBitmap then
    begin
      png := TPngImage.Create;
      png.Assign(gr);
      RVData.SetPictureInfo(ItemNo,s, png,VAlign,Tag);
    end;
  end;
  ContinueEnum := True;
end;

procedure TForm3.ToolButton12Click(Sender: TObject);
var v: Integer;
begin
  v := 0;
  RichViewEdit1.RVData.EnumItems(EnumItemsProc, v, '')
end;

After that, this document's size: 17 Mb as RVF, 10 Mb as DocX.
DocX is smaller, because it is zipped.
Please note that you need to use a binary field type for these formats.

[tiagosis]

I decided to follow your recommendation and changed the field type to LONGBLOB to receive the content, I started saving as Docx with "SRichViewEdit1.RichViewEdit.SaveDocXToStream(_stream,false);", the size decreased considerably to 10mb.

however,

_stream := TMemoryStream.Create;
(FieldByName('TEXT') as TBlobField).SaveToStream(_stream);
_stream.Position := 0;
SRichViewEdit1.RichViewEdit.LoadFromStream(_stream,rvynaAuto);
SRichViewEdit1.RichViewEdit.Format;

it stopped working for me.

[Sergey Tkachenko]

LoadFromStream must detect DocX.

I suggest making a test: when storing to DB, story a copy to a file.
Post data, then load content from DB to a file. Compare with the original file.

[tiagosis]

when I use: SRichViewEdit1.RichViewEdit.SaveRVFToStream(_stream,false);

everything works perfectly, including:

(FieldByName('TEXT') as TBlobField).SaveToStream(_stream);
_stream.Position := 0;
SRichViewEdit1.RichViewEdit.LoadFromStream(_stream,rvynaAuto);
SRichViewEdit1.RichViewEdit.Format;

[tiagosis]

I would like to say that despite having purchased the latest version of TRichView, I haven't updated it yet, I'm using version 17. Could this be having an influence?

[Sergey Tkachenko]

Yes. DocX import was implemented in version 19.