Stephan Michels wrote:
Am Di, den 09.03.2004 schrieb Bertrand Delacretaz um 16:37:
We should move XSP in a block anyway.
+1 from Stefano, Antonio, Reinhard
+0.5 (=good idea, won't be able to help)
I can offer some help, if nobody on it, then I can try it?!
Go right ahead!
--
Stefano.
Unico Hommes wrote:
Carsten Ziegeler wrote:
Torsten Curdt wrote:
Carsten Ziegeler wrote:
Unico Hommes wrote:
I tend to think the dependency is from session-fw on xsp, not the
other way around. Unless this becomes really difficult to
accomplish
I'd prefer keeping it the
Am Di, den 09.03.2004 schrieb Bertrand Delacretaz um 16:37:
We should move XSP in a block anyway.
+1 from Stefano, Antonio, Reinhard
+0.5 (=good idea, won't be able to help)
I can offer some help, if nobody on it, then I can try it?!
Stephan.
Stephan Michels wrote:
Am Di, den 09.03.2004 schrieb Bertrand Delacretaz um 16:37:
We should move XSP in a block anyway.
+1 from Stefano, Antonio, Reinhard
+0.5 (=good idea, won't be able to help)
I can offer some help, if nobody on it, then I can try it?!
Awsome, I'm
Unico Hommes wrote:
Awsome, I'm willing to do some stuff as well. I think that
besides just moving code around it involves some work
regarding quite a few core samples that use XSP. Here's a list:
./common/view-source.xsp
./flow/calc/screens/displayResult.xsp
Carsten Ziegeler wrote:
Unico Hommes wrote:
Awsome, I'm willing to do some stuff as well. I think that
besides just moving code around it involves some work
regarding quite a few core samples that use XSP. Here's a list:
./common/view-source.xsp
./flow/calc/screens/displayResult.xsp
Unico Hommes wrote:
Carsten Ziegeler wrote:
Unico Hommes wrote:
Awsome, I'm willing to do some stuff as well. I think that besides
just moving code around it involves some work regarding quite a few
core samples that use XSP. Here's a list:
./common/view-source.xsp
Am Mi, den 10.03.2004 schrieb Reinhard Pötz um 11:03:
Stephan Michels wrote:
Am Di, den 09.03.2004 schrieb Bertrand Delacretaz um 16:37:
We should move XSP in a block anyway.
+1 from Stefano, Antonio, Reinhard
+0.5 (=good idea, won't be able to help)
I
Stephan Michels wrote:
Am Mi, den 10.03.2004 schrieb Reinhard Pötz um 11:03:
Stephan Michels wrote:
Am Di, den 09.03.2004 schrieb Bertrand Delacretaz um 16:37:
We should move XSP in a block anyway.
+1 from Stefano, Antonio, Reinhard
+0.5
I have following problem, that
src/blocks/session-fw/conf/xsp-session-fw.xconf
depends on the xsp block, but won't be executed before the
patch files
of the xsp block :-/
This may require a change to the build system. Hmm.
What about moving *all* xsp stuff into the xsp block?
Am Mi, den 10.03.2004 schrieb Carsten Ziegeler um 14:24:
I have following problem, that
src/blocks/session-fw/conf/xsp-session-fw.xconf
depends on the xsp block, but won't be executed before the
patch files
of the xsp block :-/
This may require a change to the build
Reinhard Pötz wrote:
Stephan Michels wrote:
Am Di, den 09.03.2004 schrieb Bertrand Delacretaz um 16:37:
We should move XSP in a block anyway.
+1 from Stefano, Antonio, Reinhard
+0.5 (=good idea, won't be able to help)
I can offer some help, if nobody on it, then I can try
Unico Hommes wrote:
Unico Hommes wrote:
Carsten Ziegeler wrote:
...
Interestingly some of these samples (e.g. flow) are ported in 2.2
from xsp to jx...
Yep I already started doing some work in that department :-)
BTW. this was done only in the flow samples and regarding me wanting
to test
Vadim Gritsenko wrote:
Please note that currently jxtransformer/generator is not up
to speed in non-flow environment. It has to be extended /
completed first in order to be xsp replacement.
I hope to come up with a solution in the next weeks
Carsten
Vadim Gritsenko wrote:
Unico Hommes wrote:
Unico Hommes wrote:
Carsten Ziegeler wrote:
...
Interestingly some of these samples (e.g. flow) are ported in 2.2
from xsp to jx...
Yep I already started doing some work in that department :-)
BTW. this was done only in the flow samples and
Unico Hommes wrote:
I tend to think the dependency is from session-fw on xsp, not
the other way around. Unless this becomes really difficult to
accomplish I'd prefer keeping it the way it is now. I will do
some research as to what would be involved to change the
build system to
Please note that currently jxtransformer/generator is not up to speed in
non-flow environment. It has to be extended / completed first in order
to be xsp replacement.
Yes, this is certainly needed to help the jxtransformer/generator
conquer XSP. I am currently using the JXTemplateGenerator to
Stefano Mazzocchi wrote:
We should move XSP in a block anyway.
+1 from Stefano, Antonio, Reinhard
--
Reinhard, giving this thread an appropriate subject but doesn't mean he will do the
move ;-)
We should move XSP in a block anyway.
+1 from Stefano, Antonio, Reinhard
+0.5 (=good idea, won't be able to help)
-Bertrand
Reinhard Pötz wrote:
Stefano Mazzocchi wrote:
We should move XSP in a block anyway.
+1 from Stefano, Antonio, Reinhard
+1
--
Unico
Am Di, den 09.03.2004 schrieb Unico Hommes um 16:39:
Reinhard Pötz wrote:
Stefano Mazzocchi wrote:
We should move XSP in a block anyway.
+1 from Stefano, Antonio, Reinhard
+1
Big +1
Stephan Michels.
Bertrand Delacretaz wrote:
We should move XSP in a block anyway.
+1 from Stefano, Antonio, Reinhard
+0.5 (=good idea, won't be able to help)
same here,
Geoff
On Tue, Mar 09, 2004 at 11:20:46AM -0500, Geoff Howard wrote:
Bertrand Delacretaz wrote:
We should move XSP in a block anyway.
+1 from Stefano, Antonio, Reinhard
+0.5 (=good idea, won't be able to help)
same here,
Geoff
and same reasoning here, +0.5
--Tim Larson
Reinhard Pötz wrote:
Stefano Mazzocchi wrote:
We should move XSP in a block anyway.
+1 from Stefano, Antonio, Reinhard
+1
/Daniel
On 09.03.2004 16:34, Reinhard Pötz wrote:
We should move XSP in a block anyway.
+1
25 matches
Mail list logo
