Portal Engine Questions on portal engine and web parts.
Version 5.x > Portal Engine > Evaluating Kentico View modes: 
User avatar
Member
Member
tomlid - 4/27/2011 11:08:28 AM
   
Evaluating Kentico
Hi

Wasn't sure where to post this so hope this is the right place.

We are planning on developing a site that has as the home page a combined/merged display of various content types including Articles, Blog Posts, PR, Tweets, Facebook posts etc.

I like the look of Kentico very much and am trying to determine whether it would be technically feasible to combine "internal feeds" of content types and external feeds such as twitter into one filterable merged feed.

Oh, and more merged content will come asynchronously as the bottom of the page is reached.

It'd be great if anyone could help in verifying whether this requirement could be met by Kentico.

Thanks!

User avatar
Kentico Developer
Kentico Developer
kentico_helenag - 4/27/2011 2:46:05 PM
   
RE:Evaluating Kentico
Hi,


Regrettably, we do not have web parts which could support merging of different kinds of data sources (internal and external). I would recommend you developing a custom web part where you can get the Kentico documents by API, other sources by custom code and then merge the sources by standard ASP.NET methods and display it by ASP.NET controls.

The sample code of selecting documents by API: Selecting nodes


Best regards,
Helena Grulichova

User avatar
Member
Member
tomlid - 4/28/2011 2:56:50 AM
   
RE:Evaluating Kentico
OK, so it is feasible within Kentico as we're more than happy to develop custom code. Thanks for your advice.

User avatar
Kentico Developer
Kentico Developer
kentico_helenag - 4/28/2011 5:20:38 AM
   
RE:Evaluating Kentico
Hello,


one more advice: You can take a look at following example with UniView control:

//Create DataSet containing all menu item documents in the system
DataSet ds = TreeHelper.SelectNodes("/%", false, "CMS.MenuItem", "", "NodeLevel, NodeOrder", -1, true);


//Check that the DataSet isn't empty
if (!DataHelper.DataSourceIsEmpty(ds))
{
//Create GroupedDataSource from the ds DataSet
GroupedDataSource gpd = new GroupedDataSource(ds, "NodeParentID", "NodeLevel");

//Set RelationColumnID property of the UniView control
this.UniView1.RelationColumnID = "NodeID";

//Bind the DataSet to the UniView control
this.UniView1.DataSource = gpd;

this.UniView1.DataBind();
}

The SelectNodes method returns each document type in a separated table. If you convert it to GroupedDataSource, it will merge the document type tables. Similarly, you can convert any other dataset to GroupedDataSource.


Best regards,
Helena Grulichova