pguillard wrote:
Hi all,
I'd like to know if a fd:case for the union widget is still planned to
give more flexibility than the fd:struct or if there is another way to
give a matching expression to the fd:struct.
There were discussions about this [1] which unfortunately have stalled.
IIRC,
Stavros (and others),
First of all, I don't mind that you patch the file and add a bugzilla entry.
Thank you for taking the time to do that.
Second: the forms-samples-styling.xsl file and the dependent XSL files are
powerful enough to merit a place outside the forms samples, but they need a
bit
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31813.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31992.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Leszek Gawron wrote:
Vadim Gritsenko wrote:
How can I retrieve that ID? I could implement a test version for
Carsten.
It is in AbstractInterpreter.getInterpreterID()
Some problems coming. Are there any reasons why doesn't
Interpreter.getInterpreterID() exist? Also
Sylvain Wallez wrote:
Leszek Gawron wrote:
Vadim Gritsenko wrote:
How can I retrieve that ID? I could implement a test version for
Carsten.
It is in AbstractInterpreter.getInterpreterID()
Some problems coming. Are there any reasons why doesn't
Interpreter.getInterpreterID() exist? Also
Il giorno 01/nov/04, alle 03:16, Pier Fumagalli ha scritto:
Just finished writing, please, no comments as of yet... It will MOST
DEFINITELY not work, as it's something put together over a couple of
lazy afternoons while the girlfriend was at some extremely odd
park/garden in South London.
If
Stefano Mazzocchi wrote:
Reinhard Poetz wrote:
I think it can provide a smooth transition from
current blocks to RealBlocks and the work can be done
in incremental steps.
Agreed.
Stefano and others, What do you think, should I
continue with the new block build system?
Go right ahead.
Ok. So
Stefano Mazzocchi dijo:
This is very weird: instead of executing the 'xsp' block, it runs the
'paranoid' block. This is not a gump problem.
Do you people have any idea of what's going on?
Yep! We know! :-D
See this:
project name=cocoon-block-xsp status=stable
On 1 Nov 2004, at 09:20, Ugo Cei wrote:
Il giorno 01/nov/04, alle 03:16, Pier Fumagalli ha scritto:
Just finished writing, please, no comments as of yet... It will MOST
DEFINITELY not work, as it's something put together over a couple of
lazy afternoons while the girlfriend was at some extremely
bdelacretaz wrote:
Author: bdelacretaz
Date: Mon Nov 1 00:57:10 2004
New Revision: 56219
Modified:
cocoon/site/site/index.html
Log:
added ApacheCon logo (by directly editing this page, it is not generated by Forrest,
right?)
Yes it is generated by Forrest. However, this is a good
Hi,
On 28 Oct 2004, at 16:04, Torsten Curdt wrote:
Folks please cast your votes for:
[+1] Leszek
[+1] Ralph
Sorry to be late to the party ;-)
Andrew.
--
Andrew Savory, Managing Director, Luminas Limited
Tel: +44 (0)870 741 6658 Fax: +44 (0)700 598 1135
Web: http://www.luminas.co.uk/
Orixo
Le 1 nov. 04, à 12:16, David Crossley a écrit :
Yes it is generated by Forrest. However, this is a good idea
just to do a quick edit. Probably no-one will update the
source in the next two weeks...
Thanks for the clarification!
-Bertrand
smime.p7s
Description: S/MIME cryptographic signature
We have talked several times about changing the request
processing in cforms to not touch any widget whose
request parameter is missing (to prevent these widgets'
values from being reset to null,) the end result being
that it would be easier for the view to decide how to
split a form across
Hello H,
Stavros (and others),
First of all, I don't mind that you patch the file and add a bugzilla entry.
Thank you for taking the time to do that.
Second: the forms-samples-styling.xsl file and the dependent XSL files are
powerful enough to merit a place outside the forms samples, but
After a lot of mails talking about expression languages and templating enginges
I try to summarize the current state of our discussion. I see following
requirements so far (in brackets you find the name of the person that brought up
the requirement):
- control structures like for/each, if,
Le 1 nov. 04, à 17:30, Reinhard Poetz a écrit :
After a lot of mails talking about expression languages and templating
enginges I try to summarize the current state of our discussion. I
see following requirements so far (in brackets you find the name of
the person that brought up the
Bertrand Delacretaz wrote:
Le 1 nov. 04, à 17:30, Reinhard Poetz a écrit :
After a lot of mails talking about expression languages and templating
enginges I try to summarize the current state of our discussion. I
see following requirements so far (in brackets you find the name of
the person
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=26854.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
I'm going to integrate the new Rhino+cont implementation in the next few days
and plan to support the old and the new implementation, at least in 2.1. I
wonder ...
1. What do we want to call the new implementation (I mean the language
name in map:flow language=???/).
a.) call the new
Reinhard Poetz wrote:
After a lot of mails talking about expression languages and templating
enginges I try to summarize the current state of our discussion. I see
following requirements so far (in brackets you find the name of the
person that brought up the requirement):
- control
Is the new implementation compatible (from the user's perspective) with
the old version? If so, in my opinion you can just switch it now. If
changes will be required then a notice should go out with 2.1.6 in the
release notes and the switch would occur in 2.1.7.
Ralph
Reinhard Poetz said:
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=30417.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=30417.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
So anyway, I didn't know if I should (a) re-open the bug, (b) create a
new one for the new patch, or (c) leave it CLOSED but attach my revised
patch. I guessed (c) was probably the right answer... please advise
:-)
~mark
On Nov 1, 2004, at 1:06 PM, [EMAIL PROTECTED] wrote:
DO NOT REPLY TO
On Thu, Oct 14, 2004 at 12:11:06PM +0200, Bart Molenkamp wrote:
Another thing that may be needed is to do some modifications on the
FormsTransformer and the forms stylesheets. Forms using unions and
structs still have f* tags in their code, eg. fi:union, ft:case and
fi:struct.
Fixed in the
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=30417.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=30417.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi Mark:
If the bug was not fixed, then the correct is to reopen it. I already did
that. You can see the activity history here:
http://issues.apache.org/bugzilla/show_activity.cgi?id=30417
Best Regards,
Antonio Gallardo
Mark Lundquist dijo:
So anyway, I didn't know if I should (a) re-open
Thx, Antonio :-)
~mark
On Nov 1, 2004, at 1:20 PM, Antonio Gallardo wrote:
Hi Mark:
If the bug was not fixed, then the correct is to reopen it. I already
did
that. You can see the activity history here:
http://issues.apache.org/bugzilla/show_activity.cgi?id=30417
Best Regards,
Antonio Gallardo
A long time ago I made improvements that you are talking
about. I'm not sure if
they are still up-to-date, but I can do some investigation
and send the patch :-)
Please do!
Thanks.
Bye, Helma
Hi:
First of all congratulations to Igor Bukanov from the Mozilla community,
to you and to the other people that make this posible!
To answer your question is hard because:
1-We have nearly 1 month waiting for the 2.1.6 release.
2-Same as Ralph: If the changes don't break beackward
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31297.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Il giorno 01/nov/04, alle 12:16, Pier Fumagalli ha scritto:
Maybe KernelException should be unchecked, well, done anyway!
Fine. Another small observation, if you don't mind. The name of the
Abstract class is a little vague. Can't we find a better name?
Ugo
--
Ugo Cei -
Le 1 nov. 04, à 19:28, Reinhard Poetz a écrit :
...I would wait with switching to the new flowscript implementation
until the release of 2.1.6 Then we have a few months to test it in
branch and trunk and if everything goes well I would deprecate the old
one and rename it to javascript-legacy
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31297.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
On 01.11.2004 09:20, Sylvain Wallez wrote:
I'd like to know if a fd:case for the union widget is still planned to
give more flexibility than the fd:struct or if there is another way to
give a matching expression to the fd:struct.
There were discussions about this [1] which unfortunately have
Bertrand Delacretaz said:
+1, there's no hurry I think, better switch after the release to test
the new implementation a bit more.
Stability is extremely important and should not be compromised. That
said, if this change is backward compatible I view getting this in as
extremely important.
I
Coincidentally I'm just starting work on a templater too. I have been using JXTemplate
and I really like it, but a few things have frustrated me about it, too.
Perhaps it's unusual, but I really like it BECAUSE it's like XSLT, and I don't mind at
all that it's not like Java. The things I don't
Antonio Gallardo wrote:
Stefano Mazzocchi dijo:
This is very weird: instead of executing the 'xsp' block, it runs the
'paranoid' block. This is not a gump problem.
Do you people have any idea of what's going on?
Yep! We know! :-D
See this:
project name=cocoon-block-xsp status=stable
Reinhard Poetz wrote:
I'm going to integrate the new Rhino+cont implementation in the next few
days and plan to support the old and the new implementation, at least in
2.1. I wonder ...
Jesus, what happened to the release early and often paradigm? 2.1.6 has
been in the making forever.
On 1 Nov 2004, at 21:42, Ugo Cei wrote:
Il giorno 01/nov/04, alle 12:16, Pier Fumagalli ha scritto:
Maybe KernelException should be unchecked, well, done anyway!
Fine. Another small observation, if you don't mind. The name of the
Abstract class is a little vague. Can't we find a better name?
On 1 Nov 2004, at 23:22, Stefano Mazzocchi wrote:
Reinhard Poetz wrote:
I'm going to integrate the new Rhino+cont implementation in the next
few days and plan to support the old and the new implementation, at
least in 2.1. I wonder ...
Jesus, what happened to the release early and often
Pier Fumagalli dijo:
On 1 Nov 2004, at 23:22, Stefano Mazzocchi wrote:
Reinhard Poetz wrote:
I'm going to integrate the new Rhino+cont implementation in the next
few days and plan to support the old and the new implementation, at
least in 2.1. I wonder ...
Jesus, what happened to the
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=26854.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Tim Larson dijo:
We have talked several times about changing the request
processing in cforms to not touch any widget whose
request parameter is missing (to prevent these widgets'
values from being reset to null,) the end result being
that it would be easier for the view to decide how to
Pier Fumagalli said:
On 1 Nov 2004, at 23:22, Stefano Mazzocchi wrote:
Jesus, what happened to the release early and often paradigm? 2.1.6
has been in the making forever. Can we get that sucker out of
the door or we have to fix all the bugs before we do? and that will
never happen
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-xsp *no longer* has an issue.
The current state of this project is
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-chaperon has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-hsqldb has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-woody has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-forms has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-portal has an issue affecting its community integration.
This issue
Ralph Goers wrote:
Is the new implementation compatible (from the user's perspective) with
the old version? If so, in my opinion you can just switch it now. If
changes will be required then a notice should go out with 2.1.6 in the
release notes and the switch would occur in 2.1.7.
IIRC, there is
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32011.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
On Mon, Nov 01, 2004 at 11:19:15PM +0100, Joerg Heinicke wrote:
On 01.11.2004 09:20, Sylvain Wallez wrote:
I'd like to know if a fd:case for the union widget is still planned to
give more flexibility than the fd:struct or if there is another way to
give a matching expression to the
On Mon, Nov 01, 2004 at 06:13:21PM -0600, Antonio Gallardo wrote:
Tim Larson dijo:
We have talked several times about changing the request
processing in cforms to not touch any widget whose
request parameter is missing (to prevent these widgets'
values from being reset to null,) the end
Thanks to all!
Tim Larson wrote:
On Mon, Nov 01, 2004 at 11:19:15PM +0100, Joerg Heinicke wrote:
On 01.11.2004 09:20, Sylvain Wallez wrote:
I'd like to know if a fd:case for the union widget is still planned to
give more flexibility than the fd:struct or if there is another way to
give a
58 matches
Mail list logo
