Berin Loritsch wrote:
OOPS! Wrong list. My oppologies.
Actually, it's a pleasure to see Avalon growing again as a community :-D
PS: Is oppoligy a contraption for oops my apologies? Cool! ;-)
Berin Loritsch wrote:
Let's do this right this time. I would like to propose Hamilton Oliveira
as a
From: Christopher Oliver
In that case, the Woody flowscript api needs to be refactored. I'll
start doing this. If anyone's using the existing one, plan on seeing
some changes.
snip
From: Bruno Dumon
How would you propose to handle multi-page
forms?
Something like
hi:
Here is the answer. They are not running Cocoon.
Hi Antonio,
We run Tomcat 4.1.24, j2sdk1.4.0, Servlet 2.3.
We stoped to run cocoon.
Antonio Gallardo dijo:
Hi:
While surfing on the net I found this site that sell cocoon hosting
services... Anyone know about this company? Here is the
On Thursday, September 11, 2003, at 06:38 AM, David Crossley wrote:
I propose Antonio Gallardo and Tony Collen to be Cocoon committers.
They have both been contributing lots of stuff and discussion
on both cocoon-dev and cocoon-users since mid-2002.
Here is my +1 for both.
--David
+1
Nicola Ken Barozzi wrote:
Berin Loritsch wrote:
OOPS! Wrong list. My oppologies.
Actually, it's a pleasure to see Avalon growing again as a community :-D
PS: Is oppoligy a contraption for oops my apologies? Cool! ;-)
;P Not intentionally...
--
They that give up essential liberty to obtain
Glad to see support for multi-page forms is getting attention.
The separation of concerns between the form model and the form view
leads me to think the model should not need to know how the view is
split across multiple pages. For example, helpdesk-assisted forms
may present a view to the user
Maybe subforms should be interested here so that you can define a form
inside another form and then you can validate a specific subform. Ofcoz
keeping in mind that separation of concerns is not handled with this as
the form model has to know about the form view (which are here
subforms).
Gunter
--- Sylvain Wallez [EMAIL PROTECTED] wrote:
Quick answer on the union : I very much like it, and actually was about
proposing something similar. We just need to add datatype, label and all
the usual stuff to the union widget to allow automatic generation of
switchable panels (like in
From: Timothy Larson
Glad to see support for multi-page forms is getting attention.
The separation of concerns between the form model and the
form view leads me to think the model should not need to know
how the view is split across multiple pages. For example,
helpdesk-assisted
Hi!
I want to set the cocoon (jetty) working-directory to an not default
value (for example to my webapp-dir)
How is that possible?!?
Thanks for helping
Freddy
Frederic Gaus wrote:
Hi!
I want to set the cocoon (jetty) working-directory to an not default
value (for example to my webapp-dir)
How is that possible?!?
Two options:
1) Read and modify web.xml
2) Send email to cocoon-users and ask this question there
Dev list is not appropriate for such
--- Bruno Dumon [EMAIL PROTECTED] wrote:
On Thu, 2003-09-11 at 22:32, Timothy Larson wrote:
The wd:union switch can default to having no child widgets and later
switch to various sets of child widgets. Constrained only by the list of
cases in the union, you can dynamically decide which
I've found some odd little things about
Woody that may be features or bugs. Not sure which.
1) asserts only seem to work for equalities.
This works:
wd:assert
test=Quantity1=Quantity2 /
but this doesn't:
wd:assert
test=Quanty1 lt; 3 /
(OT: I wonder what happens when you
try to assert the
Timothy,
I've been thinking about this sort of
thing a lot. It mostly makes my head hurt...
Timothy Larson [EMAIL PROTECTED] wrote
on 09/12/2003 06:13:05 AM:
Glad to see support for multi-page forms is getting attention.
Ditto.
The separation of concerns between the form model and the
14 matches
Mail list logo
