Am 2006-06-08 um 15:09 schrieb Ed Leafe:
1. An intro to "a typical Dabo app" (i.e. small but not trivial app)
(maybe two - a db one and a non-db one)
i.e. something like the simpleDemo apps, but explaining which
parts are "boilerplate" and which are expected to vary.
That was my intent when I created the screencast and Wiki HowTo
page on populating a grid with data:
<http://dabodev.com/wiki/
HowToCreateAFormWithAGridAndPopulateItWithData>
This was the result of a post here asking that exact question, and
I thought that this was an excellent topic to illustrate. Is this
the sort of scope that you had in mind? Or could you perhaps
suggest a different sort of app, along with the sorts of
capabilities it should have?
I like AppWizard, because its results are 80% of what I need.
But without knowing dabo in detail I can't work with the created
files to get the other 20%.
Thus I'd very much appreciate an explanation of the Wizard created
structure and where to place the wrench to get further.
e.g.
- how can I limit some text entry to e.g. numbers or lowercase letters
- how can I cope with MySQL enum or set fields
- how can I set a field readonly
- can I simply omit a field from a form if I want to get the default
(or old) value
- how do I get a foreign key selection (dropdown list with entries
from another table)
- how do I get the index number of a new entry
- the same fields and labels appear in at least 3 forms; wouldn't it
make sense to change AppWizard so that one must change only one
place? (e.g. to localize labels)
Sure! Got some in mind? The hard part is coming up with an example
that would be instructive. The easy part is writing the code!
Perhaps my suggestions make sense?
Sorry for being of no help myself.
Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net
http://www.cacert.org (I'm an assurer)
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
