Hi , im currently designing the architecture of my coming grid for .net
and i just want to ask all of you what grid (for .net or whatever) that you think is the best and easiest to use
my current implementation is beginning to resemble the infragistics ultrawingrid ,
but if any of you have any suggestions or would like to beta test the grid when it gets that far , please reply here or email me at roger.johansson[at]compona.com
//Roger

Making a .net Grid
SabTimur
http://www.compona.com/themes.gif
//Roger
ricardocsouza
bodyman
Len Weltman
http://www.compona.com/newgrid.jpg
it now supports binding to datatable,dataview,dataset,IList,IBindingList,IEnumerable,IListSource
we still need beta testers..
Zan_
Peso
what do you guys think would be the best solution
1) using custom formatting objects that are set in designtime
or
2) simply raising an event before the row is rendered and let the developer apply any formatting to the row or its cells
i personally think the 2nd alternative would be the far most dynamic way to go , that would allow you to write true logic for the formatting and you wouldnt be locked to the limitations of any predefined formatting object...
any suggestions
//Roger
George Jordanov Ivanov
the grid alpha version of the grid can be found at:
http://www.compona.com/alphaalphagrid.zip
NOTE:
this sample uses the xp theme painter only! , if your not on xp you will not be able to see some of the visual elements...
but as i said , its an alpha release so the following stuff is not yet implemented:
EDITING!
selections (only 1 row can be selected right now)
column resizing/row resizing
summary/footer values (currently empty cells)
databinding can currently only handle hierarchies for datasets.
i hope to have the editing and resizing working till next week.
//Roger
Mathew Ong
1. Try to make any cell and column headers contain images and allow them to align it accordingly.
2. Have an AutoSize facility that binds the width of the cell to its contents.
3. Simplify the object library used to manipulate the grid control to display contents.
4. Make the control light weight so that it does not have a big memory signature.
5. Make available many controls that can be used as both cell value viewers and editors.
6. Add effiecient and effective validation event handlers for the grid cells.
7. Make the insertion, modification and deletion functionality easy to use and very accessible.
8. Have very simple grid customisation functions that reduce coding overheads.
9. If possible create a grid designer that can make the grid, easy to be setup in the design time.
I know I am asking for the stars. But again, these are just suggetions that can or cannot be implemented. Try to make it better and unique. All the best
Manas
http://www.compona.com/WikiEngine/WikiPageViewer.ascx ID=48
shots can be seen at:
http://www.compona.com/treegrid.gif
http://www.compona.com/standardgrid.gif
http://www.compona.com/standardcolors.gif
http://www.compona.com/summaryrows.gif
to refer to your post:
1. NO HORIZONTAL SCROLLING (like the Outlook or the Netscape grids)
ok , we dont support this yet but i guess it would be fairly easy to implement this..
2. Customizable Columns (change order or add/remove columns from a palette)
columns can be reordered / shown/hidden via code right now.
support for rearranging is coming (the gird is currently in alpha stage)
3. OwnerDraw on Rows & Columns
the grid currently supports custom painters that allow you to customize the entire drawing process of the grid (per band/table)
we will add customdrawing to , so you wont have to create a complete renderer.
4. Visual Style Support on XP
coming very soon , we are almost finnished wrapping the xp themes dll...
other ideas are also very welcome :)
//Roger
malconium
1. NO HORIZONTAL SCROLLING (like the Outlook or the Netscape grids)
2. Customizable Columns (change order or add/remove columns from a palette)
3. OwnerDraw on Rows & Columns
4. Visual Style Support on XP
All the grids I've tried are not only rather expensive for small projects, but are either missing some key feature, have excessive runtime sizes (requiring large downloads for my users), are memory hogs, or are just too darn hard to use.