[test] Remove upper bound for cubicweb-localperms
Version 0.4.0 does not use a deprecated API that we are planning to drop
in forthcoming changesets.
This requires changing expected values in unittest_cwconfig.py where we
scan install cubes.
* In CubicWebConfigurationTC.test_available_cubes(), localperms
disappears from the list of expected cubes because this test method
will look for new style cubes in located in cubicweb/test/data/libpython/
(we patch pkg_resources.iter_entry_points()) as well as old style
cubes installed in $PREFIX/share/cubicweb/cubes; since the new
cubicweb-localperms version is new-style, it won't be catched by this
method.
* In CubicWebConfigurationWithLegacyCubesTC.test_available_cubes(),
localperms is still listed, but now with the package name, because
this method will simply look at installed cubes whether old or new
style.
Once you have read the `RQL tutorial`_ and you know the application'`schema`_,
you're ready to define your own views. Just type the RQL query retreiving data
you're interested in in the search field. If the view used to display them
doesn't fit your need, choose another one in the possible views box (this box
isn't displayed by default, but you can activate it in your `user
preferences`_). Once you're satified, add a `bookmark`_ if you want to reuse
this view later.
.. _`RQL tutorial`: tut_rql
.. _`schema`: ../schema
.. _`user preferences`: ../myprefs
.. _`bookmark`: bookmarks
Below are some example of what can be acheived...
.. winclude:: custom_view_last_update
.. winclude:: custom_view_rss