My problem with the command line is that the few external commands I want to run in XML CE are programs I'm not all that familiar with. And consequently I don't know how to enter the parameters, but have to look them up.
- Validation via RXP (I like the error messages)
- Use an alternate XSLT engine (per your suggestion)
- Use TortoiseSVN to check files out and commit them to Google Code subversion repository (trying to figure this out now)
Have any ideas on this?
Hm-m. Just thinking aloud here -- can I edit the Help file to add my own info?
Thanks!
Roger
Enormously gratified user of XML CE since early 2007 (have to find out when so I can celebrate my one-year anniversary!)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If an organization using XML CE wanted to supplement the existing help file info, is there any trivial way to get a second help file listed in the Help menu?
Then I could just put my own local info in this second file.
Roger
PS: Yes, I think I can decompile the .chm file, add my info and then recompile. Or locate the source help files (part of the source code?) and start from that point. But I'd like to be able to do this sort of thing trivially.
Actually, of course, I'd like to be able to save the whole command-line and parameters setting for each tool (an approach I've seen in Textpad), but that sounds like a bigger endeavor.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I do need to check why the command window works as expected for many programs but not for all. In general it should always be possible to run programs with the --help flag, select 'Wait' (for synchronous processing) and send the output to a new document tab (which you can split from the main book and drag to the right so it's shown alongside your active document). I realised recently that not everyone is aware that the tabs can be split off from the notebook, which is why I updated the screenshots.
<can I edit the Help file to add my own info?>
Of course, any time! If you'd like write access to the repository, just let me know - alternatively just email me any modified files and I'll commit them and release them with the next version.
<(I like the error messages)>
Yes, I'm aware that the error messages aren't always very helpful right now and that's something I'm hoping to address soon. The first step was rationalising the validation process (DTD & Schema validation is one function from 1.1.0.4, so I only need to work out how to tune one validating parser and make sure I get the best message I can, and hopefully multiple error messages, too).
1.1.0.4 is on its way...
Gerald
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just to pick up on your second message: I think getting the edit boxes with memory sorted for the command, find and replace panels would get us a lot closer to a sensible solution.
I just need to sit down and write a class that handles this.
-g
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK 3rd time lucky: I still didn't address the point of additional help pages: I can't think of an easier way than adding the page and recompiling the chm.
Ideally we'd use examples that would benefit lots of people, perhaps a page of example entries for the command interface -- that would be great for everyone and I'd be more than happy add it to the general distribution.
-Gerald
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My problem with the command line is that the few external commands I want to run in XML CE are programs I'm not all that familiar with. And consequently I don't know how to enter the parameters, but have to look them up.
- Validation via RXP (I like the error messages)
- Use an alternate XSLT engine (per your suggestion)
- Use TortoiseSVN to check files out and commit them to Google Code subversion repository (trying to figure this out now)
Have any ideas on this?
Hm-m. Just thinking aloud here -- can I edit the Help file to add my own info?
Thanks!
Roger
Enormously gratified user of XML CE since early 2007 (have to find out when so I can celebrate my one-year anniversary!)
Just wanted to add:
I see that it's a .chm (compiled html) file.
If an organization using XML CE wanted to supplement the existing help file info, is there any trivial way to get a second help file listed in the Help menu?
Then I could just put my own local info in this second file.
Roger
PS: Yes, I think I can decompile the .chm file, add my info and then recompile. Or locate the source help files (part of the source code?) and start from that point. But I'd like to be able to do this sort of thing trivially.
Actually, of course, I'd like to be able to save the whole command-line and parameters setting for each tool (an approach I've seen in Textpad), but that sounds like a bigger endeavor.
Hi Roger,
I do need to check why the command window works as expected for many programs but not for all. In general it should always be possible to run programs with the --help flag, select 'Wait' (for synchronous processing) and send the output to a new document tab (which you can split from the main book and drag to the right so it's shown alongside your active document). I realised recently that not everyone is aware that the tabs can be split off from the notebook, which is why I updated the screenshots.
<can I edit the Help file to add my own info?>
Of course, any time! If you'd like write access to the repository, just let me know - alternatively just email me any modified files and I'll commit them and release them with the next version.
<(I like the error messages)>
Yes, I'm aware that the error messages aren't always very helpful right now and that's something I'm hoping to address soon. The first step was rationalising the validation process (DTD & Schema validation is one function from 1.1.0.4, so I only need to work out how to tune one validating parser and make sure I get the best message I can, and hopefully multiple error messages, too).
1.1.0.4 is on its way...
Gerald
Just to pick up on your second message: I think getting the edit boxes with memory sorted for the command, find and replace panels would get us a lot closer to a sensible solution.
I just need to sit down and write a class that handles this.
-g
OK 3rd time lucky: I still didn't address the point of additional help pages: I can't think of an easier way than adding the page and recompiling the chm.
Ideally we'd use examples that would benefit lots of people, perhaps a page of example entries for the command interface -- that would be great for everyone and I'd be more than happy add it to the general distribution.
-Gerald