Unico Hommes wrote: > > I doubt there are (m)any custom pipeline implementations out > there. I think it shouldn't be a consideration if it means > sacrificing code transparency. Not that I am saying it I > think it will (don't know), but if it helps to make the code > cleaner or better I prefer incompatible changes. > > Btw. The only code I use from the treeprocessor is the > variable resolver stuff. I think this code is of general > enough interest to dedicate its own subpackage for (away from > treeprocessor). I noticed Carsten currently has duplicated > that code in the portal block. WDYT? > Yepp, I think the variable resolver is a useful component that has general interest. The version in the portal block has currently not the stack support for nested sitemap components (map and actions) as this isn't a general feature. The version in the portal block already uses the o.a.c.components... as the package name so we can simply move it to the core and perhaps enhance it.
Carsten
