Introduction to the technology of TextDynamic
|[Top] [Chapter] [Previous] [Next]|
The central part is the component WPDLLInt.
Finally there is an editor component available which is available for a wide range of programming languages (VB6, dotNet, VS2003, VS2005, VS2008, VS2010, VS2013 ...).
TextDynamic is a royalty free word processing and reporting control which can be embedded into applications to create text in code, to offer the end user WYSIWYG editing features and to convert document formats, such as RTF to HTML or RTF to PDF.
It is completely customizable. You can use it without the internal toolbars or use XML scripts to create the toolbars according to your needs.
TextDynamic provides all state of the art word processor features, including full header/footer support, sections to have different page sizes in one document, tables, nested tables and a multitude of character and paragraph attributes. Optionally footnotes and text boxes (text frames) are supported.
The TextDynamic component package include support for .NET and also for Access or Visual Basic 6. So you can, at no additional cost, support your legacy applications.
TextDynamic .NET and the OCX work in a very similar way, the interfaces are as interchangeable as possible. But the .NET interface contains some additional features for tight integration, such as the ability to use .NET streams and .NET pictures. So if you have a picture box with a PNG image loaded, the PNG data can be transferred to the text without any conversion necessary.
But also the OCX has a speciality, using the property editor for user defined properties you can load an XML script which configures the editor without the necessity to write a single line of code. This makes it very easy to use the text control in Access since you only have to drop the control and use the property editor.
Since the .NET interface was written in native, managed C# code there is no requirement to ship any OCX with your application. It is not required to modify the registry, simply install the kernel DLL and the assembly DLL into the directory where your dotNET application is installed as well.
Do you have a C++Program which you need a powerful Editor for? Or do you sell a database application which needs an new editing popup dialog. A call to method wptextCreateDialog will solve this problem.