CubicWeb 3.9.0 went out last week. We now have tested it in production and fixed the remaining bugs, which means it is now show time!
The 3.9 release development was started by a one week long sprint at the
beginning of May. The two goals were first to make it easier to customize the look and
library. This led to the following major changes.
- We introduced property sheets, which replace former external_resources
file, as well as define some constants that will be used to 'compile' cubicweb
and cubes' stylesheets.
- We started a new, clean cubicweb.css stylesheet, that tries to keep up
with the rhythm. This is still a work in progress, and by default the old
css is still used, unless specified otherwise in the configuration file.
- We set the bases for web functional testing using windmill. See test cases
in cubicweb/web/test/windmill/ and python wrapper in
cubicweb/web/test_windmill/ if you want to use this in your own cube.
cubicweb/web/test/jstests/ and python wrapper in
cubicweb/web/test_jscript/ if you want to use this in your own cube.
namespace, the ajax api is now much simpler thanks to more generic and
powerful functions. As usual backward compatibility was kept, which means
that your existing code will still run, but you will see tons of deprecation
warnings in the firebug console.
But that's not all! There are also two major changes in 3.9.
The first major change is the introduction of adapters, also found in the
Zope Component Architecture and documented in the GoF book. This will
allow for better application design and easier code reuse. You
can see several usage in the framework, for instance the "ITree" adapter in
cubicweb.entities.adapters, the "IBreadCrumbs" adapter in
cubicweb.web.views.ibreadcrumbs, or still the "ICalendarable" adapter in
The second major change will benefit directly to end users: we worked with our
friends from SecondWeb to expose the ranking feature found in postgres
full-text search. This clearly improves the user experience when doing
full-text searches. Ranking may be finely tuned by setting different weights
to entity types, entity types attributes, or even be dynamically computed
per entity instance. Of course, all this is done in an adapter, see
"IFTIndexableAdapter" in cubicweb/entities/adapters.py.
Other minor changes include:
- support for wildcard text search for application using postgres >= 8.4 as
backend. Try searching for 'cub*' on cubicweb.org for instance.
- inline edition of composite relation
- nicer, clickable, schema image of the data model
- enhanced support for the SQLserver database