We don't bite newbies here... much | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
1. What users find is wrong with it?
I would suggest sitting with five of your users (in person and one at a time and not all together in a group which is bad) as they use it and take notes on what they don't know how to do. See what they find intuitive and find obfuscated. See www.useit.com for more info on user interface issues. 2. What features are missing from it? Same as above though you really want to do this at the outset when you write up requirements for the project. 3. How to make it faster and other load issues? That depends...is it slow? If it is then find your bottleneck. Is it the server hardware? The server OS? The client's hardware? The client's OS? The client's browser? The network? The algorithm used to implement function x in your CGI script? Consider timing the various parts of your code to find the bottlenecks and focus on those parts. As you can see on this site there are many monks who point out faster and simpler alternatives to various perl hacks. metadoktor "The doktor is in." In reply to Re: How do I test a CGI program properly?
by metadoktor
|
|