Hi @bouks,

sorry for the late answer, but I have other things to do in New Year. :-)

`defaultValue` of `"integer"` or `"number"`, `"currency"` formatters can be defined in `formatoptions`. If no such property are specified in `formatoptions` then the values from the language file (`grid.locale-en.js` for example) will be used (see [the lines](https://github.com/tonytomov/jqGrid/blob/v4.7.0/js/i18n/grid.locale-en.js#L97-L99)). So in case of empty string as the input data the currency and the number formatter will produce `0.00` string and the integer formatter will produce `0` string instead.

Now about "the goal". I don't think that removing such small code duplicates like in the above example should be the first step of "new jqGrid". If we start with such modifications in the way we could include a lot of side effects and new bugs in the code. The benefit of such changes for the end user (the developer who use jqGrid) will be reduced to 0 because of a lot of compatibility problems which he have to solve.

jqGrid have **many bugs which need be fixed**. It have **many small design problems**. One can include some small but nice new features which the users could good use. *Such changes* could be be interesting for the users of jqGrid. Look at [the change list](https://github.com/OlegKi/jqGrid/commits/master) which I posed in my fork of repository. The changes fixed many existing problems which I know.

It could be very simple and small changes which can be helpful for the users. For example one can change default values of some jqGrid parameters. I posted Tony the corresponding suggestions many times, but he had another opinion on the subject. One can set `gridview: true` and `autoencode: true` as default options of jqGrid. One can change default value of `rowNum` property from `20` to for example `10000` if the user don't specified neither `pager` option not `toppager: true` option. If you create grid now with 50 items of data and no pager then jqGrid will display the first 20 rows and the user will have no pager to see the next rows.

What I try to say is that one can *improve* jqGrid not just reformatting of the code or by reducing the size of JS file. One can provide new features and to fix existing problems. It could be the main goal of development of jqGrid in my opinion.

Do you see some features which would be good to implement as the first? Do you know some bugs which need be fixed?

Best regards
Oleg