I would like to contribute and maintain a module called Views Contextual Displays.
Summary:
The module extends the Display Suite Object row style plugin for Views allowing contexts, defined through the Context module, to set build modes dynamically. This enables us to create a View of which the rowfields can be dynamically switched depending on the context.
This is useful if you would like to build a view with objects who have restricted fields. Logging in with trigger a context which would set the build mode with all the fields while anon users would see a restricted build mode. Using clunky field permissions is no longer required.
This module has been build with support/tips from Swentel, maintainer of Display Suite.
A ready to commit first dev version can be found here:
https://github.com/netsensei/Views-Contextual-Displays
Only supports D6 atm but when feature complete, I plan a port to D7.
Thank you!
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | netsensei-Views-Contextual-Displays-5ce92cf.tar_.gz | 3.67 KB | netsensei |
Comments
Comment #1
netsensei commentedA tar'ed version of the module straight from Github.
Github commit ID: 5ce92cf
Comment #2
rfaySubscribe - Congratulations, looking forward to looking at it. You'll get approved. Just have to jump through the hoops.
Comment #3
attiks commentedNice one! +1
Will/Do you support views 3 (D6) as well?
I had a quick look at the code, and all is looking clean, except for some formatting issues (see https://github.com/netsensei/Views-Contextual-Displays/blob/master/views...)
Comment #4
swentel commented+1 from me too for several, mostly biased reasons, but there still valid of course :)
- He's my colleague, I know the guy :)
- I've actually seen the code working on his laptop
- As the maintainer of Display Suite I'm excited to see new contribs and I can possibly add him as maintainer to those modules
- He's been active already contributing patches on DS, but also in various other queues too
- We will not see the last of him after this first contribution, pretty sure of that!
Comment #5
pcambra+1 Reviewed the code, looks good to me
Comment #6
avpadernoPlease read all the following and the links provided as this is very important information about your CVS Application.
Drupal.org has moved from CVS to Git! This is a very significant change for the Drupal community and for your application. Please read the following documentation on how this affects and benefits you and the application process:Migrating from CVS Applications to (Git) Full Project Applications.
Comment #7
zzolo commentedHey @kiamlaluno. I think for the this one, we should maybe just pass it through to approved, since it was already RTBC? I also don't know if how (or if I still can) approve user access. Thanks for all your help on these issues.
Comment #8
netsensei commentedOkay.
I've set up my Git account, created a new Git sandbox project and migrated all my Github code...
The Applying For Full Projects instructions (http://drupal.org/node/1011698) mention something about applying again by creating a new issue here: http://drupal.org/project/issues/projectapplications. Then again, it's been four weeks since my application here got RTBC...
Comment #9
zzolo commentedHi @netsensei. Sorry for the confusion. I have just given you Full Project access. Please make sure to read up on the following and the child articles:
http://drupal.org/documentation/git
http://drupal.org/node/10259
Comment #12
avpadernoI am giving credits to the users who actively participated in this issue.