[eluser]Atasa[/eluser]
[quote author="suashi" date="1204389941"]I quickly tested your datagrid and let me say some words.
I prefer using base_url() and site_url() functions provided by CI's URL helper so you have url consistency among your application;
[/quote]
That's a really small thing you change it any time and I agree.
[quote author="suashi" date="1204389941"]the curious thing is that the current datagrid in CRUD lib is done the same way, except for pagination which will be implemented. It relies on CI's Table class to easily create tables from arrays, and the data that CRUD interprets is: the fields name (if not overridden) for the table headings, and the fields values for the rows, plus an additional column for all the operations links as Edit, Delete....
What I would like to see is an implementation of a more functional datagrid in CRUD and keep pumping this library!
Btw thanks for your contribution! I appreciate it!
see ya![/quote]
Can you explain what do you mean by "more functional datagrid"?
Perhaps Ajax enabled table.
Because a datagrid is a datagrid.
I thing we have a disagreement here.
I don't see any datagrid in your crud.
You have a general library that does all the operations together difficult to find out which function calls which and then calls another etc.
After some point you get completely lost (I least I do).
To tell you the truth I haven't even looked before in your library code.
And I haven't done it because as a said from my very first post that I like to create a model
for what you do in your library perhaps, and of course in the example code, I used the CI table class there no other as far as I know.
More over, the edit delete functions also have to pass to the datagrid library to display them,
because this library is not aware if you want to display data with edit delete functions
or just to display them.
As for the next post I agree up to a certain point for what you said about JavaScript.
It is a long issue I thing and didn't express myself the right way.
Cheers