In the Designer, the steps are fairly simple. You start by creating an EditorGridPanel. This new grid panel will come pre-canned with several columns and column editors (which are just form field components). You edit the existing columns or delete/create columns as needed, and you can attach the appropriate column editor to each column that you want to be editable. So if you want a text box to show up when editing, then you want to add a TextField. If you want a drop down when editing, add and configure a ComboBox. Etc.
Lastly, for grouping, you can add the GroupingView to the EditorGridPanel and configure it to group on a particular data attribute from your store records.
Let me know if that is enough information to get you started. Good luck!
Thanks Mihai, I have this ticket open and will get this fixed ASAP for the next release. Thanks for reporting it! It's ok that the view is placed under a column, that doesn't matter...but there is an issue with Ext JS itself in terms of rendering the component that didn't exist before, so I will get it resolved.
I'm going to have to remove the GroupingView in the next release until we release the custom Store configurations (where you can supply your own DataProxy, DataReader, and DataWriter configs). The GroupingView needs a GroupingStore to work (whoops!) and we don't support the GroupingStore at the moment, but we will when we allow for custom proxy, reader, and writer configurations against a generic Store or a GroupingStore. I'll try to prioritize this for a near future release.
Just curious... When can we expect to see the Grouping Store available in Designer? An IDEAL situation would have all the available features of EXTjs ready to use in the Designer.
Perfection as a goal is a nice idea that can point one in a specific direction. However, since "perfection" is an ever changing (evolving?) and moving target, one must admit that perfection can never be obtained...
When in doubt, check the d4mn source code!
And here are my terms...
I don't care if you use my source code. (Known as "Code.")
I don't care if I get any monetary compensation.
I do care to receive credit for Code provided. So, please keep my name in the comments for Code provided.
Code is provided without warranty "AS-IS" and I claim absolutely no warranty nor liability to the quality, security, and run-ability on any platform.
By using Code, you accept all risk inherit with Code regardless if Code has known and yet to be discovered bugs.
You are welcome to change and improve the Code to best meet your needs.
I don't care if you use the Code in a commercial or open-source project.
You are not required to contact me prior to using the Code.