Antonio Gallardo wrote:
On Mie, 9 de Febrero de 2005, 4:52, Andrew Savory dijo:
On 9 Feb 2005, at 09:20, Carsten Ziegeler wrote:
2) create two blocks for each block that supports xsp: for example a
databases and a databases-xsp block
I suspect this is the easiest option.
Forget to say the
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
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
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
Carsten Ziegeler wrote:
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
Hi,
On 9 Feb 2005, at 09:20, Carsten Ziegeler wrote:
2) create two blocks for each block that supports xsp: for example a
databases and a databases-xsp block
I suspect this is the easiest option.
Forget to say the obvious: this is of course only for trunk.
Hmm - any reason why it can't happen in
On Mie, 9 de Febrero de 2005, 4:52, Andrew Savory dijo:
Hi,
On 9 Feb 2005, at 09:20, Carsten Ziegeler wrote:
2) create two blocks for each block that supports xsp: for example a
databases and a databases-xsp block
I suspect this is the easiest option.
Forget to say the obvious: this is
Reinhard Poetz wrote:
Carsten Ziegeler wrote:
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,
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
Il giorno 09/feb/05, alle 18:37, Carsten Ziegeler ha scritto:
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?
+1
--
Ugo Cei - http://agylen.com/blojsom/blog/
Carsten Ziegeler wrote:
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
11 matches
Mail list logo
