dojox.grid.cells.NumberTextBox will be nice to have

[Marcin Gołębski]

It will be nice to have cellType which accepts only number, like dijit.form.NumberTextBox?

[Marcin Gołębski]

test for NumberTextBox?

[Nathan Toone]

Have you signed a cla?

[Marcin Gołębski]

Replying to toonetown:

Have you signed a cla?

No, I haven't. How can I do this? The second question: why milestone 1.5 not trunk?

[Marcin Gołębski]

Have you signed a cla?

No, I haven't. How can I do this?

OK, I know it. I will send it this weekend.

[Nathan Toone]

Replying to mgolebsk:

why milestone 1.5 not trunk?

Since we don't have a CLA yet from you, you said you'll get it in this weekend, but we are cutting the 1.4 beta this weekend...and no new features will be going in. I can get it into the trunk as soon as we release 1.4 (thus it will be available for 1.5).

Even if the CLA were in now, I am a bit wary of adding any new features this close to a release...so the change would still be in for 1.5.

[haysmark]

As the patch indicates, you can already do this with a _Widget cell+widgetClass=NumberTextBox? very compactly. You don't even need the get/setValue definitions because if you type something invalid, the NumberTextBox? just stays open.

[haysmark]

For instance, we have a CurrencyTextBox? declared in a grid structure that is simply:

{
name: 'Amount',
field: 'col5',
formatter: formatCurrency,
constraint: {currency: 'EUR'},
widgetClass: dijit.form.CurrencyTextBox
},

It seems overkill to add a separate NumberTextBox? definition given that CurrencyTextBox? works fine without its own definition.

[Marcin Gołębski]

Replying to haysmark:

As the patch indicates, you can already do this with a _Widget cell+widgetClass=NumberTextBox? very compactly. You don't even need the get/setValue definitions because if you type something invalid, the NumberTextBox? just stays open.

Two cases:

1. when NumberTextBox? cell you enter character then widget stays open until it deletes
2. when you enter out of ranges value and then pres enter - the new incorrect value will be send to the Store.

That's why get/setValue is necesary.

[Marcin Gołębski]

Replying to haysmark: It does not work when you use pure html grid definition, eg:

<th field="minH" editable="true" widgetClass="dijit.form.NumberTextBox" constraint="{min:0, max:9999999}">Min H</th>

the efect is simple edit cell which accespts all character.

[Marcin Gołębski]

patch which adds NumberTextBox?

[haysmark]

You're right, I looked at the source I pulled that from and what I posted was not the whole story. It turned out there was a defaultCell being set that was specifying type: dojox.grid.cells._Widget.

We have an example of creating such a cell in markup (although it is acting up ATM):

​http://archive.dojotoolkit.org/nightly/checkout/dojox/grid/tests/robot/_DataGrid.html

If you look at the source for that page, the equivalent HTML to what I posted above, with the defaultCell flattened into the definition, is:

<th cellType="dojox.grid.cells._Widget" widgetClass="dijit.form.CurrencyTextBox" field="col5" formatter="formatCurrency" constraint="{currency:'EUR'}" editable="true" width="8em" styles='text-align: right;'>Amount</th>

I would encourage you to try it. For the problem number 2 you were describing, that sounds like a bug with Grid using RangeBoundTextBox?, which we should fix for all widgets, not just this one.

[Marcin Gołębski]

Replying to mgolebsk:

Have you signed a cla?

I sent my cla on 28.10.2009.

[Marcin Gołębski]

Replying to haysmark:

<th cellType="dojox.grid.cells._Widget" widgetClass="dijit.form.CurrencyTextBox" field="col5" formatter="formatCurrency" constraint="{currency:'EUR'}" editable="true" width="8em" styles='text-align: right;'>Amount</th>

I would encourage you to try it.

Yes, it works fine.

For the problem number 2 you were describing, that sounds like a bug with Grid using RangeBoundTextBox?, which we should fix for all widgets, not just this one.

Maybe we shoud create another ticket for this issue and close this one?

[Nathan Toone]

Replying to mgolebsk:

Maybe we shoud create another ticket for this issue and close this one?

Yes - please open another ticket for that issue. I will close this one as worksforme since the original issue appears to be working now.