TextPad+Validator3.05+XP
Moderators: AmigoJack, bbadmin, helios, Bob Hansen, MudGuard
-
Ken Grace
TextPad+Validator3.05+XP
I have installed TextPad 4.62 + CSE HTML Validator 3.05 on a Windows XP machine but cannot call Validator to run and return results in the Command Reuslts window. Does anybody have any experience/advice?
-
mo
Re: TextPad+Validator3.05+XP
Personal experience: I have found it a lot easier to make corrections in the CSE editor. Call it from TextPad, validate and correct in CSE, return to TextPad. What I say is needed is for TextPad to fully integrate with CSE so that validation and correction can be made within TextPad.
-
Paul White
Re: TextPad+Validator3.05+XP
I can't offer much help as the TextPad / HTML Validator combination has always worked for me and that is with all versions of both programs that I have owned. As the current version of HTML Validator is now at 5.51 I wonder why you are using 3.05 which hasn't been updated since January 1999. That is the full version you are using isn't it? The Lite version cannot be called by other programs - see the HTML Validator web site for details.
-
Ken Grace
Re: TextPad+Validator3.05+XP
What I say is needed is for TextPad to fully integrate with CSE so that validation and correction can be made within TextPad.
That is exactly what happens - or used to happen. It worked under Windows 2000 but since re-installing on a Windows XP machine the integration has failed. Validator is seen in the TextPad tools menu but is greyed out.
That is exactly what happens - or used to happen. It worked under Windows 2000 but since re-installing on a Windows XP machine the integration has failed. Validator is seen in the TextPad tools menu but is greyed out.
-
Ken Grace
Re: TextPad+Validator3.05+XP
Paul - yes it is the full version. I haven't upgraded because the upgrades don't seem to offer any facilities that I would use. 3.05 does exactly what I want - and I have a licence for it.
k
k
-
mo
Re: TextPad+Validator3.05+XP
Ken, we are talking about slightly different things. At least in my setup: W2KPro, TP4.6, CSE5.51. TP and CSE are working together, they are not integrated. I can call CSE from TextPad, that brings up a CSE window with the file I am working on which I can validate and correct in the CSE editor, close that and TP will prompt me to update the file. That's fine.
What I would like to see is for CSE to work within the TextPad window so that I can use TP as the editor and do not need to switch back and forth. (Not a major hassle, just something that would be an improvement).
As to your problem. What I would try is a complete do-over in terms of adding the program to the tools. Remove it, then re-install it.
What I would like to see is for CSE to work within the TextPad window so that I can use TP as the editor and do not need to switch back and forth. (Not a major hassle, just something that would be an improvement).
As to your problem. What I would try is a complete do-over in terms of adding the program to the tools. Remove it, then re-install it.
-
Ken Grace
Re: TextPad+Validator3.05+XP
Mo
The behaviour I am now missing is exactly what you describe as desirable.
A keyboard shortcut in a TextPad window runs Validator and passes the validation output to the Command Results window. Double clicking any of the errors reported in the Command Results window jumps to that position in the file in the TextPad window so you can fix the problem.
It worked fine for me under Win95, then Win2000, but since reinstalling under XP it doesn't.
I've removed and reinstalled both programmes till I'm blue in the face - and that includes manual removal of registry entries and odd files and folders that the removal tools leave behind.
If you are not getting the integration I have described, here is the procedure described to me by TextPad support:
1) Exit from TextPad.
2) Run REGEDIT.EXE using the Run command on the Start menu.
3) Select the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\cse55.exe
4) If the Path data isn't as follows, then modify it to this: C:\Program Files\HTMLValidator55\cmdlineprocessor.exe
Next:
Start TextPad.
From the Configure menu choose:
1. Preferences
2. "+" sign next to Tools
3. Click on Cse55
4. In the Command box type, C:\Program Files\HTMLValidator55\cmdlineprocessor.exe
5. Click Apply / OK.
It was no good to me because I'm not using Validator 5.
I hope it works for you.
k
The behaviour I am now missing is exactly what you describe as desirable.
A keyboard shortcut in a TextPad window runs Validator and passes the validation output to the Command Results window. Double clicking any of the errors reported in the Command Results window jumps to that position in the file in the TextPad window so you can fix the problem.
It worked fine for me under Win95, then Win2000, but since reinstalling under XP it doesn't.
I've removed and reinstalled both programmes till I'm blue in the face - and that includes manual removal of registry entries and odd files and folders that the removal tools leave behind.
If you are not getting the integration I have described, here is the procedure described to me by TextPad support:
1) Exit from TextPad.
2) Run REGEDIT.EXE using the Run command on the Start menu.
3) Select the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\cse55.exe
4) If the Path data isn't as follows, then modify it to this: C:\Program Files\HTMLValidator55\cmdlineprocessor.exe
Next:
Start TextPad.
From the Configure menu choose:
1. Preferences
2. "+" sign next to Tools
3. Click on Cse55
4. In the Command box type, C:\Program Files\HTMLValidator55\cmdlineprocessor.exe
5. Click Apply / OK.
It was no good to me because I'm not using Validator 5.
I hope it works for you.
k
-
mo
Re: TextPad+Validator3.05+XP
Hum...yes I see we are talking about the same thing from different views. I don't call that integration...haha...
I wonder if you have looked in your install directory for CSE to see if you can figure out the name of the equivalent application for your version...you say it was working before it must be there in some form. Then just substitute that name in those instructions.
I wonder if you have looked in your install directory for CSE to see if you can figure out the name of the equivalent application for your version...you say it was working before it must be there in some form. Then just substitute that name in those instructions.
-
Ken Grace
Re: TextPad+Validator3.05+XP
Mo - It's not the same thing!
Your workflow is to validate and edit in Validator, and then when you return to the document in TextPad, to accept that TextPad must reopen the document because you have changed it in another programme. I agree that's not integration.
What I am talking about is when Validator is used as a TextPad tool to validate a document which is open inTextPad and take you directly to any errors within the document, still using TextPad to edit it. You never leave TextPad. The document is only changed in TextPad. Validator navigates you to errors it finds in your open TextPad document.
I call that integration, damned useful, and I wish I could get it back. I probably could by upgrading to Validator 5, but that's a different option.
The manual configuration suggested by tech support involves calling an exec programme which directs output from Validator to the Command Results window in TextPad, and there just doesn't seem to be any equivalent in what I am working with. So I am assuming that somewhere in Validator 3.05 (and earlier versions) there is code to do what has become an external programme in Validator 5, and that this code for some reason will not execute under XP.
I can run Validator from a DOS command within TextPad and invoke transfer of its output to the Command Results window, but as the output file from Validator remains open, there is an access conflict and TextPad can't display it.
I'm just going to have to use a workflow like the one you have.
Thanks for your interest.
k
Your workflow is to validate and edit in Validator, and then when you return to the document in TextPad, to accept that TextPad must reopen the document because you have changed it in another programme. I agree that's not integration.
What I am talking about is when Validator is used as a TextPad tool to validate a document which is open inTextPad and take you directly to any errors within the document, still using TextPad to edit it. You never leave TextPad. The document is only changed in TextPad. Validator navigates you to errors it finds in your open TextPad document.
I call that integration, damned useful, and I wish I could get it back. I probably could by upgrading to Validator 5, but that's a different option.
The manual configuration suggested by tech support involves calling an exec programme which directs output from Validator to the Command Results window in TextPad, and there just doesn't seem to be any equivalent in what I am working with. So I am assuming that somewhere in Validator 3.05 (and earlier versions) there is code to do what has become an external programme in Validator 5, and that this code for some reason will not execute under XP.
I can run Validator from a DOS command within TextPad and invoke transfer of its output to the Command Results window, but as the output file from Validator remains open, there is an access conflict and TextPad can't display it.
I'm just going to have to use a workflow like the one you have.
Thanks for your interest.
k