Kristen, regarding our recent conversation I'd love to help out as co-maintainer creating some D7 views. Would that work for you?

Comments

Kristen Pol’s picture

Sounds great! Let me see how to get you a git account...

Thanks!!
Kristen

Kristen Pol’s picture

I added you as a co-maintainer and configured it to allow you to use the version control for the project so maybe if you reload the project page it will show you something about the repository... ??

Kristen

johnstorey’s picture

Assigned: Unassigned » johnstorey
Status: Active » Closed (fixed)

Yes, if I look under the Version Control tab I now have write access to the repository.

Kristen Pol’s picture

Ok, adding an example to the code is pretty easy:

1) check out the repository

2) put the repository directory into a drupal 6 module contrib directory, e.g. sites/all/modules/contrib for a test site

3) enable views_examples module along with views and any other required modules

4) go and create a view with views that you think my be a good one for others to use

5) export the views code and save file with the naming convention:

vex_[title].vex

e.g. there already exists:

vex_comments_posts.vex
vex_similar_by_terms.vex
vex_files_general.vex
etc.

6) put the file into one of the existing examples directories:

* accesslog
* comment
* file
* node
* term
* user

or you can create a new directory if it is better categorized differently

7) edit the file and change the name to have the same naming convention, e.g.

$view->name = 'vex_similar_by_terms';

9) create an "info" file for your example with the same name as the .vex file, e.g.

vex_similar_by_terms.info

and put a name, description and package in it... look at another info file for an example

8) go to the views_examples settings page (/admin/settings/views_examples) and enable your new example

9) go to views and your new view should be showing up

10) enable the new view and play around with it

11) if it works, then check-in the new .vex and .info files (and new directory if applicable)

Note that now that features is so mature, it would make sense to redo this whole module using features. I should set up a 2.x branch to do that. It would need to have separate features modules depending on the module dependencies so that users can use the simpler views without relying on other modules besides views.