Re: [web2py] should re remove crud from the book?
... But if we want to keep it longer term we need a better reason. A recent post has reminded me about a really cool crud feature: crud.settings.many table-wide callbacks and other options What would be the replacements for SQLFORM?, I don't think that SQLFORM supports this kind of options. --
Re: [web2py] should re remove crud from the book?
El sábado, 22 de diciembre de 2012 19:30:17 UTC-3, Alan Etkin escribió: I like crud very much (it's almost tallking english to the server) crud.read crud.update, ... it's like a web2py classic. For me, sounds like your preferred pizza delivery is not selling pepperoni anymore I guess I need to clarify the pizza metaphor: What I'm saying is that crud is intended as a simpler wrapper for sqlform and users should not be encouraged to replace it with the latter, since one reason for the use of the first object is to simplify code. Whenever a user needs a more complete API he can switch to sqlform, provided that crud is updated to support all new sqlform features. --
Re: [web2py] should re remove crud from the book?
LOL. I understand. For now this will stay. But if we want to keep it longer term we need a better reason. One posibility would be to rewrite crud keeping the current API (which you like) on top the new DALForm object from web3py (which is faster than form handling in web2py). Massimo On Sunday, 23 December 2012 12:18:32 UTC-6, Alan Etkin wrote: El sábado, 22 de diciembre de 2012 19:30:17 UTC-3, Alan Etkin escribió: I like crud very much (it's almost tallking english to the server) crud.read crud.update, ... it's like a web2py classic. For me, sounds like your preferred pizza delivery is not selling pepperoni anymore I guess I need to clarify the pizza metaphor: What I'm saying is that crud is intended as a simpler wrapper for sqlform and users should not be encouraged to replace it with the latter, since one reason for the use of the first object is to simplify code. Whenever a user needs a more complete API he can switch to sqlform, provided that crud is updated to support all new sqlform features. --
[web2py] should re remove crud from the book?
I am finishing up the book 5th edition. I was to remove every mention of the crud API. Almost all of the functionality has been moved into SQLFORM(...).process(). The latter is in fact better. The crud code has not been updated in long time and should be deprecated. The code will stay and we are not breaking it. Should we remove it form the book completely or simply leave the chapter and mark is as reprecated. massimo --
Re: [web2py] should re remove crud from the book?
On 22 Dec 2012, at 11:44 AM, Massimo Di Pierro massimo.dipie...@gmail.com wrote: I am finishing up the book 5th edition. I was to remove every mention of the crud API. Almost all of the functionality has been moved into SQLFORM(...).process(). The latter is in fact better. The crud code has not been updated in long time and should be deprecated. The code will stay and we are not breaking it. Should we remove it form the book completely or simply leave the chapter and mark is as reprecated. If we mark it deprecated, we should define (in the book) exactly what we mean by that. --
Re: [web2py] should re remove crud from the book?
I am going over the book with grep. The problems are these: 1) crud checks permission, SQLFORM does not. 2) crud is used in welcome 3) in chapter 13 we say plugins can rely on crud. So on a second thought we cannot easily remove it form the book. I will remove some examples to avoid using crud. I will provide examples of how to enforce permissions with SQLFORM without using crud. I add a notice at the beginning of the crud chapter to suggest using SQLFORM instead of crud. We cannot remove it from welcome app because plugins require it. Therefore we cannot remove it from book quote yet. I am not too happy about this but I cannot think of a better solution. Massimo On Saturday, 22 December 2012 13:48:39 UTC-6, Jonathan Lundell wrote: On 22 Dec 2012, at 11:44 AM, Massimo Di Pierro massimo@gmail.comjavascript: wrote: I am finishing up the book 5th edition. I was to remove every mention of the crud API. Almost all of the functionality has been moved into SQLFORM(...).process(). The latter is in fact better. The crud code has not been updated in long time and should be deprecated. The code will stay and we are not breaking it. Should we remove it form the book completely or simply leave the chapter and mark is as reprecated. If we mark it deprecated, we should define (in the book) exactly what we mean by that. --
Re: [web2py] should re remove crud from the book?
I like crud very much (it's almost tallking english to the server) crud.read crud.update, ... it's like a web2py classic. For me, sounds like your preferred pizza delivery is not selling pepperoni anymore El sábado, 22 de diciembre de 2012 16:57:34 UTC-3, Massimo Di Pierro escribió: I am going over the book with grep. The problems are these: 1) crud checks permission, SQLFORM does not. 2) crud is used in welcome 3) in chapter 13 we say plugins can rely on crud. --
