Vadim Gritsenko wrote:
Nicola Ken Barozzi wrote: <snip/>
*IMPORTANT* (and the reason why I started the RT):
So in he CLI, instead of asking for the link view and then generate, I simply ask Cocoon to insert a transformer that gathers links in the same positions where the links view would.
This would make it possible for the CLI to have the configurability of the view gatherer but the speed of the transfomer gatherer.
Links view is not a transformer. It's a view, meaning that it can have actions, matchers, selectors, transformers, and should end with text serializer. So, you cannot simply add one transformer and think that you are done with links view.
You are right - Nicola Ken is here mixing up Link View and Link Gathering - two different approaches. What he says though is relevant to the link gathering approach, i.e. that it could be implemented with an 'aspect' allowing the user to insert the gathering stage at any point in their pipeline, by attaching a gathering transformer to a label (defaulting to the last stage, just before the serializer).
Once we have links view working allright, we will kill link gathering alltogether -- anyway it was just a hack ;-)
Vadim
