My best advice is to plan it as cleanly and thoroughly as you can before you start tinkering with tools and inadvertently paint yourself into a corner.
On Hobo's part the whole thing boils down to "can this user create/edit/update now?", with the addition of per-field "is this user allowed to see this field?" permissions as well. You put behind this as simple or as complex a logic as you find it makes sense for your situtaion, To reduce your work, I suggest you look at capapbility/permission frameworks, e.g. cancan/cancancan or look around for others. There's plenty of boilerplate you could spare that way, time better spent on focusing on what's really specific to your application. 2015. július 17., péntek 18:05:13 UTC+2 időpontban Nathan Peters a következőt írta: > > I'm starting a new Hobo project that is going to have a very complicated > (to my experience) permission structure. It is a process control app. > Visibility on some things will be controlled both by date and by active > user. Users will not even be able to see certain things until a target > date, at which point they will have edit rights which should be removed > after a second target date. In short, it is heady stuff. > > Any tips as I delve into this type of thing? Are there some examples out > there (on GitHub or other) that would be a good reference as I think about > more complicated process permissions in Hobo? > > Thanks, > Nathan > -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/hobousers. For more options, visit https://groups.google.com/d/optout.
