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.
  • As an author of yet another CRUD framework I am interested in stealing your ideas and code.
    • Not really. I still use what I wrote but haven't released it. I think it needs some work before I could. You're more than welcome to check the source, work with it, play with it and help to release it, obviously.

      However, I have an idea that I wanted to propose and this might be a good place (or not). I want to create a layers model for a CRUD system. That would include scaffolding, form processing, etc. That way, we'll be able to use modules interchangeably and everything will work because they will conve

      • :) - sure. You can have a look at my Catalyst::Example::InstantCRUD module. It is a scaffolding. It does the CRUD part - and it works but I wanted to offload it to something more flexible and possibly RESTful (perhaps using Catalyst::Controller::REST and Catalyst::Request::REST::ForBrowsers).

        My form processing is currently done by Rose::HTMLx::DBIC - another of my modules, but I am not too much attached to Rose (it is a fine module - but I would rather have one object model - and since everyone goes wi

        • I'm all very for the "I don't want to do it like that!" attitude. It's a sum of years of experience and I think it could leverage us and make sure we do things better and not fall over the same things again.

          With regards to your concerns: we don't have to use HTML::FormHandler specifically. The idea is that we figure out a protocol (or, something of that sort) for CRUD and CRUD implementations which will make it possible for users to use either HTML::FormHandler or Rose:HTMLx::DBIC or anything else they want

          • by zby (4817) on 2009.03.02 16:26 (#67669) Homepage
            OK - great! I am all for constructing interfaces between all the layers. There is just one thing - see CatalystX::CRUD - it is designed with the idea of interchangeable database layer - and I think the result is too complex. The reason for that is that the DBIC model is the schema - that is the whole database - while in RDBO the model is one table (at least in CatalystX::CRUD::Model::RDBO). In my opinion this creates too much friction between those two to hide it behind one interface. And by the way I don't like the model per table arrangement because then all the models become cut-and-paste repeated code. Aside that I think there is a lot to steal from CatalystX::CRUD - it has many things thought over.

            So I am for interfaces (and I've actually started the Form Processing [perlfoundation.org] page with the idea of nailing down the differences and similarities between the different form processing modules - and in the longer perspective abstracting them behind some interface). But I don't want to sacrifice the simplicity of the usage.

            Enough talking. See InstantCRUD - I know it is quite a bit of work to digest all the details of a project like that - but only this will give us some more steady ground for discussion. Of course I promise to get acquinted with your code as well.

            In the evenings I am also at the #formhandler IRC channel (at irc.perl.org) and at the Catalyst mailing list.