I created a (quick/dirty) simple syntax-highlighting definition file for
the editor Kate, which is part of the KDE environment, it is also loaded
in KDevelop.
It recognizes blocks/regions (<>), and datatypes (strings, numeric
types)
For me it is useful, so if you want it, I hope attachments arrive on the
mailinglist.
Just put it somewhere on your computer (best is in cache directory
(below) where all the other syntax files are) and add the lines
I wonder whether it is worth using the same convention we used in the
specifications?
*
* *keywords like cardinality, existence = blue*
* *class and attribute names = dark green*
* *[at-codes] = magenta*
* *comments = brown*
* *leaf values = red (as you have)*
this is not necessarily any better than the convention you chose, but
it may help people if the editor highlighting matches the specs..
It is a good, idea Thomas, I will do that, if possible. But first I have
to find out how, it is badly documented.
For now I leave it as they are. I am thinking of doing also one for
Eclipse (if it does not cot too much time).
It is a good, idea Thomas, I will do that, if possible. But first I have
to find out how, it is badly documented.
For now I leave it as they are. I am thinking of doing also one for
Eclipse (if it does not cot too much time).
Me too. the problem is that there are more coloring plugins. Eclipse
from itself only supports coloring over the preferences menu in the
Editor properties.
It is also possible to leave the coloring plugins, and inherited a new
editor from Text Editor. There are already some 60 examples on the
Eclipse plug site. So, that wouldn't be too hard. And the advantage is
also that it is in more ways extensible, for the feature.
A step forwards for a the openEHR-software-ECO-system.
For example could it be possible to use the code from the
Java-archetype-editor in a plugin, and thus create an eclipse-OpenEHR
set.
The problem is only now that I am directly working towards openEhr
implementations, which cost all of my time. This will go on for the next
few months.
After that I will be happy to work on that. These are nice and small and
usefull projects, and great to show one's face. A project like this can
become very popular in the openEHR-community.
So if no-one takes the change, I take my change to shine on this in a
few months.
You will notice that the ADL colouring has been achieved.
Richard Kavanagh
Head of Interoperability Specifications
Data Standards and Products
NHS Connecting for Health
Richard.Kavanagh@nhs.net
www.connectingforhealth.nhs.uk
NHS Connecting for Health supports the NHS in providing better, safer care
by delivering computer systems and services which improve the way patient
information is stored and accessed.
Your openEHR tooling in Eclipse looks very interesting. It would be
great to make it available to the community so it can be further
explored and extended. Is there a plan to open source the software,
perhaps through OHT?
I guess the answer is "NO"? Or still considering?
Too bad if it will not be published.
Maybe after a few months, I have more time, I do it myself.
It shouldn't be to hard. There are many editors inherited from the Eclipse Text-editor, to take as an example.
The limitations in us making the tool available to the community is hampered
by IPR issues, not our desire to make it open source. We will explore
options and hopefully get it available soon.
regards
Richard Kavanagh
Head of Interoperability Specifications
Data Standards and Products
NHS Connecting for Health
Tel : +44 (0)113 397 4398
Mob : +44 (0)7770 644449
Richard.Kavanagh@nhs.net
www.connectingforhealth.nhs.uk
NHS Connecting for Health supports the NHS in providing better, safer care
by delivering computer systems and services which improve the way patient
information is stored and accessed.
I wonder, could this be usable to build an Eclipse ADL/DADL-editor with
al the useful things like outline, syntax-check, syntax-coloring,
validation, etc....