Slash Boxes
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Check out Joose [] too.

    It's unlike the three in your post in that it's purely an object system for JavaScript, and an incredibly flexible one at that. It can work in conjunction with the interface tools provided by jQuery, YUI, etc., and I've found it quite helpful for maintaining any serious kind of state or logic client-side.
  • Have you tried MooTools [] ? I've seen some pretty nifty GUIs developed on it, and it seems pretty compact.

    For a more professional solution (wo/ nasty Flash-ness), you might look into TIBCO GI [], tho it has some of the same bloatware issues as ExtJS

    I agree Dojo's docs to date have been appallingly bad...but now there are several print books on it (I haven't read any yet, but its on my TO DO list).

    And I also agree YUI is probably the most accessible of all, probably because the website has really nice examp

    • No response from the MooTools link.

      Exit MooTools.

      ThinWire: I abstain from Java, and am only looking for Javascript stuff. Now, in the ThinWire FAQ I see
      'Thinwire is not designed to use custom JavaScript code elsewhere'. Oh. (By 'elsewhere' I assume they mean 'anywhere').

      Exit ThinWire.

      Now: QooXDoo.

      Yes, this is more suited to my way of thinking, and a demo like this (go in, I'm afraid, via Documentation/Getting started/Snippets/Demo browser): []

  • I don't like method chaining either, but you can program jQuery without it. It's so much easier to use than YUI. I think you should give it a chance.

    • The phraseology I used implied it was just the chaining that I don't like (true) but the other thing which put me off was the sheer quantity of code (in the demos, admittedly) to achieve results.

      It reminded me of assembler (shudder) and Tk (mega-shudder). A lot of code for a small effect.

      I, like you, and like everyone, either are forced to use a particular package in a specific situation, or choose something we like. And this I don't like.

      OK. I've had another looks at jQuery's docs, specifically the Tab int

  • I was really happy with Rico (, which is built on prototype. However, I really only had a single application - which was a dynamic AJAX table with sorting and filtering. There is not much of a perl API. I did end up reimplementing it (just a quick database connection).
    • The home page of OpenRico responds, but clicking on Demo gets no response.

      And from their archives, it looks like development stopped in Jan 2008 :-(.

      Exit OpenRico.

  • I've been using jQuery and love it. I find coding with it clear is simple, there are plenty of plugins and great docs online.

    It's also been easy to write our own jQuery plugins.

    Sometimes I use method chaining with it, but often I don't. I have found it useful at times and appreciate the feature.