ok. i doubt we would actually end up using the scale property in the EHR anyway. i think exploring ext column layouts is probably a better option for us.

your suggestion about using editor types is a good one. that would fit well with the idea of using something like .getFieldEditor(), as a standardized way to create the right component.

one idea i mentioned to mark that i'll repeat here is that it'd be very powerful if we could specify an xtype for each field in the table metadata. this way we could easily load highly tailored components and make them consistent across labkey. some of these might even be fairly generic, like using a slightly different date/time editor instead of always using a date editor.

It's worth noting that while labkey supports datetime fields, the corresponding editor is date-only. Below is a link to a simple datetime component I found on ext forums. this is the cleanest one i could find, although perhaps there are others.

http://extjs.eu/docs/?class=Ext.ux.form.DateTime

The above one makes a composite field with a date picks next to a time picker. I also have a different version in which the calendar panel has a time select above it (which might be more appropriate for a grid).