Todos in the pipline / wishlist
General
- cleaner code to avoid namespace pollution
- create Perl version which is auto-translated to JS-version
- auto create documentation of syntax
- test suite also checking browsers
- move to git-hub
- allow individual customizing of allowed features and used markup
- allow caching of imported JS to spare band width
- general JS-Extension framework to encourage more contributions, see also older discussion
More Features
- DONE auto link URLs starting with http://
- DONE parse for internal url's and create [id://...] links (thus avoiding logouts)
- map doc-links of operators to correct perldoc, like ?and? to [doc://perlop|and]
- support for abbreviation list, i.e. auto linking autolinking SOPW or CPAN with mouseover (' title' -attribute) description
- better support for quotes from commented post
- onchange preview with JS of resulting post
- looks-like-code() heuristic to warn about perlcode outside code-blocks
- move [ ]wiki? checkbox under textarea, show only if any submit button available
- include timestamp after updates
- DONE support for deeplinks in perldocs (jump to right chapter)
- better support for cut&paste from perldoc (web or console)
... to be continued...
Requested
- Wiki support for CB
- look behind assertion in around_words
- treat punctuation like whitespace
-
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.
|