View Full Version : Why change width to inputWidth in v4?

26 Feb 2013, 1:33 PM
Our previous v3 app used a largely uniform width on all form fields - some fields were smaller of course where it made sense based on the likely user input - and we made better use of space by making occasional small changes to label width in some windows to ensure everything fit nicely.

Now in v4 the width config option determines the total width of the form field. Why is this annoying?

1. inputWidth isn't actually in the docs, meaning we wasted time finding out about it.
2. we have to change *thousands* of config settings across the app
3. we now have no sure way of telling the app that this field should be 400 wide as inputWidth is not universally adopted. For example, a fieldcontainer has no inputWidth we can use so we have to individually size form fields.

So what was the justification? Was it anything other than trying to unify Ext and Touch nomenclature?

26 Feb 2013, 4:03 PM
The fields changed in V4 to a hbox layout. It was then only a width that was available along labelWidth to calc the width of the input as a delta. We then added inputWidth.


15 Mar 2013, 12:55 AM
Also noticed that in v3 if I declared width = 400, that's the width I would get.

In v4, declaring inputWidth = 400 results in an internal width of 400 plus any padding your theme applies to x-form-field

This makes it extremely annoying to get all fields exactly the same size.

Screenshots attached show the exact same field in v3 and v4 with the same structural css applied. Note the differences.