es. :)
Antonio Gallardo.
>
> A very interesting discussion.
>
> --Michael
>
>
>
>
> "Antonio Gallardo" <[EMAIL PROTECTED]>
> 07/30/03 02:02 AM
> Please respond to
> [EMAIL PROTECTED]
>
>
> To
> <[EMAIL PROTECTED]>
> cc
>
>
Marc Portier dijo:
>
>
> Antonio Gallardo wrote:
>> Marc Portier dijo:
>>
>>>I can't see a need for a field that should be 'calculated
>>>automatically' AND be editable at the same time.
>>>(I tried though)
>>
>> It sometimes happens, for example here in my country, in a restaurant
>> invoice is a
of the forms we process.
A very interesting discussion.
--Michael
"Antonio Gallardo"
<[EMAIL PROTECTED]>
07/30/03 02:02 AM
Please respond to
[EMAIL PROTECTED]
To
<[EMAIL PROTECTED]>
cc
Subject
Re: [RT] Woody and round
trip of parameters.
Marc Porti
Marc Portier <[EMAIL PROTECTED]> writes:
>
> Hunsberger, Peter wrote:
> > Marc Portier <[EMAIL PROTECTED]> asks:
> >
> >>I can't see a need for a field that should be 'calculated
> >>automatically' AND be editable at the same time.
> >>(I tried though)
> >>
> >>>Thoughts ?
> >
> > We have a cou
Hunsberger, Peter wrote:
Marc Portier <[EMAIL PROTECTED]> asks:
I can't see a need for a field that should be 'calculated
automatically' AND be editable at the same time.
(I tried though)
Thoughts ?
We have a couple of weak use cases for this:
1) Normally a medical protocol phase might ta
Marc Portier <[EMAIL PROTECTED]> asks:
> I can't see a need for a field that should be 'calculated
> automatically' AND be editable at the same time.
> (I tried though)
>
> > Thoughts ?
>
We have a couple of weak use cases for this:
1) Normally a medical protocol phase might take 14 days, ho
Antonio Gallardo wrote:
Marc Portier dijo:
I can't see a need for a field that should be 'calculated
automatically' AND be editable at the same time.
(I tried though)
It sometimes happens, for example here in my country, in a restaurant
invoice is a non written rule to pay 10% of the subtotal to
Marc Portier dijo:
> I can't see a need for a field that should be 'calculated
> automatically' AND be editable at the same time.
> (I tried though)
It sometimes happens, for example here in my country, in a restaurant
invoice is a non written rule to pay 10% of the subtotal to people that
serviced
Sylvain Wallez wrote:
Antonio Gallardo wrote:
Marc Portier dijo:
some attempt/proposal:
definition-model declares field:
case A: nothing special -> defaults to read-write
case B: as being read-only
case C: specific as read-write
binding declared on field
case 1: nothing special -> defaults
Antonio Gallardo wrote:
Marc Portier dijo:
some attempt/proposal:
definition-model declares field:
case A: nothing special -> defaults to read-write
case B: as being read-only
case C: specific as read-write
binding declared on field
case 1: nothing special -> defaults to inherited from the fi
Antonio Gallardo wrote:
Marc Portier dijo:
some attempt/proposal:
definition-model declares field:
case A: nothing special -> defaults to read-write
case B: as being read-only
case C: specific as read-write
binding declared on field
case 1: nothing special -> defaults to inherited from the fie
Marc Portier dijo:
> some attempt/proposal:
> definition-model declares field:
> case A: nothing special -> defaults to read-write
> case B: as being read-only
> case C: specific as read-write
>
> binding declared on field
> case 1: nothing special -> defaults to inherited from the field
> defini
Sylvain Wallez dijo:
> I guess Antonio is talking about computed fields. For example, the
> "subtotal" above is the sum of all "amount" fields. Amounts are
> read-only, and subtotal is a fake field that has no binding to the
> application data model.
Yep. This is the idea. Also note this type of f
Bruno Dumon dijo:
> On Tue, 2003-07-29 at 15:07, Antonio Gallardo wrote:
>> Hi:
>>
>> I had a concern about how to manage parameters that are flying between
>> the server and the client.
>>
>> It will worth if we have an attribute in the form that define when we
>> are waiting or not for a paramete
Sylvain Wallez wrote:
Bruno Dumon wrote:
I guess Antonio is talking about computed fields. For example, the
"subtotal" above is the sum of all "amount" fields. Amounts are
read-only, and subtotal is a fake field that has no binding to the
application data model.
I'm wondering if "read-only
Bruno Dumon wrote:
On Tue, 2003-07-29 at 15:07, Antonio Gallardo wrote:
Hi:
I had a concern about how to manage parameters that are flying between the
server and the client.
It will worth if we have an attribute in the form that define when we are
waiting or not for a parameter back from the u
On Tue, 2003-07-29 at 15:07, Antonio Gallardo wrote:
> Hi:
>
> I had a concern about how to manage parameters that are flying between the
> server and the client.
>
> It will worth if we have an attribute in the form that define when we are
> waiting or not for a parameter back from the user?
do
Hi:
I had a concern about how to manage parameters that are flying between the
server and the client.
It will worth if we have an attribute in the form that define when we are
waiting or not for a parameter back from the user?
I know woody has some formulas, I was not full review woody. :)
I wa
18 matches
Mail list logo
