TMS Scripter Pro XE2 update 4 problems

BIZ TMS Scripter
1

Hi,

 
I just bought TMS Scripter Pro and I want to share my problems installing it in Delphi XE2 update 4.
The Delphi XE2 I have is the Delphi STARTER edition.
 
The installation step by step:
1) I removed the 'normal' TMS scripter (which I bougth before the PRO) completely from Delphi and also uninstalled it.
2) Started the Setup.exe of the PRO which aborts with an error (could not copy a *.blp file). I had this same problem with the setup of the 'normal' TMS scripter when I installed it, probably this has something to do with the (non) availability of the external compiler of the Delphi Starter edition.
3) Uninstall the PRO again.
4) Install the pro with setup.exe again (this time without the checkboxes for Delphi and C builder on).
5) Open your manual to do a manual install. Opening Delphi and adding all the directories as stated ('source', 'source\advmemo', 'source\designer' to the libray path. Sofar so good.
6) According to your manual 'FILE\OPEN' the 'asscriptproxe2.dpk' file.
7) Loading the *.dpk file gives the following error 'Component 'TAdvMemo' not found.
8) So I do a manual install ('Component\Install component') in Delphi of the 'advMemoReg.pas' file. Which took me a while to find. I finally found it after a search in the files on the word 'register'. TAdvMemo installed with no problems.
9) Loading the 'asscriptproxe2.dpk' again. This time the following error 'Component TMSIDE not found' came up.
10) So, again a manual component install this time the file 'IDEReg.pas' was the (un)lucky one. Now Delphi came with a LOADS of errors. In all the files in de 'designer' directory Delphi issued errors on the 'uses' clauses (Graphics.dcu not found, Forms.dcu not found etc.).
11) In ALL the files in the designer directory I had to change the uses clauses manually for the correct name spaces (Vcl.Graphics instead of Graphics, Vcl.Forms instead of Forms etc.). Since there are about 30 *.pas files in this directory and I had to change averagely 10 statements per file, you can do the math on how many statements I modified.
12) Finally the TmsIDE component installed without errors.
13) Loading the  'asscriptproxe2.dpk' for the THIRD time and building/installing it finally went OK (with some minor glitches which were completely due to me).
 
The exampe of the IDEPro works fine, so I assume the installation is correct.
 
In a nutshell: It took me more then 3 hours to install TMS scripter Studio PRO.
Probably the problems have a LOT to do with upgrade 4 in Delphi XE2 (and maybe a tiny bit with me?)
I still have some warnings from the Delphi compiler:
- in file ScriptCtrls.pas - 'Symbol RESUME is deprecated'. (twice)
- in file ObjectInspector.pas - 'Symbol ThemeServices is deprecated: 'Use StyleServices'.(three times)
 
Conclusion:
- an update in the documentation about the manual install is in order.
- an update of TMS Scripter (pro) for XE2 update 4 is in order
- (If possible) an update of your automated setup wizard is in order
 
I hope you will upgrade the scripter (pro) soon (please insert also the all new and improved TadvMemo :) so everything works hunkydory with XE2 update 4 again :)
 
By the way, I realize this message could be interpreted as negative criticism, but it is not meant that way, I am still very happy with scripter studio.
 
regards,
André Lubke
 
 
2

André,


>>>2) Started the Setup.exe of the PRO which aborts with an error (could not copy a *.blp file). I had this same problem with the setup of the 'normal' TMS scripter when I installed it, probably this has something to do with the (non) availability of the external compiler of the Delphi Starter edition.<<<

Correct, for Starter Edition, scripter must be installed manually

>>>7) Loading the *.dpk file gives the following error 'Component 'TAdvMemo' not found.<<<

Here was the cause of problems. You could just ignore all error messages, since this is common in Delphi packages where some forms (usually design-time forms) use the components of the package itself. Just ignore the errors here, and build/install the package normally. You don't have to manually install other components in other packages, nor change scripter source code.


3
 
Wow,
This must be the quickest response I've ever seen :)
----- 2. I thought so. Maybe something to mention (or check) in the installation wizard and the documentation?
----- 7. Also something to mention in the documentatione ('When you see an error 'Tadvdmemo not found' just ignore it etc....
 
Thanks for the reply.
I am going to de-install and start the procedure fresh again.
 
Kind regards,
André Lubke