Talking about future needs... What would you do/how would you display in the admin if the columns are to be read-only only for certain groups ? For example editors can modify most parameters of an article, but only a publisher should be able to change it's status.
On Mar 31, 5:06 pm, Yarko Tymciurak <yark...@gmail.com> wrote: > On Tue, Mar 31, 2009 at 8:03 AM, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > I do not understarstand > > What I am saying is that you "solved" the problem of write permissions on a > column in appadmin by ignoring the permissions. If I now want to be able > to see the various permissions in appadmin, there will be another patch... > and if I want something else that has to do with authorization on a data > item, it too will be some other code... > > What I want to see is permissions cause / limit access and take a specific > behavior in the application - and have that permission setup. > > For example: PyCon registration (I am making this up I think): if there > is a field that the registration desk managers want something done with > (maybe not just showing up on a form), I do not want to patch code > everywhere; instead, I want to set a behavior for that..... field's > permission... > > I have not thought through all the details yet, but that is the point: I > want us to think about this more. The only thing I think I am sure about is > I am not happy with the solution in place yesterday. Yes, it solved an > immediate problem - and it's fine for a quick patch. But I want to plan to > remove the patch, and talk about what the nature of the problem that was > discovered is, and find the structure that will handle that nature (and > therefore enable easy adapting to future, unanticipated "needs" that are > related). > > Massimo - I hope that last paragraph makes sense to you in light of the > Finiteness paper.... > > Anyway, patch ok for now; lets think about what's going on and see if we > can't find a better fitting solution. > > > > > On Mar 30, 11:45 pm, Yarko Tymciurak <yark...@gmail.com> wrote: > > > I looked at your post into trunk, Massimo - expedient... but can we have > > > this be something more... functional before next release? > > > I am thinking like this: > > > > istead of: > > > > ignore_rw=True > > > > appadmin would serve better to have something like this: > > > > rw.action= some_function() > > > > Ignore could be implemented this way... > > > > What do you think? > > > > On Mon, Mar 30, 2009 at 7:22 PM, mdipierro <mdipie...@cs.depaul.edu> > > wrote: > > > > > in trunk > > > > > On Mar 30, 11:49 am, Vidul Petrov <vidul.r...@gmail.com> wrote: > > > > > I agree. > > > > > > On Mar 30, 7:28 pm, TheDude <officed...@gmail.com> wrote: > > > > > > > Yes! I was disapointed to find out this wasn't the case and had to > > go > > > > > > back into my db.py models and change it. +1 :) > > > > > > > On Mar 30, 11:11 am, AchipA <attila.cs...@gmail.com> wrote: > > > > > > > > +1 > > > > > > > > On Mar 30, 4:37 pm, Kacper Krupa <pageno...@gmail.com> wrote: > > > > > > > > > i also agree > > > > > > > > > On Mar 30, 4:23 pm, Timothy Farrell <tfarr...@swgen.com> > > wrote: > > > > > > > > > > +1 > > > > > > > > > > johann.scheibelho...@easytouch-edv.com wrote: > > > > > > > > > > agree > > > > > > > > > > > On Mar 30, 4:10 pm, mdipierro <mdipie...@cs.depaul.edu> > > wrote: > > > > > > > > > > >> Right now if you say: > > > > > > > > > > >> db.table.field.writable=False > > > > > > > > > > >> your field will be hidden to both custom forms and > > appadmin > > > > forms. I > > > > > > > > > >> think appadmin forms should ignore these constraints and > > > > always > > > > > > > > > >> display all fields. Do you agree? > > > > > > > > > > >> Massimo > > > > > > > > > > -- > > > > > > > > > Timothy Farrell <tfarr...@swgen.com> > > > > > > > > > Computer Guy > > > > > > > > > Statewide General Insurance Agency (www.swgen.com) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
