trichview.com

trichview.support.examples




How to install and update TRichView and addons: Extended guide


Return to index


Author

Message

Sergey Tkachenko

Posted: 09/05/2003 14:52:53


Almost all the information below can be found in install.txt/readme.txt for

TRichView and its addons.

An extended step by step instruction can be useful nevertheless.



1) ABOUT SOURCE FILES (PAS, DPK, DCU, ... ETC.)

The simplest way for updating - installing updates of the components in the

same directory as their previous versions.

In this case you do not need to delete files of the old version of the

components because files of the new one override them.

But if you have, for example, previously installed TRichView 1.7.10 in one

directory, and newly installed TRichView 1.7.26 in another directory, this

may lead to problems. In this case, delete all files of old version (delete

the directory with *.pas and *.dcu files in Windows Explorer or other file

manager). Or better, copy files of newer version to the location of the old

version (override it), and delete a new directory.

The same is for RichView addons: RvHtmlImporter, RvXML, RichViewActions.

Each of them must be installed in their own directory, but make sure that

there are no different versions of the same component in different

directories! The same applies to any third-party components that you use,

not only to TRichView and its addons.


Note: word "install" above means extracting/copying files of components to

the specific directory, not installing components in Delphi


2) ABOUT THE FIRST INSTALLATION OF THE COMPONENTS

I assume you use D7, but for other versions of Delphi the procedure is the

same.


2.a) Installing TRichView

- Open RVPkgD7.dpk (File | Open). Click [Install] button in the package

window.

- Open RVDBPkgD7.dpk (File | Open). Click [Install] button in the package

window.

- menu Tools | Environment Options, tab Library, click [...] button near the

"Library path" edit-box. In the "Directories" dialog, add the directory to

TRichView files (PAS, DPK, etc) in the list. Close all these dialog clicking

[OK] buttons.


2.b) Installing RvHtmlImporter.

This procedure must be performed after performing all the steps of (2.a)

- Open rvhtmld7.dpk (File | Open). Click [Install] button in the package

window.

- menu Tools | Environment Options, tab Library, click [...] button near the

"Library path" edit-box. In the "Directories" dialog, add the directory to

rvHtmlImport files (PAS, DPK, etc) in the list. Close all these dialog

clicking [OK] buttons.


2.c) Installing RvXML

This procedure must be performed after performing all the steps of (2.a)

It is almost the same as (2.b):

- Open rvxmld7.dpk (File | Open). Click [Install] button in the package

window.

- menu Tools | Environment Options, tab Library, click [...] button near the

"Library path" edit-box. In the "Directories" dialog, add the directory to

RVXML files (PAS, DPK, etc) in the list. Close all these dialog clicking

[OK] buttons.


2.d) Installing RichViewActions.

This is the most tricky, because they have both run-time and design-time

packages, and because they may use RvHtmlImport and RvXML packages.

RichViewActions require TRichView, so they must be installed after

performing all the steps of (2.a).

RvHTMLImport allows RichViewActions to import/paste HTML files. If you want

this functionality, RichViewActions must be installed after RvHTMLImport

(after

performing all steps of (2.b)).

RvXML allows RichViewActions to save and load documents in XML format. If

you want this functionality, RichViewActions must be installed after RvXML

(after performing all steps of (2.c)).

- Open RichViewActions.inc in Delphi (File | Open, choose the file filter

for "Any files (*.*)"). The file will be opened in the Delphi text editor.

  If you want RichViewActions to use RvHTMLImport, remove the dot from the

line {.$DEFINE USERVHTML}

  If you want RichViewActions to use RvXML, remove the dot from the line

{.$DEFINE USERVXML}

  Save RichViewActions.inc

- Open RvActionsRunD7.dpk  (File | Open). Click [Compile] button in the

package window. IMPORTANT: do not click [Install]! This is a run-time

package, it cannot be installed. On compiling, Delphi will ask you to add

rvhtmld7 and rvxmld7 in the list of dependencies ("required") of the

package. Confirm it.

- menu Tools | Environment Options, tab Library, click [...] button near the

"Library path" edit-box. In the "Directories" dialog, add the directory to

RichViewActions files (PAS, DPK, etc) in the list. Close all these dialog

clicking [OK] buttons.

- (there are alternative ways to do this step; this one may be not the most

convenient, but the simplest to explain). Find the compilation result of the

package: RvActionsRunD7.bpl (it must be in <DELPHI DIRECTORY>\Projects\Bpl\;

<DELPHI DIRECTORY> is usually "c:\program files\borland\delphi7"). Move this

file to <WINDOWS DIRECTORY>\System32\. Move, do not copy! There must be only

one instance of this file! Use Windows Explorer or other file manager to do

this.

- Open RvActionsD7.dpk (File | Open). Click [Install] button in the package

window.


That's all. If you want to use Addict3 with RichViewActions, additional

steps are required. They are almost the same as for installing rvHtmlImport

and rvXML.


3) ABOUT UPDATES

So, you downloaded and extracted files of new version of TRichView, and may

be, of some of its addons.

You followed the rules of (1) and (2).

Now you need to install updates in the Delphi environment.

Updates must be installed in the same sequence as in (2):

- update RvPkgD7.dpk

- update RvDbPkgD7.dpk

- update RvHTMLD7.dpk and RvXMLD7.dpk (they are independent, so the order of

their update is not important)

- update RvActionsRunD7.dpk

- update RvActionsD7.dpk.

Updating is simpler than the first time installing because all paths to the

source files are already in the Delphi library paths list. Of course, if you

extracted files of new versions of the components in the same directories as

their old versions. Otherwise you need to update Delphi library paths (menu

Tools | Environment Options, tab Library).


3.a) Updating TRichView

- Open RVPkgD7.dpk (File | Open). Click [Compile] button in the package

window.

- Open RVDBPkgD7.dpk (File | Open). Click [Compile] button in the package

window.

After compiling RVPkgD7.dpk, you may get a sequence of error messages by

Delphi:

- "XXX could not be located in the dynamic link library YYY.dpk". Click [OK]

in such messages.

- "Can't load package ZZZ. AAA cannot be found. Do you want to attempt to

load this package the next time a project is loaded? [Yes/No]". Click [Yes].

These annoying messages will continue appearing from time to time until you

recompile all the packages that are dependent on RvPkgD7.dpk. Always click

[OK] and [Yes].

These messages appear not for all updates of TRichView, only if there were

some important changes in the interface part of TRichView units.


If you want to update only version of TRichView itself, and files all addons

were not changed, the subsequent steps are required only if you got these

error messages. Of course, if you update not only TRichView but also their

addons, you need to perform the steps below.


3.b) Updating RvHtmlImporter.

This procedure must be performed after performing all the steps of (3.a)

- Open rvhtmld7.dpk (File | Open). Click [Compile] button in the package

window.


3.c) Installing RvXML

This procedure must be performed after performing all the steps of (3.a)

- Open rvxmld7.dpk (File | Open). Click [Compile] button in the package

window.


3.d) Installing RichViewActions.

This procedure must be performed after performing all the steps of (3.a),

and after (3.b) and (3.c) if RichViewActions use RvHTMLImport and RvXML.

- Your changes (see 2.d) in RichViewActions.inc are overwritten by the files

of the update, so you need to repeat them:

  Open RichViewActions.inc in Delphi (File | Open, choose the file filter

for "Any files (*.*)". The file will be opened in the Delphi text editor.

  If you want RichViewActions to use RvHTMLImport, remove the dot from the

line {.$DEFINE USERVHTML}

  If you want RichViewActions to use RvXML, remove the dot from the line

{.$DEFINE USERVXML}

  Save RichViewActions.inc

- Open RvActionsRunD7.dpk  (File | Open). Click [Compile] button in the

package window. IMPORTANT: do not click [Install]! This is a run-time

package, it cannot be installed. On compiling, Delphi will ask you to add

rvhtmld7 and rvxmld7 in the list of dependencies ("required") of the

package. Confirm it.

- Find the compilation result of the package: RvActionsRunD7.bpl (it must be

in <DELPHI DIRECTORY>\Projects\Bpl\; <DELPHI DIRECTORY> is usually

"c:\program files\borland\delphi7"). Move this file to <WINDOWS

DIRECTORY>\System32\. Move, do not copy! There must be only one instance of

this file! Use Windows Explorer or other file manager to do this.

Possible problem: RvActionsRunD7.bpl may be locked by Delphi. Solution:

close Delphi, move the file, run Delphi again (if you exit Delphi at this

point, it may display an access violation message on closing; do not worry:

all will be ok when you finish updating).

- Open RvActionsD7.dpk (File | Open). Click [Compile] button in the package

window.


That's all.


====================

For advanced users:

Explanations why moving of RvActionsRunD7.bpl is required:

Run-time packages must be located in directories where Windows can find

them. Windows searches for libraries in its system directories and in

directories specified in the system environment variable PATH.

RvActionsRunD7.bpl must be in one of such directories.

May be <DELPHI DIRECTORY>\Project\Bpl\ is already in the PATH? (this is

possible for new versions of Delphi).

You can try to omit the step of moving RvActionsRunD7.bpl (even in this

case, RvActionsRunD7.bpl must be EITHER in <DELPHI DIRECTORY>\Project\Bpl\

OR in Windows system32 directory, not in both places! there must be only one

instance of BPL).

If RvActionsD7.bpl is successfully installed and ActionTest can be compiled,

all is ok and you do not need this step.









Powered by ABC Amber Outlook Express Converter