Stories
Slash Boxes
Comments
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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I think one of the reasons there are so many CRUD systems for Catalyst, and none of them ever feels right, is because the CRUD system is almost an anti-Catalyst concept.

    Catalyst as you say is all about choices, flexibility in application, etc. A CRUD system is (usually) a drop-in single "app" which works with ORM X and HTML templating system Y. So each CRUD system has a different X and Y. I could see CRUD working far better for, say, Jifty.

    I am the author of one such Catalyst CRUD system, and I fully ac

    • I think CatalystX::ListFramework::Builder was the one I haven't tried yet but wanted to. Usually when you start checking these things out, you get discouraged pretty quickly and don't even remember what you tried or didn't try.

      It's definitely the prettiest, and I'm checking the tinyurl.com slides right now. I think I'll try it today. Thank you.

      Usually I write my own CRUD because:

      1. I want it done fast
      2. I want to make some checks in the way

      There's a major problem I think in this area because it's tricky. For example, in CatalystX::ListFramework::Builder, the ExtJS library does the rendering but also the form handling (create, add) so if it was

      [DB] <-> [form handling] <-> [form rendering]

      it has changed to

      [DB] <-> [form handling + rendering]

      and somewhere there you still have to fit the code for the controller methods to have the CRUD functions. If I could make a wish, I would wish on a generic CRUD layers model and thus be able to provide a standard glue for each piece, but the piece move around with the inclusion of AJAX, etc.

      • Yes by all means have a poke and feedback on LFB is welcome - but at the same time I completely understand why you would want to go a different way.

        LFB, as a "first stab" at this type of application, was a good learning experience and highlighted to me much of why CRUD is Hard to do right. But LFB is a mess of design, it's true.

        If you look at the last slide of my LPW talk, I'm basically saying the same as you - what we need is a generic CRUD layer, or really a set of layers which conform to an API. The