[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (FC-Devel) RE: Language choice
I think your mention of the Argo tools hit the nail on the head. In
my opinion, I think the Argo Tool is a fantastic starting point. It
would be a shame to have to re-implement - and re-implement it in
I register my vote for C++ in the backend and Java in the front. I
even dare to say, develop the whole lot in Java. It would aid
portability (Linux/win32), could promote reuse between the backend and
frontend. Downside is that it may be too slow. :-(
Just my two cents.
> Hi Andrezej,
> > 4. And the question C++ or Java is valid only for graphical interface
> > and strictly speaking it is not clear whether it makes sense now. What
> > has to be done in the nearest future is some king of prototyping. An
> > interpreter with interpreting environment, debugging environment is the
> > easiest solution. That language should support graphics environment as
> > well. In my opinion a reasonable solution might also be tcl/tk since it
> > has an interface to postgress as well. As soon as something working has
> > been got it can be transfered to C++, Java or whatever. Perhaps my last
> > opinion is because of my experience (I do not have a lot of experience
> > with C++, and almost none with Java).
> Hmm, well we will have to decide which language to use for all
> components of the system, not just the interface. I would
> personally be happiest with C or C++ for the repository server side
> of things, and Java as the client, but hey, whatever. I have to say
> that tcl/tk is certainly not one of my favourite languages, actually
> the complete opposite, but I could live with it if people wanted to
> use it. There is the matter of the Argo tool though (written in Java),
> which would be a bit of a boon if we could utilise it.
> Duane Griffin.
> Duane Griffin
> Paradigm Technology Limited
> Phone +64-4-495-1010
> Facsimile +64-4-499-7762
> Level 13, Paxus House.
> 79 Boulcott Street, Wellington.
> NEW ZEALAND