Are you interested in Lazarus version of TRichView?

News about TRichView and related components

Are you interested in Lazarus version of TRichView/ScaleRichView for Windows?

Yes
17
57%
No
11
37%
Probably
2
7%
 
Total votes: 30

RobertoVG
Posts: 40
Joined: Fri Mar 15, 2013 8:35 pm

Post by RobertoVG » Thu Apr 28, 2016 8:23 pm

lazarus (windows) accepts ActiveX. What do you consider this situation?
or ActiveX to .NET has another feature that out of the .Net another language
You will not have integration?

Martian
Posts: 77
Joined: Sun Apr 03, 2011 7:32 pm

Post by Martian » Thu Apr 28, 2016 8:41 pm

FireMonkey - YES
Lazarus - NO
.NET - NO

snorkel
Posts: 53
Joined: Mon Dec 19, 2005 6:29 am
Location: Milwaukee,WI

Re: Are you interested in Lazarus version of TRichView?

Post by snorkel » Fri Oct 27, 2017 4:02 pm

Any news on Lazarus support?
Lazarus is close to releasing version 1.8 and it looks really good.

Still have had no reason to use Delphi though their sales people have been hounding me with emails to purchase a upgrade to the last version I bought back in 2010, told them it was too expensive.

Sergey Tkachenko
Site Admin
Posts: 13637
Joined: Sat Aug 27, 2005 10:28 am
Contact:

Re: Are you interested in Lazarus version of TRichView?

Post by Sergey Tkachenko » Fri Oct 27, 2017 5:04 pm

We will start porting TRichView to Lazarus soon after releasing TRichView 17.
V17 is already uploaded, but we need to update web site.

SInteZ
Posts: 1
Joined: Wed May 27, 2009 9:15 am

Re: Are you interested in Lazarus version of TRichView?

Post by SInteZ » Thu Nov 23, 2017 7:51 am

Sergey, we are looking forward to the version for Lazarus.

Sergey Tkachenko
Site Admin
Posts: 13637
Joined: Sat Aug 27, 2005 10:28 am
Contact:

Re: Are you interested in Lazarus version of TRichView?

Post by Sergey Tkachenko » Thu Nov 23, 2017 7:56 am

We just released a major update, and now I want to stop adding new features and concentrate on porting.
Lazarus for Windows will be first, because it seems to be the simplest conversion.
(But I want to make some preliminary steps before porting. The main of them - to remove ANSI text processing where it is possible; the internal representation will be Unicode, not ANSI/Unicode switch, as in the current version)

Post Reply