Richmemo

[typo]

Maybe we can merge the 2 projects, RichMemo and lzRichEdit. Consider this.

[skalogryz]

Sure, but only, if agreement on API is reached.

I'm very careful about creating APIs.. that's why Print() is not in RichMemo yet.
As well as some of the methods (i.e. paragraph numbering) is not officially "released" (even though available for win32)
I found my way out of not being compatible with delphi RichEdit, by using helpers.

I don't see the component's API as reflection of WinAPI. Just like you noted - WinAPI might be a bit hostile to a developer

[typo]

What is wrong about Print method? It works quite well in Windows. I think it will be difficult to you making something different from that.

[skalogryz]

What is wrong about Print method? It works quite well in Windows. I think it will be difficult to you making something different from that.

well...
There's RichEdit delphi method Print.

Code: [Select]

procedure TRichEdit.Print(const caption: string);...and people were complaining about not being able to setup margins.
I believe that's why lzRichEdit finished with

Code: [Select]

procedure Print(const DocumentTitle: string; Margins :TMargins)
I believe, that giving an option just for margins is still not enough, and the method should be something like this.

Code: [Select]

procedure Print(const PrintOptions: TPrintOptions)
where TPrintOptions looks like this:

Code: [Select]

  TPrintOptions = record
    caption : String;
    margins : TMargins;
    pages   : array of TPageRange;
    pagesCount : integer;
    target : TCanvas; // for preview printing
    targetRect : TRect; // for preview reszing
    ... something else? + any future extension of printing could be consumed.
  end;

With that method, a backward (delphi) compatible method can be easily implemented.

[skalogryz]

I'm currently preparing cross-platform apis for low-cost images insertion. See a demo at youtube

[typo]

Good.

Chat apps will like this.

[typo]

I found my way out of not being compatible with delphi RichEdit, by using helpers.

I think it can be a problem because lzRichEdit is entirely compatible with Delpihi, according to general guidelines of Lazarus.

[skalogryz]

yes, being Delphi compatible is certainly a plus. Which is more of a burden for me than a benefit.

A thus, It has never been a priority for RichMemo. Instead a cross-platform functionality. But I'm glad I was able to get avoid sub-classing.

[typo]

The lack of a RichEdit in Lazarus is a great problem for converting projects from Delphi.

Workarounds go from TMemo to IpHtmlPanel.

[typo]

Maybe Lazarus can house the 2 ways, one of Delphi compatibility, and another, with an independent way. I don't consider this (non-compatibility) as a not worthy way, but a Delphi user rages.

[skalogryz]

Richmemo provides basic richedit properties: SelAttributes and Paragraph through a class helper - just add richmemohelpers unit to uses section. As well as find() method.

[arneolav]

Uses ...RichMemo, RichMemoHelpers;

---> unit1.pas(1,1) Fatal: Unit RichMemoHelpers searched but RichMemo found 

 Lazarus 1.2.6 r46529 FPC 2.6.4 i386-win32-win32/win64

[skalogryz]

what's your RichMemo package revision? The unit has been added with r3752 (19 nov 2014)
The latest richmemo update was with r3847 (20 dec 2014)

[arneolav]

Version 1.0.0 , Same as SourceForeget, no update ...?

[typo]

Try my RichMemo revision, only 45KB.

What is special about this revision? Well, it compiles and installs fine on Windows.