I didn't look into the code but it looks like CRUD extends SQLFORM... so it is your choice in using SQLFORM and do few things by hand, or use CRUD and create a prototype in less lines and therefore in less time !...
On Thu, Jun 2, 2011 at 11:50 AM, apple <simo...@gmail.com> wrote: > In previous post it was stated that CRUD was more for prototyping and > SQLFORM for when you need more control. However now I see that there > is some additional functionality in CRUD e.g. the link with the auth > module; and archiving of records. > > It seems to me these are two separate ways of doing the same thing but > with slightly different interfaces. Quite confusing. I wonder why the > CRUD functionality was not just incorporated into SQLFORM rather than > creating a separate interface? > > Personally I would rather stick with one or the other because it is > easier to remember the quirks and names of parameters. Should I choose > SQLFORM as it allows most flexibility or CRUD as this will ultimately > have greater functionality? > > -- Sebastian E. Ovide
