Ability to pass urls to be validated through cmdline

[TomasF]

I posted this in the old forum and mailed you about it, but since you're asking for input even if it's been mentioned before, and because it's *really* important to me, I'll bring it up here too. Would be great if others who have thoughts on this would voice in, brainstorming usually brings instant improvement

I'm customizing my Opera right-click menu to better suit my web development tasks, and have already added an option for "Open with Topstyle" where Topstyle Pro will open not just the cached file in Operas cache, but actually go out and retrieve the url from the web, and thus automagically open the linked css files, just as it would if you used the "open from the web" dialog. I do this by passing the url as a plain parameter to the topstyle.exe file.

What I would like is to be able to send a url to cse though a commandline parameter so it either validates directly or just opens in the CSE editor, preferrably select between the two though a switch.

[Albert Wiersch]

I'm customizing my Opera right-click menu to better suit my web development tasks, and have already added an option for "Open with Topstyle" where Topstyle Pro will open not just the cached file in Operas cache, but actually go out and retrieve the url from the web, and thus automagically open the linked css files, just as it would if you used the "open from the web" dialog. I do this by passing the url as a plain parameter to the topstyle.exe file.

What I would like is to be able to send a url to cse though a commandline parameter so it either validates directly or just opens in the CSE editor, preferrably select between the two though a switch.

Hello,

Thanks for posting your suggestion on the new forum. I do have this on my to-do list at a high priority so it is definitely one of the things I want to get done for v7.0, though I haven't gotten to it yet.

Currently I'm working on import/export options so that the validator engine options can be easily saved and distributed using the exported files. This would also be good for people checking different pages or projects that have different validation requirements.

You can somewhat monitor the progress of new features by visiting this page:
http://www.htmlvalidator.com/htmlval/be ... ryv70.html

I typically add the new features to that page when the feature has been added successfully. I thought you might want to know.

[TomasF]

Woo, I love the progress list, I'll be keeping my eye on that for sure (that's a threat ).

A few comments after skimming through it:

* XML lists and config export/import - excellent
* NTLM auth - Love it!

Some new suggestions:
* Any chance of adding an option for using Mozilla as the built in preview? (I'll admit I very rarely use this feature as well as the editing part, but considering the state of IE this might comfort some users)
* Not sure if this is somehow possible already, but if it isn't, a commandline switch to export validation results to a xml file (like the "save messages to clipboard as xml" feature in the editor)

[Albert Wiersch]

Woo, I love the progress list, I'll be keeping my eye on that for sure (that's a threat ).

A few comments after skimming through it:

* XML lists and config export/import - excellent
* NTLM auth - Love it!

Some new suggestions:
* Any chance of adding an option for using Mozilla as the built in preview? (I'll admit I very rarely use this feature as well as the editing part, but considering the state of IE this might comfort some users)
* Not sure if this is somehow possible already, but if it isn't, a commandline switch to export validation results to a xml file (like the "save messages to clipboard as xml" feature in the editor)

Great! Glad you like the progress list and some of the new features.

I may consider adding a Mozilla/Firefox browser in the future but it's currently not on my to-do list. Very few people have made any mention of wanting this, but it's always a possibility down the line. Most people still use IE. Personally, I use to use Mozilla, but now use Firefox. I'm currently fine with IE in CSE for my own use.

There is an "XML Output" option in the Classic Tab of the Validator Engine Options. Would this work or do you want a switch when using cmdlineprocessor.exe? If so, I can add that to my to-do list (but no guarantees on anything in my to-do list! )

[TomasF]

There is an "XML Output" option in the Classic Tab of the Validator Engine Options. Would this work or do you want a switch when using cmdlineprocessor.exe? If so, I can add that to my to-do list (but no guarantees on anything in my to-do list! )

I was thinking of using this in conjunction with my original proposal, as an alternative to opening it in the editor. Thus as a switch to cmdlineprocessor would make sense, so that if I'm browsing through some pages, I could just right click and choose a homemade menu item like "validate to xml", and I'd have the xml files stored in the background without interrupting my browsing. Then I could review the xml files later, using some xmldiff app, or adapt my own xml log reader in Coldfusion to handle these.

[Albert Wiersch]

I was thinking of using this in conjunction with my original proposal, as an alternative to opening it in the editor. Thus as a switch to cmdlineprocessor would make sense, so that if I'm browsing through some pages, I could just right click and choose a homemade menu item like "validate to xml", and I'd have the xml files stored in the background without interrupting my browsing. Then I could review the xml files later, using some xmldiff app, or adapt my own xml log reader in Coldfusion to handle these.

OK, I've added that to my to-do list. As usual, no guarantees that I will be able to get to it (but it's on my list).

[Albert Wiersch]

I've added a "-xi" option to cmdlineprocessor.exe so that you can now override the XML file generation default setting. -x0 will disable XML result file generation and -x1 will enable it. This will be available in the first v8.00 BETA.

[TomasF]

Wheee! That's great. I tend to customize and automate as much I can of "routine" and frequent actions (I guess validation qualifies as such), so the more stuff that can be scripted/launched through cmd from other apps, etc, the better.

Looking forward to the first beta of v8