This naming convention was chosen 5 years ago, and since it has never
caused any problems for my developers we have stuck with it.
A
syan tan wrote:
it is nice to see the svn co http://.../subversion/subversion
still works, and there is a 4.2 branch with some work on web services
and a delphi project offshoot.
One query , about the way the packages are organized ,
the Shared directory contains shared class files but with
the same package name in the various applications for argus.
It's more common to organize into one single package directory,
and have a shared package, and a server package, and a client package,
etc. e.g. something like
org.argusconnect.argus.client, org.argusconnect.argus.shared,
org.argusconnect.argus.server ,
if you look at other open source java projects on the net.
This prevents the problem with naming conflict when server and client
have similiarly named class files in whatever xxxxDomain package.
eclipse can refactor this , but it takes a few goes to get it
right.
On Tue, 2006-12-05 at 16:17 +1100, Ross Davey wrote:
Horst Herb wrote:
All you would have to do is make the open source community happy would be to
make the version control system your programmers must be using anyway
available read-only "live", instead of maintaining two separate source trees
which only generates extra work for you and can't really serve any purpose if
what you say is right.
Availability of most recent source code is all we were asking for, plus not
being locked out from participation in message exchange when not yielding to
compulsory registration - the idiosyncracies of your registration code
enforcement etc could then be made irrelevant by those who feel inclined.
Horst
You are mistaken in this statement.
SINCE AUGUST 7TH, Argus *has* been available as the latest, live version
as open source as announced on this list by Andrew Shrosbree. (see
below) It *is* read-only and *is* on the same source tree as used by
our developers.
(We believe that you may have been looking at the very old Health
Openware Foundation site where Argus source was first published).
We did make a number of announcements on this list about the
availability of Argus source on our Subversion site but had not got HOWF
to modify its site and perhaps link to our site. Since then we have
added the README and licence files that Tim Churches suggested to
explain the licence conditions better.
With regard to your concerns about the registration process, I have
explained the rationale for this on a number of occasions. However we
have started discussions here now about your suggestions for allowing
'forking' of the code, and we will seriously consider that so that those
who object to registration might be able to remove that to create a
'non-ArgusConnect' version.
regards
Ross Davey
Andrew N. Shrosbree wrote:
-------- Original Message --------
Subject: Argus Open Source Code
Date: Mon, 07 Aug 2006 15:12:04 +1000
From: Andrew N. Shrosbree <[EMAIL PROTECTED]>
To: General Practice Computing Group Talk <[email protected]>
CC: Ross Davey <[EMAIL PROTECTED]>, julia Davis
<[EMAIL PROTECTED]>, Jamie Stevens
<[EMAIL PROTECTED]>, Nick Balkin <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
David, et al
ArgusConnect has modified its open source policy.
The current policy allows us to release (current version - 2). This has
proven difficult to control.
Henceforth, the working version of the code will be viewable via a Web
interface, free for developers to download using a CVS client.
We find it easiest to use Borland JBuilder for viewing Java code, and
NetBeans 5 for making WebServices development easy.
Browse access to the ArgusConnect subversion repository is enabled for
anonymous users at this URL
http://www.argusconnect.com.au/subversion/subversion/ (do not leave out the trailing '/' or it will not work.)
What you will see is the source code for the current release of Argus,
version 4.1.3, which is being released today.
Yours, in pursuit of openness.
Andrew
David Guest wrote:
I understand that MO can talk to Argus clients now (I presume that means
is sends a suitably encrypted HL7 message.) and that there was a demo of
Argus sending to MO at HIC 2005 but this is not implemented in the
current release.
Is the Argus source code available? :-)
David
--
Andrew N. Shrosbree B.Sc, B.Ec
Technical Director
ArgusConnect Pty Ltd
http://www.argusconnect.com.au
Suite 4, Greenhill Centre, Mt Helen
Victoria, Australia
Tel: +61 (0)3 5335 2214
Mob: +61 (0)415 645 291
Skype: andrewshroz
_______________________________________________
Gpcg_talk mailing list
[email protected]
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
_______________________________________________
Gpcg_talk mailing list
[email protected]
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
--
Andrew N. Shrosbree B.Sc, B.Ec
Technical Director
ArgusConnect Pty Ltd
http://www.argusconnect.com.au
Mob: +61 (0)415 645 291
Skype: andrewshroz
|
