Subject | Architecture of FB/IBO application |
---|---|
Author | L.M. Bemmelmans |
Post date | 2003-07-24T17:16:45Z |
Ok,
To make a better start a few architecture questions to FB/IBO applications
1.
Is it wise to show buttons where users can submit (commit) their changes, or
must I allways hide this from my users
The examples of Jason are very clear, but only because you can manipulate
behaviour with the supported buttons
2.
If it's not wise to show buttons. when do we commit (considering user-entry
+ browsing)
3.
While editing transactions could stay open a long while. You can prompt
users to commit (but do they have to know about committing ?)
but if they don't......
I wonder how you guys build applications with IBO.
Loading everything into memory and using FB only as datadump is a
possibility but that's not what I mean.
Leon
To make a better start a few architecture questions to FB/IBO applications
1.
Is it wise to show buttons where users can submit (commit) their changes, or
must I allways hide this from my users
The examples of Jason are very clear, but only because you can manipulate
behaviour with the supported buttons
2.
If it's not wise to show buttons. when do we commit (considering user-entry
+ browsing)
3.
While editing transactions could stay open a long while. You can prompt
users to commit (but do they have to know about committing ?)
but if they don't......
I wonder how you guys build applications with IBO.
Loading everything into memory and using FB only as datadump is a
possibility but that's not what I mean.
Leon