Damien McKenna wrote:
So the facets-lite wasn’t for the pages view? I just found it by
searching trac for “facets”.
Facets-lite was only for the page editing interface, not the main
What were the original goals of the project? How were you intending it
would work? What do you now want to change on it? If you could explain
this we might be able to help steer it in the right direction?
The original goals of the facets branch were to compartmentalize parts
of the page-editing interface so that they could be more easily and
unobtrusively modified. It operates on the principle that view
templates and partials define ‘regions’ that are filled with other
partials at render-time. You can define the contents of the regions via
the ‘admin’ object. The sample extension does a good job of showing how
to use the object.
There are some quirks to the interface, however, and I’m not sure it’s
in the right place of the API/application.
Right now I don’t have a clear answer on what I would want to change,
but my general feeling is that some things aren’t quite right. I’d have
to spend some time re-reading the code to see what needs fixing.
I was thinking a simply way to add an action column to the Pages list
would be an ample start to any grander plans, that would allow us to
start making extensions behave nicely.
This is one area in which facets needed to expand. It also needed to
cover the layout and snippets interfaces as well.
I’d like to be able to have the ReOrder and CopyMove extensions on the
same page, playing nicely. I can rework the extensions to suit, but
it’s tweaking the core I’m nervous about.
If you could document what you’d like Facets to do we could try to work
towards that goal?
Yes, but I prefer not creating more work for myself - when v0.6.5 or 0.7
rolls out with a replacement I’ll have wasted time getting.
Yes. As mentioned though if I’m going to help I’d like to at least be
working in the same direction as the main project, so my efforts don’t
go to waste.
Unfortunately, facets has become kind of the
cold-fusion-Perl-6-Duke-Nukem-Forever of the Radiant project. I agree
that the functionality is sorely needed; extensions that step on each
other are a real problem. Unless it becomes stable and mature, it won’t
be merged into any other branches or trunk before 0.6.5 or 0.7.
However, if you would like to contribute, I’d say first familiarize
yourself with the codebase and especially the tests. Then, checkout
facets and create a diff between it and trunk, then merge the changes
into your facets checkout. Once you have that, go after the most
accessible part of the code that you’d like to change. Write tests,
verify your changes. Submit a patch to the Trac. Since it’s an
experimental branch, if your patch looks good, I’ll be sure to accept
and apply it (once I find a minute… typing this email took a while