From: Andreas A. <a.a...@th...> - 2001-08-16 09:50:32
|
Hi Alex, > > 2. i noticed <maxlength> which i can forsee being used for setting a > > maxlength in a input field (HTML), and for possibly determining the > > field length in the database. (is this correct?) BUT, there was no > > Correct on both accounts. > > > LENGTH value anywhere. if HTML forms are to be built on the entities, > > having a MAXLENGTH as well as a LENGTH would be desired. > > Yes, I see your point. I was toying with the idea of associating > UI controls with each field type. That may still happen, so: > <!-- look here --> > <uicontrol> > <name>TextField</name> > <params> > <length>20</length> > </params> > </uicontrol> > </field> Hmm. But isn't that markup stuff something for the template engine/up to the designer? I'm not quite sure if integrating the UI stuff with the entities is wise or not. Imagine you use the size/length attribute of an input field within more contextes. So you have a from_a with size="20" is fine, in form_b using the same entitiy size="20" does not fit, you need size="40" in form_c you need style="width: 80px" and the so on... Ok, maybe you can override this in the template and the etydef values are defaults or whatever. Anyway, I think markup stuff does not belong here. > > 3. could you explain a field PATH a bit? > path is sort of like the way you ref a table.field_name in sql: > location.locationid is an entity path that points to a field in an entity. > it could also be a sql table_name.field_name path - it's intentionally > similar. Extremely nice. <required> Antoher question. Does the <required /> tag mean "not null" in the database only or with the form? I think this should not be combined, caus there are applications you have the db-field defined "not null" (requried) but no input value coming from the ui whatever, not required or not present. </required> Andi |