Re: GUI for Test suite

The answer to "I have no idea what it should contain and how it should look" is simple: just read the program specification. Wot? Not got one? Then maybe you should sit down with your users/sponsors and write one first. Methinks someone decided on the solution before understanding the problem.

If you have never written a GUI then you might consider a web-based approach instead - in other words let the browser be your GUI and use HTML. Since you are running on Linux then you probably already have all the components, like Apache, installed. This also has the advantange of allowing the users to access the interface remotely.

Comment on Re: GUI for Test suite

Replies are listed 'Best First'.
Re^2: GUI for Test suite by dpatel (Novice) on Apr 19, 2010 at 08:25 UTC
oh... your idea seems to be promising in case of server client model. so in case if i use html, I will also have to use CGI, don't I? and Yes I have program specification. I need to give users 2-3 options, and he will choose and accordingly my program will choose the scripts to run. I have created a demo using perl-tk and in which i have used button . user will press the button and program will run specific perl scripts. i have used perl-tk in it. So can you elaborate how HTML could be more useful or better?	[reply]

Replies are listed 'Best First'.

Re^2: GUI for Test suite
by dpatel (Novice) on Apr 19, 2010 at 08:25 UTC

oh... your idea seems to be promising in case of server client model. so in case if i use html, I will also have to use CGI, don't I? and Yes I have program specification. I need to give users 2-3 options, and he will choose and accordingly my program will choose the scripts to run. I have created a demo using perl-tk and in which i have used button . user will press the button and program will run specific perl scripts. i have used perl-tk in it. So can you elaborate how HTML could be more useful or better?

[reply]