I just did a check which blocks require xsp: - "python" Uses the xsp core, so this is ok
- "chaperon",
- "lucene"
- "eventcache"
All these three use xsp just for the samples, so we should imho simply rewrite the samples.
- "databases" - "session-fw". These two are the only blocks that have own logigsheets.
- "scratchpad" Don't know why this depends on XSP. Anyone?
So I would suggest to rewrite the samples and simply move the logicsheets to the xsp blocks; imho it's not worth creating new blocks just because of these two logicsheets. WDYT?
Carsten
Carsten Ziegeler wrote:
We some blocks that depend on XSP just because they provide some logigsheets (session, databases etc.), so as soon as you want to use them you *have* to include XSP although you don't use it at all.
We discussed this already, but didn't change anything :(
I see two solutions:
1) either move all xsp related stuff into the xsp block and then the xsp block depends on other blocks.
2) create two blocks for each block that supports xsp: for example a databases and a databases-xsp block. Obviously the first one contains the block without logigsheets and is free of XSP and the second one just contains all the XSP stuff, depends on the databases and the XSP block. Et voila.
Leaving it the way it is is really annoying.
WDYT?
-- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
