El 14/08/13 09:44, Paul McNett escribió:
On 8/9/13 12:39 PM, Ricardo Aráoz wrote:
- within a form we are supposed to work with data through the Form's methods
and not
the bizobj. But dForm.new() will not take the parameters dBizobj.new() will
take. In
particular I've found no way to set field values from Form's methods after a
dForm.new(), if I have to go down to the Bizobj so as to do that then I'd
rather not
bother with the form's methods at all, consistency would dictate to always use
the
bizobj.
We should add that ability to dForm.new(). Personally, I prefer interacting with
bizobjs directly and not usually going through the form methods.
- dForm.deleteAll() will always ask if the user is sure, it's not the user but
the
programmer who is sometimes issuing this method. There is a "message" parameter
set
to None by default which should prevent any messages but it is not working this
way.
Had to go down to dBizobj.deleteAll() to be able to not get the confirmation
message
popping up.
In my mind the form methods are there to be convenient for quick development,
and the
bizobj methods are closer to the metal and will have more options.
But isn't that going against the three tier concept?
I thought the idea was that the control (let's say a button) interacted
with the form, then the form interacted with the biz and finally the biz
with the db.
Or am I getting it wrong.... again ;c)
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/[email protected]