I'm in the process of testing SRVE for use in my application (which has used TRVE since 2004).
My plan is to provide a "normal" TRVE editor, with the option of using SRVE for WYSIWYG. After nearly 5 years of coding for TRVE, I really don't want to *break* any of that.
So is there a collection of guidelines or gotchas for using TRVE and SRVE in the same application? And also for moving from TRVE to SRVE?
I've looked through the SRVE help file and on these forums, but haven't turned up much.
Any advice/suggestions would be appreciated.
Thanks.
-David
Any guidelines for upgrading an app to use SRVE?
-
- Site Admin
- Posts: 17602
- Joined: Sat Aug 27, 2005 10:28 am
- Contact:
Generally, the conversion does not require rewritting old code, only minimal changes are required.
1) All code that used TRichViewEdit control must be applied to TSRichViewEdit.RichViewEdit property.
2) Some properties and events of TSRichViewEdit.RichViewEdit are duplicated in TSRichViewEdit. You can use any of them, but only properties and events of TSRichViewEdit are available at designtime.
3) By default, TRVStyle object is created internally by TSRichViewEdit and accessible as TSRichViewEdit.RichViewEdit.Style. If you need to access its properties and events at design time, place TRVStyle component on form and assign it to TSRichViewEdit.ExternalRVStyle.
1) All code that used TRichViewEdit control must be applied to TSRichViewEdit.RichViewEdit property.
2) Some properties and events of TSRichViewEdit.RichViewEdit are duplicated in TSRichViewEdit. You can use any of them, but only properties and events of TSRichViewEdit are available at designtime.
3) By default, TRVStyle object is created internally by TSRichViewEdit and accessible as TSRichViewEdit.RichViewEdit.Style. If you need to access its properties and events at design time, place TRVStyle component on form and assign it to TSRichViewEdit.ExternalRVStyle.
-
- Site Admin
- Posts: 17602
- Joined: Sat Aug 27, 2005 10:28 am
- Contact: