Sorry if my comment sounded harsh, it wasn't meant to be.
What I wanted to say was:
I'm new to codeIgniter/groceryCRUD, so I'm trying to figure my way around the customization part of both frameworks, CI is pretty straightforward, groceryCRUD requires a bit more learning, but I really think it's worth it.
Now while trying to do the task that motivated this thread, I admit I got bit scared... I look at this +1000 lines css file for grocey's flexigrid theme and my jaw fell...I haven't seen nothing like that since the 'old days of sharepoint 2007...of course that the classes that count are the ones called on each template (list/view), but it's still scary for a newbie!
While the themeroller seems like a very reasonable option (I'll certainly have to give it a go on the datagrid theme), doing a manual replace of all the .css seems a bit backwards for a tool that is so easy and so effective to use. You get a full CRUD with "extras" with like 5 min worth of code with grocery, on my book thats really good!
So, I guess I was expecting that being grocery such a powerfull tool, maybe there was a more...streamlined way to customize the flexigrid theme, or even a "vanilla" version of both templates(list, view) with some (or all) of the javascript functionality.
If I understood your suggestions correctly, the current scenario on the flexigrid leaves only two courses of action available: if one is going for full customization, we can "almost" trash the full css set and make some new ones from scratch (could be faster than browsing the css file?), on the other hand if one only wishes to do minimal costumization (basic stuff such as colours and fonts for instance), we'll have to identify and replace the required css classes. I'm thinking correctly? I'm sorry if this sounds a bit daft, but I'm trying to get a real take on the complexities of this process.
Oh, also, I'm interpreting the usage of both themes (datagrid/flexigrid) by the "old" VB definition: datagrid for "non-editable"/recordset bound data, flexigrid for all sorts of "editable" data (recordset bound and inputed on the table), is this somewhat correct? Or is it really just a matter of look and feel?