Monday, 26 September 2011

RadDock vs WebParts comparison list

To compare RadDock and Webparts, I did some research and I found few points that
can help you taking decision which control to use either RadDoc or WebParts. Both provides you user personalization experience. Below are my listings:

Features of Webparts and RadDock

WebParts provide the following features out of the box:

  • Adding new WebParts to the page

  • Editing the content of a WebPart

  • Binding WebParts

These features are not built-in within the RadDock control but can be easily implemented.

RadDock provides:

  • [Live] resize functionality

  • Rich client-side API

  • Animations

  • Smooth drag and drop

  • Cross-browser compatibility

  • 13 built-in Skins

Ease of development

RadDock allows developers to create dynamic pages, the content of which can be personalized
by end users, and then the changes are saved and later restored to the last state.
Inbuilt features are available to support the rapid development and can be customized
as per the requirements. Built-in skin and CSS support.

Save state in cookies for statically created RadDocks.
Dynamically add or delete RadDocks via Ajax and save their state in the session

Microsoft WebParts allow developers to easily create a portal, i.e. they represent
the parts for creating and personalizing page layouts, contributing content, uploading
documents, etc. - things related to portals. Webparts has to be designed from scratch
but can be built in separate DLL and installed in the GAC to reuse across applications.
Creation of webpart and Adding skin/css requires work from scratch and provide high
level of customization.

Personalization

Available Features:
Asp.net Webparts allows the personalization with two types of control:

Shared control: - An authorized user can personalize both Shared and User scoped
properties on the control for all users. In the case of a dynamic control (a control
that is added to the page programmatically, or from a catalog of controls), an authorized
user can permanently delete it for all users. In the case of a static control (a
control that is declared in the markup of an .aspx page), it cannot be deleted,
although an authorized user can close the control for all users.

Per-User control: - The control cannot be personalized with the page in Shared scope,
because the control does not even appear on the page. The control only appears when
the page is in User scope.

RadDock controls are always in shared mode and allow all users to interact. But
you can customize them to persist/Not-persist the changes in layout state as per
the user.

Ease of Customization:

For custom personalization you need to create a custom provider class in Asp.net
WebParts. WebPartPersonalization class Implements the logic necessary to carry out
personalization actions.

Customization of the RadDock would be much easier as more focus would be on logic
rather than the look n feel. RadDock allow saving/loading of layout so no need to
create custom provider.

Pros and Cons
  • The biggest drawback of webparts is that it does not open the properties section
    inside the webpart. Instead, it opens in a zone on the main screen.

  • An even bigger drawback of WebParts is that you can't edit the properties while
    in catalog view. To switch between the two, you need to do a postback.

  • For RADDOCK there’s no need to implement any provider. Instead it requires customizing
    the scope and persistence of user’s layout.

  • WebParts work only when in admin mode.

  • Webparts are using the table layout which itself seems problematic in some cases.

References:

http://demos.telerik.com/aspnet-ajax/dock/examples/myportal/defaultcs.aspx

http://msdn.microsoft.com/en-us/library/z36h8be9.aspx">
http://www.telerik.com/community/forums/aspnet-ajax/docking/comparison-with-the-asp-net-web-part-framework.aspx

http://www.telerik.com/community/forums/aspnet-ajax/docking/comparison-with-the-asp-net-web-part-framework.aspx

No comments:

Post a Comment