Ocean Archetype Editor source code?

Technical (archive)
1

Hi,
My attempts to check out Ocean’s archetype editor fail with a request for a username/password for svn.oceaninformatics.com
I can omit externals in my svn client (should I?), however when I do that only beryllium directory in releases contains a project I can compile and run. Others, including the one in the trunk do not compile due to a missing project or an undefined type.
I’m a little bit lost here, can someone help me out to get the up to date source for the current ArchetypeEditor exe?

Kind regards
Seref

2

Seref Arikan wrote:

My attempts to check out Ocean's archetype editor fail with a request
for a username/password for svn.oceaninformatics.com
<http://svn.oceaninformatics.com>
I can omit externals in my svn client (should I?), however when I do
that only beryllium directory in releases contains a project I can
compile and run. Others, including the one in the trunk do not compile
due to a missing project or an undefined type.
I'm a little bit lost here, can someone help me out to get the up to
date source for the current ArchetypeEditor exe?

Hi Seref,

The TRUNK is the current source:

http://www.openehr.org/svn/knowledge_tools_dotnet/TRUNK/ArchetypeEditor

Don't omit svn externals. The TRUNK has two externals, one of which you
need and the other you don't need:

AdlParser -r65
http://www.openehr.org/svn/oe_distrib/windows/adl_parser/dotnet
Archetypes
https://svn.oceaninformatics.com/svn/EHR/RELEASES/BlueChina/knowledge/deploy/archetypes

"AdlParser" is the .NET ADL Parser. You need it.

"Archetypes" is just a standard set of archetypes, which we install with
Archetype Editor so that users have some archetypes to play with. This
is on our Ocean server, as you discovered, but just disregard the
failure to check it out. You can build ArchetypeEditor.exe without it.

- Peter

3

I should have given it a try instead of erasing the directory. I’ll give it another try with my ultra fast 3g mobile connection, I hope my laptop can handle 4kbs per second…
Thanks for your response Peter

Cheers