- One of the reasons why you do not find anything about PerlScript used in the browser is ... that people do not do that often enough. You simply can't do this in any other case than if all your users are running Windows and have Perl installed. Maybe some intranets are elligible, I don't really know. I might do something like this soonish in a HTA, but for web client-side stuff JavaScript has to be good enough.
- The second reason is IMHO that there is not much to document. Perl is Perl and browser object model is browser object model. Sure Netscape and MS has all their docs in J(ava)Script, but converting that to Perl syntax is not that a big deal. If you want to control a program using OLE/COM you usualy need to convert the description and examples from VB and thats a bigger difference.
Jenda
Always code as if the guy who ends up maintaining your code
will be a violent psychopath who knows where you live.
-- Rick Osborne
Edit by castaway: Closed small tag in signature
-
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.
|
