Create TRichEdit(version lazarus LCL) to remplace TRichEdit(version delphi VCL)

[codedeep]

Create TRichEdit (version lazarus LCL) to remplace TRichEdit (version delphi VCL)

This will help to migrate applications from Delphi to Lazarus

Idea for Lazarus comunity.

 

[Vincent Snijders]

For carbon and win32 there is already a replacement: TRichMemo.

[codedeep]

Yes. 
I know.
Rename it and include it in the migration tool project

Please.

[Vincent Snijders]

Make a request to the author, maybe he did this on purpose, to make sure you notice that you notice the difference. Maybe the exact properties and methods are not identical and you have to port it tool.

What migration tool project do you mean? If you mean the converter, then this is mostly a contributed tool, since people using Lazarus already don't need that much.

[Astral]

I use TRichEdit on Delphi.  For a long time I used the TNT version, TTntRichEdit, which supported Unicode before Delphi 2009 came out.

Now I'm using SynEdit on Lazarus.  Perhaps I should be using TRichMemo instead?

Maybe it will solve my character spacing problems. 

   This little icon reminds me of the "dining philosophers" problem!

Such cute icons.

I don't really need the RTF capabilities (Rich Text Format) of TRichEdit, since I mostly process plain text.  But it's still convenient and provides all the support I need.

[skalogryz]

TRichMemo is not compatible 100% with TRichEdit, TRxRichEdit and TTntRichEdit.

That's why it's called *Memo, rather than *Edit

The reason for this, is that, imho, TRichEdit interface is rather heavy and not convenient.

So, porting TRichEdit code to TRichMemo would not be very easy.

On the other hand TRichMemo is a wrapper over cross-platform widget TWSCustomRichMemo (see WSRichMemo unit).
So it's quite possible to create TLazRichEdit, that would have the identical API interface, as delphi's TRichEdit, TRxRichEdit or TTntRichEdit have.

OR, maybe add TRichEdit methods and properties to TRichMemo (it's better to sub-class the control).

Personally, I'm not much interested in making delphi compatible component, but surely you can do it yourself. That's the power of opensource

[codedeep]

ummmm

RTF is the problem.
A lot of information available

http://en.wikipedia.org/wiki/Rich_Text_Format

or

other info site:  http://www.snake.net/software/RTF/

good examples.