Hi there,
I am interested in participating in the project.
But first, I have to get CVS working on my
machine...
I read the mailing-list archives, and someone
wrote about keeping the logic and the GUI
separate. That kind of answered my question:
"Have you thaught of a web GUI?"
If so, how do you want to implement it?
Also, I think I've seen you want to use the
Bekerley DB. I don't know much of it. The only
one I used is MySQL and I'm getting pretty
familiar with it.
What would you think of a file-driven database
interface? It could be XML files, each file
representing a table, or maybe integrating all
the tables into one file. That would make the
application more easily transferable. But we
should consider performance issues.
It would be great to have a pedigree-browsing,
integrated in the application, allowing fast
feedback on the data. Maybe it could simply be a
dynamic report. The reports could be used in two
ways: In the application, and to produce a file
(postscript).
To go that way, we sould separate the logic of
the report, from the process outputting it. The
logic's output (XML?) could contain "hyperlinks"
that would be used by the application to popup
person info, or event info. The file-generator of
the reports could then ignore them when generating
postscript. PDF documents support hyperlinks.
Static-HTML creation could also use those
hyperlinks.
Resumed:
1- Selecting the data that should appear in the
report
2- Generating XML containg the data
3- Apply a XSL report stylesheet that would
take the data and format it in Postscript or HTML
or whatever format, and the application could use
the XSL stylesheet to display the report directly
on screen, integrated withing the application
environment, with "hyperlinks".
If you are not familiar with XML and XSL, let me
know. Basically it allows to separate the content
from the layout or presentation. The content is
trored in the XML, while the template resides in
the XSL file.
These are standards and using them could allow
more flexibility if we want to use more than just
C or C++. Also, with XSL, there is no need of a
custom report scripting language.
Getting back to the web GUI, I see to ways of
doing it:
1- Rewrite all the logic in PHP or Perl and use
the same database
2- Let PHP or Perl use compiled C programs to
access the data trough that program's interface.
(hum, there are multiple ways to do that too)
An other possibility is to use a Java applet that
could directly communicates with the server. It
could then use C++ code to listen on a specific
port and access all the funcions of the
application.
Let me know what you think of all this!
--
Nicolas Marchildon
[EMAIL PROTECTED]
http://www.mlink.net/~enix/
_______________________________________________
Genes-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/genes-devel
