Out of curiosity, I downloaded and tried PerlEdit 1.00 for Linux. The tarball was downloaded quickly, and it extracted without any problem (well, it put some files in my current working directory, but I can live with that).

Editing files is very intuitive, and it was nice to find a Windows-ish Open...-dialog in Linux. I dislike MDIs, but have to admit that for editing source files, it can be quite useful. The debugger didn't work, as it looks for DB::DB, which I don't have. It would have been nice if the error messages involved were displayed somehow - I had to find out by starting the program from an xterm.

As a Perl editor, PerlEdit didn't please me at all. A big deal is made out of its syntax highlighting, but it was very simplistic. Recognized keywords were rendered in blue, and some operators (I found ge and gt) are rendered bold. I'd expect a syntax highlighting program to at least color comments differently. And some quote-operator recognition is better than none at all. Only perl can parse Perl, but this isn't anywhere near parsing. It's rudimentary matching. Maybe Syntax::Highlight::Perl can help.

The block indent seems to work fine, but I couldn't find a way to unindent. The editor uses a proportional font, which is a bad thing. Code should always be rendered monospaced. I like having line numbers in graphical editors, but PerlEdit only offers the statusbar line/col indication.

The syntax checking idea is great, so I removed an opening curly and had PerlEdit check my syntax. This is a wonderful feature, and one of the few PerlEdit features that actually work the way I expect.

I screwed up a perl script to test this marvellous error message system some more, and it showed my errs as before. I closed the file without saving (or so I thought), and wondered why it didn't ask for confirmation. It saved my file somewhen, but I didn't want it to, as the script was (intentionally) in a very bad shape. I spent five minutes cleaning up the mess I had created, and getting the program to run again.

I like the visualization of syntax errors, but this editor is not usable for real work. If I had to guess the version number, I'd have guessed 0.04, not 1.00. Does this program really cost $99? I find it hard to imagine that anyone would pay such an amount of money for a mostly dysfunctional program while there are better editors out there that are free. I'll stick to vim for now.

I put a screenshot online at http://tnx.nl/perledit.png. 

- Yes, I reinvent wheels.
- Spam: Visit eurotraQ.

In reply to PerlEdit V1.00 reviewed by Juerd
in thread PerlEdit release V1.00 is now available by talexb

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.