+3
hugh
Hi Koray,
If you imagine some sort of workbench or platform that can be used to create openEHR-based applications, wouldn’t it be nice if the workbench would offer the creator/developer some sort of help along the way? Not with tooltips saying something like “See the reference documentation” but more like tooltips containing snippets of the reference documentation, e.g. “Insert here an object of type DV_TEXT: ”. If you envisage this workbench or platform in a web-centric setting, it’s not too hard to see that a translation service (Yahoo’s or Google’s) could machine-translate those snippets. Of course it should be very clear that the originally published (English) specification on openEHR.org is authorative.
I think the OP was pointing into this direction, and not a multi-million resource-intensive translation process.
From-the-pitfalls-yours,
Roger
Hi Roger,
I’d really like the kind of functionality you describe and it is definitely desirable…I was little concerned about the workload implications to already supersaturated core members. And I must say worried about the wording in subject of the thread - the content and quality of openEHR documents look pretty satisfactory to me at the moment. Sorry if my message has been little “reactive” - but I can not help but become emotional when it comes to openEHR 
BTW I’d be very interested to know if anyone prefers to use a “text editor” when creating/updating archetypes? It’d be very cool to have an “ADL” aware editor and have kind of “intellisense” functionality for writing ADL expressions for advanced users.
Cheers,
-koray
Roger Erens wrote:
Hi Koray,
Autocomplete for a syntax colored ADL editor is one of the features planned for Opereffa Eclipse plugins, FYI.
All the best
Seref