Dear All,

I have build a complete publishing system for OpenEHR.

It ends up in part with a bunch of href's in an HTML page e.g. if it 
finds errors then it creates a link to the file in the relevant working 
copy.

2 points:

A) Wrt .adl I can set the filetype etc in windows & when I clik on a 
link to an adl, the archetype editor opens with that file.

Hurray.

However......If I click on a .oet even if I set the template designer to 
be the default file handler I just get a Dr Watson with

EventType : clr20r3     P1 : templatedesigner.exe     P2 : 1.0.1244.410    
P3 : 47608b1a     P4 : mscorlib     P5 : 2.0.0.0     P6 : 4333ab80     
P7 : 26bb
P8 : 38     P9 : system.argumentexception   


Can the template designer open a .oet if passed by a browser or clicked 
with a mouse having set the file association?

It would be nice if it could as for instance wrt errors, this allows the 
user to simply click on the file link, the relevant editor opens, the 
fix can be made & the file saved.


B) Obviously.... .xml is a commonly used extension......as such is there 
any plan to swap to say .xadl before too many peopel start building 
round .xml files? e.g. right now it will be easy for me to re-adjust 
form .xml to .xadl.


Adam





**********************************************************************
This message  may  contain  confidential  and  privileged information.
If you are not  the intended  recipient please  accept our  apologies.
Please do not disclose, copy or distribute  information in this e-mail
or take any  action in reliance on its  contents: to do so is strictly
prohibited and may be unlawful. Please inform us that this message has
gone  astray  before  deleting it.  Thank  you for  your co-operation.

NHSmail is used daily by over 100,000 staff in the NHS. Over a million
messages  are sent every day by the system.  To find  out why more and
more NHS personnel are  switching to  this NHS  Connecting  for Health
system please visit www.connectingforhealth.nhs.uk/nhsmail
**********************************************************************


Reply via email to