> About 2:
> The whole Lazarus IDE works with strings, not widestring.
> The LCL will use strings, because that is more compatible to
> existing code.
> Existing LCL applications using synedit uses strings.
>
> It seems to me, we should merge with the normal synedit,
> instead of unisynedit. But maybe I missed a point?

Maybe they want to keep both an ANSI SynEdit and a Unicode SynEdit. In that
case if Lazarus one is Unicode only it should contribute to the UniSynEdit
all Unicode stuff and to both SynEdit and UniSynEdit the rest (problem may
be that they did their own codefolding - not sure which one works better)

----------------
George Birbilis ([EMAIL PROTECTED])
Microsoft MVP J# for 2004-2006
Borland "Spirit of Delphi"
* QuickTime, QTVR, ActiveX, .NET, Delphi VCL, XML, IPC
http://www.kagi.com/birbilis
* Robotics
http://www.mech.upatras.gr/~Robotics
http://www.mech.upatras.gr/~robgroup




  _____  

avast! Antivirus <http://www.avast.com> : Outbound message clean. 


Virus Database (VPS): 0630-1, 24/07/2006
Tested on: 25/7/2006 10:41:03 p?
avast! - copyright (c) 1988-2006 ALWIL Software.



_________________________________________________________________
     To unsubscribe: mail [EMAIL PROTECTED] with
                "unsubscribe" as the Subject
   archives at http://www.lazarus.freepascal.org/mailarchives

Reply via email to