[LazFreeType] Patches

[circular]

Here is a new patch :
- external access about hinted option
- font hinting when text center
- OnRenderText event added
- line ending when splitting

[Ask]

I have applied first part of the patch in r40120.

I have few questions about other parts:

>external access about hinted option
Are there other descendants of TFreeTypeRenderableFont?
If so, they should be updated to be compilable after this change.

>line ending when splitting
I can not understand what this change is supposed to do.
Can you write a commit message for it?

Also, code of RemoveLineEnding function seems too complicated.
Is not it equivalent to the following?

Code: [Select]

Result := (index <= Length(s)) and (s[index] in [#13, #10]);
if Result then
  if (index + 1 <= Length(s))  and ([s[index + 1], s[index]] = [#13, #10]) then
    Delete(s, index, 2)
  else
    Delete(s, index, 1);


[circular]

>external access about hinted option
Are there other descendants of TFreeTypeRenderableFont?
If so, they should be updated to be compilable after this change.

No.

>line ending when splitting
I can not understand what this change is supposed to do.
Can you write a commit message for it?

When there are #13#10 chars in a string, they are taking into account when splitting the text, i.e. text goes to a new line before reaching the maximum width.

Also, code of RemoveLineEnding function seems too complicated.
Is not it equivalent to the following?

Code: [Select]

Result := (index <= Length(s)) and (s[index] in [#13, #10]);
if Result then
  if (index + 1 <= Length(s))  and ([s[index + 1], s[index]] = [#13, #10]) then
    Delete(s, index, 2)
  else
    Delete(s, index, 1);


I would say so, but this part seems slower (more complicated for the compiler) :

Code: [Select]

[s[index + 1], s[index]] = [#13, #10]

[circular]

Here is another patch to apply to easylazfreetype.pas :
- OnRenderText event moved upwards to be accessible from TFreeTypeRenderableFont

[circular]

And another to add text decoration (underline and strikout) in TIntfFreeTypeDrawer :

[Ask]

Are there other descendants of TFreeTypeRenderableFont?

No.

Ok, committed in r40130

text goes to a new line before reaching the maximum width.

... but this part seems slower (more complicated for the compiler)

Ok, I have taken a look from the optimization point of view.
Committed modified version of this change in r40131-40133. Main differences are:
1) No extra calls to "Delete" (note that "Delete" contains a loop)
2) No extra loop variable (in you version, "p" did the same as "left")

OnRenderText event moved upwards to be accessible from TFreeTypeRenderableFont

Committed in r40134. Please create patches from "lazarus" or "lazutils" directory, not from the disk root. Otherwise, patches include absolute paths which I have to edit manually before applying.

add text decoration (underline and strikout)

Committed with minor modification in r40135.
However, I have doubts about design -- should not underline/strike-out be a property of a font?

[circular]

Thanks.

add text decoration (underline and strikout)

Committed with minor modification in r40135.
However, I have doubts about design -- should not underline/strike-out be a property of a font?

Oh you're right. I'll try to move it there.

[circular]

Here is the patch to move text decoration into font :

[Ask]

Applied in r40147.
In the future, please update your working copy before creating a patch --
the one you sent reverted changes I made in r40131.

[circular]

Alright.

[circular]

This is not exactly about FreeType, but there are drawing routines in the drawer that could be moved to FPCanvas.

[Ask]

I have no commit access to the FPCanvas. You can create a feature request on the bug tracker.

Note, however, that FPC releases are very rare, and Lazarus traditionally allows some lag in FPC version, so even if those routines are copied to FPCanvas, they must remain in LazFreeType until FPC 2.8 comes out *and* becomes a minimum required version for Lazarus.

[circular]

I understand.

Just in case, to whom could I submit patches for that?

[BigChimp]

The bugtracker.

Note: while I agree with ask's post, if it makes sense architecturally to move stuff into FPC, I think it should be done. Yes, it will take some time to filter through to Lazarus stable releases but better late than never.

You can then use conditional compilation to check for FPC version in order to support old and new FPC up to the time a new stable FPC is released... or alternatively just live with duplicate code for a while... (which I wouldn't recommend)

[circular]

If I apply some modifications to the FP code, it is not compiled again, object files stay the same and added functions are not available. How to recompile FP?