Hi Simone,
I didn't read this mail until now, it was somehow hidden. comments below...
Simone Gianni escribió:
Hi Antonio,
thanks a lot :)
Just a few notes :
- What's the locale of cocoon.zones.apache.org ? Field formatting
currency displays a strange symbol
Yes, I noted the same error in
Hi Antonio,
thanks a lot :)
Just a few notes :
- What's the locale of cocoon.zones.apache.org ? Field formatting
currency displays a strange symbol
- Please note that VAT calculation is somewhat floppy due to floating
point division in xreporter expressions, which is still an open issue
Hi all,
I've finished my (long) work on calculated fields. I think I managed to
fulfill main goals :
- Only xreporter expressions and javascript are used
- The grammar is the one Antonio proposed, with really minimal variations
- All calculations are event based, as Sylvain explained
Hi Simone,
Simone Gianni escribió:
snip_of_great_stuff/
Please let me know what you think about it!
I ran the demo [1] and it is super ultra great!
You need to be in the cocoon hero plate! ;-)
Best Regards,
Antonio Gallardo.
[1]
it from a wider point of view, since it's a feature I'm
missing not only in calculated fields but in cocoon forms in general.
If we agree in trying this roadmap, i will produce something for
tomorrow. We can then fine tune it or drop it if we think it's not a
good idea.
WDYT?
Simone
, Field3: each have a range 0..3
TotalScore =
if (empty(Field1) || empty(Field2) || empty(Field3)) {
sum(Field1, Field2, Field3)
}
else {
score undefined
}
So two additions:
- use calculated fields for all widgets, rather than just repeaters
- allow a more flexible way of expressing
Hi Antonio,
fd:value eval=sum(articles.items)/
...
fd:value eval=sum(articles.items*articles.price)/
...
fd:value eval=sum(articles.subtotal)/
This is a very nice syntax!! However this way we are binding the system
to a language. This creates a number of problems :
- What language is it? We
of the fields are set to a value. Example:
Field1, Field2, Field3: each have a range 0..3
TotalScore =
if (empty(Field1) || empty(Field2) || empty(Field3)) {
sum(Field1, Field2, Field3)
}
else {
score undefined
}
So two additions:
- use calculated fields for all widgets, rather than just repeaters
Simone Gianni wrote:
Hi all,
what about calculated fields? In a cocoon form I have a repeater, in
the repeater there are some numeric fields, and i need to show the sum
of values in these fields at the bottom of the page. This can be done
with fd:value-changed and some javascript or custom
es it has finished parsing values (and validating
them) :
... check if the recalculate flag is set
... in that case call the algorithm
... clear the recalculate flag
- Also, since an algorithm may also need values from other calculated
fields
... in getValue(), if the recalculate flag is set, call the algo
On 10.04.2006 14:38, Simone Gianni wrote:
Yikes! Heavy FS smell!
FS? Fun Stuff? Free Style? Fiancial Service? :)
Flexibility Syndrome aka Featuritis.
Jörg
(and
validating them) :
... check if the recalculate flag is set
... in that case call the algorithm
... clear the recalculate flag
- Also, since an algorithm may also need values from other calculated
fields
... in getValue(), if the recalculate flag is set, call the algorithm.
... also use
relatively
useless with current great AJAX support. I think it was written in the
Jira issue because at that time Ajax was still far.
AFAIK, calculated fields main task is inform the user. In other way, if
we don't need to inform the webapp user about the subtotal, taxes
amount in a currency and so
Hi all,
what about calculated fields? In a cocoon form I have a repeater, in the
repeater there are some numeric fields, and i need to show the sum of
values in these fields at the bottom of the page. This can be done with
fd:value-changed and some javascript or custom classes, but actually
Hi Simone,
Thanks for taking care of this old but very important issue. Please see
comment below...
Simone Gianni escribió:
Hi all,
what about calculated fields? In a cocoon form I have a repeater, in
the repeater there are some numeric fields, and i need to show the sum
of values
/show_bug.cgi?id=25298
[EMAIL PROTECTED] changed:
What|Removed |Added
Summary|Calculated fields |[Roadmap] Calculated fields
--
Configure bugmail: http
/show_bug.cgi?id=25298
Calculated fields
--- Additional Comments From [EMAIL PROTECTED] 2004-02-12 01:54 ---
At what level we will implement it? At server side or at client side?
AFAIK, calculated fields are more important in client side to show results of
some calculations to users
/show_bug.cgi?id=25298
Calculated fields
Summary: Calculated fields
Product: Cocoon 2
Version: Current CVS 2.1
Platform: Other
OS/Version: Other
Status: NEW
Severity: Enhancement
Priority: Other
Component
18 matches
Mail list logo
