> > - Move all (all "non-basic" at least) editor commands to a separate
> > unit and implement each command on a separate method or class. I'm
> > inclined to make them TAction descendants to unify shortcut handling,
> > but I'm not set yet...
>
> What would we gain?
>
Reuse ?
In theory (depending on how that unit is implemented).
It should be designed to work on any stringlist (which is what I believe the
underlying data-set in synedit is), so it can update a synedit, or a memo or
whatever and can be used for other components or heck if called from code
directly to do easy advanced stringset parsing.
Imagine if we could tell a programmer that the stringset he is trying to
modify in a certain way before displaying - well he can access the search|
replace menu's own command from his code with all it's features|power.
Right now most string parsing seems to be handled by pos, copy and delete -
which works but why should people need to write the same code over and over
when lazarus already contains it ?
A.J.
Some might notice I am highly in favour of lazarus having MORE than delphi
ever did - to make delphi users SWOON over it :)
--
"there's nothing as inspirational for a hacker as a cat obscuring a bug
by sitting in front of the monitor" - Boudewijn Rempt
A.J. Venter
Chief Software Architect
OpenLab International
www.getopenlab.com
www.silentcoder.co.za
+27 82 726 5103
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
