Subissue status

View: New views
3 Messages — Rating Filter:   Alert me  

Subissue status

by Graham Reeds :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I spoke with Peter Davis (the founder of the project) on 05/10/05 and he
explained that he started the project with good intentions but he is
doing an undergraduate degree "So it's really a matter of too little
time, what with homework and all.".  He goes on to say "Not much code
was ever written, so for the near/medium term I don't expect the project
to go anywhere.  I do hope to pick it up again in the future."

I will be willing to lend a hand (UK, so GMT+0).

For the web-based viewing system mentioned in the project outline I
think the back end should produce an XSLT/XML script which can either be
parsed by a client tool or rendered by a browser.  I am a "dab-hand" at
HTML, CSS, etc but primarily a Java/C++ person though I could probably
learn the rudiments of PHP fairly quickly if need be.

Graham Reeds


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


Parent Message unknown RE: Subissue status

by Wherry, Matt :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

XSLT/XML for me is a good call.

I think this might also help with the reporting capability, as well
helping support multiple frontends.

Thought about Python for the web frontend? - It's very nice....

M

-----Original Message-----
From: Graham Reeds [mailto:grahamr@...]
Sent: 10 May 2006 11:16
To: dev@...
Subject: [subissue] Subissue status


I spoke with Peter Davis (the founder of the project) on 05/10/05 and he

explained that he started the project with good intentions but he is
doing an undergraduate degree "So it's really a matter of too little
time, what with homework and all.".  He goes on to say "Not much code
was ever written, so for the near/medium term I don't expect the project

to go anywhere.  I do hope to pick it up again in the future."

I will be willing to lend a hand (UK, so GMT+0).

For the web-based viewing system mentioned in the project outline I
think the back end should produce an XSLT/XML script which can either be

parsed by a client tool or rendered by a browser.  I am a "dab-hand" at
HTML, CSS, etc but primarily a Java/C++ person though I could probably
learn the rudiments of PHP fairly quickly if need be.

Graham Reeds


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...
 
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
 
Danish - Deutsch - English - Espanol - Francais - Italiano - Japanese - Nederlands - Norsk - Portuguese - Svenska:
www.cardinalhealth.com/legal/email

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


Re: Subissue web-interface [Was: Subissue status]

by Graham Reeds :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

> XSLT/XML for me is a good call.
>
> I think this might also help with the reporting capability, as well
> helping support multiple frontends.
>
> Thought about Python for the web frontend? - It's very nice....

No. Time is limited by work and girlfriend so I keep to C++ and Java. I
know you can use C++ and Java via CGI but that is less than standard
(maybe not?). My friend has been badgering me to learn PHP, which is
class based and has ports of struts etc., so that looks like where I
will aim for. Also when I get stuck I will have 24/7 support in it.

Whatever is chosen I think the XML output and have the client use XSLT
to translate it is the right choice in this case. Also the cleanliness
demonstrated by Insurrection gives a good indication of what can be done.

I haven't checked the source but I think Insurrection project (hosted
here at http://insurrection.tigris.org/) could be used as a good
starting point for the web interface. However the code is Perl, which I
have never actually touched so the learning curve (I imagine) will be steep.

If anyone has any ideas of why we should reinvent the wheel and not use
the Insurrection source as a start I would like to hear it.

G.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...