Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Open Core Testi...Open Core Testi...Why use Telerik in DNN 6 instead of JQuery?Why use Telerik in DNN 6 instead of JQuery?
Previous
 
Next
New Post
4/23/2011 4:01 PM
 
First of all thanks to everyone for the hard work being put into DNN 6 :)

I am just wondering why DNN is choosing to use Telerik instead of JQuery in DNN 6?

If DNN are serious about attracting more people to use DNN then it seems to me that JQuery would be better to use for popup windows, tooltips, editors, validation, grids etc.. as JQuery is already used millions of websites around the world compared to Telerik which may be lucky to have just thousands of developers.

DNN 6 has moved from vb to c# as there are more c# developers in the world yet they have now chosen to use Telerik over JQuery?? This does not make sense to me as there are many more millions of developers & designers who are already familiar with JQuery.

Apart from having to maintain yet another framework, adding further unneeded bloat to the DNN framework & causing unnecessary upgrade issues I cannot see why Telerik is being used in the new UI overhaul.

Another very important point to remember is that as far as I am aware (please correct me if I am wrong), because  the Telerik controls are server side controls, skin designers, website administrators, xmod users, openwebstudio users, form & list users, ventrain new article users etc.. will not be able to do things like match the new core form patters & ui design as all these will have been created using server side controls.

For example: a website administrator will not to be able to edit a standard HTML module have a picture or group of pictures open in pop windows that look the same as the new core UI as the core UI will use server side controls (Telerik Rad Window). If the core UI was using a JQuery solution like "JQuery UI" or "ColorBox" then both backend & frontend designs/developers could use the same code & keep a clean consistent UI throughout the platform.

Designers & developers need to work together, using JQuery instead of Telerik will help make this happen!
 
New Post
4/24/2011 12:27 AM
 
Adam

DNN Corp supports both Telerik and jQuery. jQuery is great - 100% agreed with you, but Telerik has a lot of great controls and it allows to build modules much more faster then the same with jQuery. But again - its up to developer. He selects what to use.

Sergey

PS: Probably its another holywar, the same like VB and C# 
 
New Post
4/24/2011 5:32 AM
 
DNN 6 will also support JQuery UI, i.e. developers have full choice of controls to use. All Telerik controls will be included using "wrappers", i.e. DNN controls containing the Telerik controls, which may be freely used by any extension developers as well, some will simply replace existing asp.net controls in the framework. The benefit of Telerik is a much better productivity, once a developer learned to use it.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
4/24/2011 6:53 AM
 
I think you guys are missing my point.

The idea of having form patterns & core UI design guides should be something that EVERYONE is able to stick to. Module developers, portal administrators, skin designers ect.. all  should be able to create a form in a popup window that looks & works exactly the same.

Using Telerik controls may be faster initially but it will draw another line in the sand between module developers & everyone else.
 
New Post
4/24/2011 7:35 AM
 

Adam,
Both jQuery and Telerik have their uses and serve very different needs.  Not all module developers will be comfortable with client-side development and will feel a lot more comfortable with tools like Telerik.  Other developers are looking for a very lean development platform and prefer the use jQuery for much of the heavy lifting.  This is not an exact science and we are still drawing up guidelines to help our own developers understand when it is appropriate to use each tool.

The other added constraint is that we don't want to deploy 100 different tools and licenses with DotNetNuke, we need a couple of tools which we can rely on to meet 99% of our needs.  jQuery is great because of the availability of plugins, but the reality is that we have to be very selective about the tools we choose to include with the platform because people will come to rely on it, and if it is not flexible enough, or have a solid team behind it, we could quickly find ourselves with an orphaned plugin.

Finally, just because a feature is implemented a specific way in the CTP does not mean that it will be implemented the same way in the final release.  We implemented the original popups using Telerik, created a version using pure jQuery, another version using jQueryTools and finally settled on a version using jQueryUI which you'll see in CTP 3.  At each step of the way, we identified behavior that we liked, behavior we didn't like and behavior which we felt was crucial to getting the feature just right.  There is still some work to be done in this area, but as you'll see in the upcoming CTP 3, the popup implementation has changed quite a bit and the behavior has been cleaned up a little (although still not in its final form).


Joe Brinkman
DNN Corp.
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Open Core Testi...Open Core Testi...Why use Telerik in DNN 6 instead of JQuery?Why use Telerik in DNN 6 instead of JQuery?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out