NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
--Larry Wall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
I'll have to agree with Elian (Score:2)
All the interfaces I have built in the last 4 years or so use HTML or the command line (or both).
Is there going to be an XML section in the cookbook?
mirod
Re:I'll have to agree with Elian (Score:2)
While it is the case that many programmers want to use a browser for an interface, there are considerable difficulties with this approach. First, you have to create a state maintenance mechanism. Second, it's tough to duplicate true application behavior with a Web-based GUI.
Right now, I'm building a "temporary" CGI application that will be replaced with a desktop app when we have time. Originally, the designers had it create a lot of pop-ups for searching. However, the pop-ups can't be used as a modal
Re:I'll have to agree with Elian (Score:2)
Well, as most of the code I write is of the type "set parameters right, shoot, wait for results, go home" I don't have that kind of problem. Plain vanilla HTML is more than enough for me (for example, I just used multi-valued checkboxes for the first time 1 hour ago).
I agree that HTML does not give you nearly as much power as a regular GUI. It's just that you don't necessarily need the full power. The added bonus is also that with a web-based interface, users expect the application to be slow (they are rarely disapointed ;--) so you can take your sweet time in the back-end and forget about all those painful optimizations to get a good response time.
mirod
Reply to This
Parent