Great!

Saki,

It's looking great!

The project I am working on is using that kind of editor grid panel with add,delete,edit buttons.
Also, I have at least 30 of those grids. It would be possible to combine with DynamicJsonReader and DynamicColumnModel, so that I don't need to rewrite the codes 30 times?

Saki some remarks, I thing will be good to have a toolbar with buttons Save, Save and Close, Delete, Cancel, Next(go to next record), Previous(go to previous record) ect I mean using toolbar you have more options, other thing will be good to get the difference (I mean only fields modified) from the original records, with its fields modified when the user click save, I can do a xml and send it to server, parser it and updatedatabase.

Other, trouble I think when the form need Fieldset, (I think it will be good to simple form) when the layout is complicate (column, fieldset ect could be hard)

Frank, I'm not sure if I'm willing to go in the direction of adding features. Because: 1) it just complicates code and makes it more bug prone and, more important, 2) I do not want to throw to user tons of buttons and toolbars he may never need (like e.g. M$ Word).

I'm neither planning to go in the direction of some custom layouts (e.g. Fieldsets). If users needs them they have to design their own forms with all the bells and whistles they want.

This should stay simple and straightforward: Plug it into an any grid, even auto-configured and get form access to fields both from column model (displayed in the grid) and store (not in column model).