In order to use server side perl scripts, you need to have the form submitted. This can be automated with JavaScript, but....
The question is whether you really want to do this. Web developers tend to stay away from JavaScript for a number of reasons.
- different browsers differ greatly in expected Jscript objects. This means that most likely, you will never have a fully cross-Jscript-capable interface. While EczemaScript has been a worthy attempt in perhaps the right direction, but even the world's most popular browser is skimpy on compatibility.
- Many browsers do not support JavaScript or many users prefer to have it off- even if it's just to avoid annoying pop-up ads. I am one of this breed. I doubt that I'm alone.
- JavaScript tends to be...well- annoying. One sees it alot sliding buttons or switching colors. This is all fine and well in the land of non-JScript-capable browsers, just as long the links are not of the JScript clicking variety. This is functionality which I believe is the correct domain of JScript- non-crucial tasks only. If I switch off JScript, I still can navigate the site perfectly fine.
Of course, you may argue that you're web app is used only in a limited pool of computers all of which support X, Y, and Z and will work great with whatever you cough up. That's nice, but as soon as the company Dilbert sees that he could work at home and he can't use your app because of JavaScript errors. OR the company wishes to move or sell or copy the app to a different circle of users, all of which have NO Jscript or use a different browser. Bad news and one that is actually easily avoidable...just use a recent version of HTML.
If you find that you your web application would be better represented using objects or states, then look into jellybean or CGI::Application, not to mention everything2 and a slur of proprietary web object servers.
If you're looking for TRUE interactivity, you're not looking for web-based apps. In that case, you'd be looking at actual GUI implementations which your customer may benefit from. Try Tk for a cross-platform solution. Web searches on any of these topics will get you off to a strong start. Good luck!
AgentM Systems nor Nasca Enterprises nor
Bone::Easy nor Macperl is responsible for the
comments made by
AgentM. Remember, you can build any logical system with NOR.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
