[oXygen-user] "Job well done!" messages

[George Cristian Bina]

Hi Wendell,

There is no possibility to show a message when the validation ends. 
However, there are a few possibilities.

We have an Information view that shows also messages for successful 
validation. You can enable that from Window->Show View->Information.

The Schematron implementation from oXygen is available in 
[oXygen]/frameworks/schematron/impl. I believe you can change that to 
automatically trigger an info level message when the validation is 
successful. Then you should put all the files in a builtin folder and 
pack everything as a jar or a zip and put that inside 
oXygen/lib/endorsed (you need to create the endorsed folder). In this 
way you will overwrite the default Schematron implementation from oXygen.

Do any of these help?

Best Regards,
George
-- 
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 1/6/11 6:02 PM, Wendell Piez wrote:
> Hi,
>
> Of course, the usual thing with XML processors when validating has been
> to give error messages for syntax or validation errors, but to be coyly
> silent when no errors are found. The user is left to infer that
> everything is good based on the fact that there are no complaints.
>
> oXygen improves this state of affairs by having a little box that lights
> up green when a document is valid, plus a line that says (with admirable
> clarity) "Document is valid".
>
> However, some users wish for more. They'd like a trumpet fanfare or
> something analogous. (Wouldn't we all?)
>
> In particular, I have some users who have asked if they can have their
> Schematron tell them when there are no errors. I have explained that
> they will probably have to be content with the green light, and I don't
> think this is too much to ask of them. But I am also wondering whether
> oXygen might have hooks somewhere that could be used to pop up an alert
> box or something, with a congratulatory message of some kind.
>
> (This is a case, of course, when having an explicit Schematron report
> test when "not($a or $b or $c)" won't work, since the number of tests is
> in the double or triple digits.)
>
> What are the ramifications here and what would it take for these users
> to get what they want? If this were all done inside a processing
> pipeline I could Schematron the results of my Schematron to run the
> test; but it's not; nor do they want it to be since of course they like
> the fact that their error messages have live links back to the documents.
>
> I am imagining some kind of facility that could be associated, for
> example, with a validation scenario.
>
> Cheers,
> Wendell
>
> ======================================================================
> Wendell Piez                            mailto:
> Mulberry Technologies, Inc.                http://www.mulberrytech.com
> 17 West Jefferson Street                    Direct Phone: 301/315-9635
> Suite 207                                          Phone: 301/315-9631
> Rockville, MD  20850                                 Fax: 301/315-8285
> ----------------------------------------------------------------------
>     Mulberry Technologies: A Consultancy Specializing in SGML and XML
> ======================================================================
> _______________________________________________
> oXygen-user mailing list
> 
> http://www.oxygenxml.com/mailman/listinfo/oxygen-user
>