Hello,
First and foremost - great to see that Telerik is also providing this set of widgets. It looks as if we will certainly be interested in purchasing this.
I do have a question though for setting up a datagrid.
Our widgets are usually set up as html entities that have a specific class assigned to them, and have data attributes that we can interprete in javascript to set up the widget. this has one major and obvious advantage: we have 1 javascript file we include in the headers that contain ALL initialisation code.
So, our grid would look like this:
<table class="fx-grid"
data-datasource-url="json.php?blablabla"
> <!-- some code can go here still -->
</table>
And in javascript, we usually initialise everything as follows:
$('table.fx-grid').livequery(function() {
$(this)
.removeClass('fx-grid') // We do this to make sure this widget can only be selected and processed ONCE
.kendoGrid({
// configuration settings go here!
});
});
The major advantage is that when I retrieve a new grid through ajax to be displayed in a tab for instance, that ajax call won't need to send along additional javascript code, and we only need the html (the livequery plugin does just what we need: detect that new widget is added to the dom, and trigger the method...)
As you notice, we would need all settings as data- parameters defined so that in javascript, we can easily interprete them using $(this).attr('data-datasource-url') and pass them along to the kendoGrid feature.
I'm just not sure at this time what the minimal configuration is for setting up a remote datasource, and in what format we need to have json.php return the data. I've been looking at your examples, but I don't see what the minimal setup is you require.
First and foremost - great to see that Telerik is also providing this set of widgets. It looks as if we will certainly be interested in purchasing this.
I do have a question though for setting up a datagrid.
Our widgets are usually set up as html entities that have a specific class assigned to them, and have data attributes that we can interprete in javascript to set up the widget. this has one major and obvious advantage: we have 1 javascript file we include in the headers that contain ALL initialisation code.
So, our grid would look like this:
<table class="fx-grid"
data-datasource-url="json.php?blablabla"
> <!-- some code can go here still -->
</table>
And in javascript, we usually initialise everything as follows:
$('table.fx-grid').livequery(function() {
$(this)
.removeClass('fx-grid') // We do this to make sure this widget can only be selected and processed ONCE
.kendoGrid({
// configuration settings go here!
});
});
The major advantage is that when I retrieve a new grid through ajax to be displayed in a tab for instance, that ajax call won't need to send along additional javascript code, and we only need the html (the livequery plugin does just what we need: detect that new widget is added to the dom, and trigger the method...)
As you notice, we would need all settings as data- parameters defined so that in javascript, we can easily interprete them using $(this).attr('data-datasource-url') and pass them along to the kendoGrid feature.
I'm just not sure at this time what the minimal configuration is for setting up a remote datasource, and in what format we need to have json.php return the data. I've been looking at your examples, but I don't see what the minimal setup is you require.