Small width layout Medium width layout Maximum width layout Small text Medium text Large text
     Search
Downloads Downloads Directory Directory Forums Forums Forge Forge Blogs Blogs        Marketplace Marketplace Careers Program Careers
Products › Development › Forge › Core - WebControls Register  |  

 

dnn_ct_webcontrols_170x64.gif

 

  Quick Links  
 


  Team Leadership  

Jon Henning

jonhenning.jpg

 


  DotNetNuke Projects  
The DotNetNuke Projects are a special category of platform extensions which are developed by volunteers to conform to the high professional standards mandated by DotNetNuke Corporation. The DotNetNuke Projects are distributed as a standard part of the DotNetNuke core application release offerings.

 


PortalWebHosting
  Ads  
Indoo
 


  Sponsors  

Meet Our Sponsors

CrystalTech Web Hosting™
Webhost4life, specialists in DNN hosting
Mad Development is a full service interactive agency focusing on the merge of design, technology, e-commerce, and affiliate marketing by providing total website solutions.
MadCap Software, Inc.
AspDotNetStoreFront - E-Commerce by Design - The Leading ASP.NET shopping cart platform for developers!
Click here to go to dev.live.com for Windows Live developer resources
 


DotNetNuke® Project :: WebControls

The primary purpose of the DotNetNuke WebControls project is to allow developers to utilize feature-rich controls in their applications without the associated cost or distribution restrictions associated with commercial controls. All controls utilize the ClientAPI, and therefore support a rich client side object model, work cross-browser, and utilize AJAX functionality.

The DotNetNuke TreeView control is an open-source ASP.NET WebControl that has a rich client-side object model and supports advanced featuresets like populate on demand and keyboard navigation.
The DotNetNuke Menu control is an open-source ASP.NET WebControl that has a rich client-side object model and supports advanced featuresets like populate on demand and keyboard navigation (soon).
The DotNetNuke Label Edit control is an open-source ASP.NET WebControl that allows any label to be editable on the client where it uses a client-callback to persist the changes. Simply specify a client-side event like onclick to allow the user to edit. It supports RichText and MultiLine editing.
The DotNetNuke Text Suggest control is an open-source ASP.NET WebControl that allows any textbox to suggest the results the user is looking for by dynamically populating a menu of matched items.
The DotNetNuke Tab Strip control is an open-source ASP.NET WebControl that allows a page to be displayed in a tabular manner. It supports 3 rendering modes, including AJAX on-demand loading to allow for optimal performance.
The DotNetNuke ToolBar control is an open-source ASP.NET WebControl that allows a toolbar to be attached to any control.
 


WebControls Project Blog
Mar 24

Posted by: Jon Henning
3/24/2008

Its been a while since my last post and I am feeling a bit behind on keeping people up to date on my latest involvement in the DNN project.  The main reason for my lack of posting is due to me starting a new job consulting.  Each time this happens, I usually drop all the "fun" projects I am involved during my spare time and brush up on the things that the new client is looking for.  This latest client has been pretty good, and provided some insights into what seems like the latest buzz word to hit technology shops:  Test Driven Development (TDD).  I definitely see some of the positives to this approach, but also some unexpected negatives.  Perhaps when time allows, I will discuss some of these, but for now lets focus on the topic at hand, DotNetNuke and the ClientAPI.

Way back in March of 2006 I made a post titled "Behold The Mighty $()".  The specific portion of this post I wish to discuss is

The $() function is something we added to Atlas as well. It basically is useful short-hand for document.GetElementById("name").
Hope this helps,
Scott

Here we are 2 years later and I am still regretting following the bandwagon and people are still paying for it.  One of my thread postings from last year outlines my thoughts well on the matter.

The whole idea of the $ function and who "owns" that "namespace" has become quite muddy.  When I first learned of the use of $ and found that MS was adopting the same notation, I decided to do it as well.  For at the time, I felt that all frameworks simply used it as a quick way to get the reference to a DOM element.  Soon afterwards I learned that frameworks like prototyle use it for much more.  Apparently, MS learned this as well, and decided to switch to $get.  What I never understood is why they went through all the trouble of creating a nice namespace hierarchy, minimizing chances to have conflicting functions, then decided to scrap the whole idea and make shortened alias' with the $.  In essence, they are saying they "own" the $ namespace.  I have commented back and forth on this issue here.

Unfortunatly, I cannot just yank my $() function since I have to worry about backwards compatibility (at the time MS did it they were in beta so they could).  My $ function should be functioning with prototype last time I checked.

I am happy to announce that the next release of the ClientAPI/WebControls and DNN 5.0 will no longer use the $() function.  The ClientAPI will still declare it if it finds it is not already defined for backwards compatibility, but this should reduce the number of conflicts people are finding dramatically. If you have any modules that rely on this function existing, I suggest changing your code to either (document.getElementById() or if you are requiring MSAJAX as Cambrian will, $get()).

Thats all I have time to report for now.

 

 

Tags:

Re: Javascript Global Namespaces (the dreaded $ function)

In jQuery you can just put this at the top of your functions file:

var j$ = jQuery.noConflict();

and then use j$() instead of $()

It's always worked flawlessly in DNN for me.

By phazer on   3/25/2008

Re: Javascript Global Namespaces (the dreaded $ function)

Great news! Thanks for all of your hard work Jon!

By irobinson on   3/25/2008

Re: Javascript Global Namespaces (the dreaded $ function)

Awesome tip, phazer. You just made my day.

By grill on   5/6/2008
 


Advanced Web Portals by Infoscaler
Infoscaler is a California based company that provides advanced Web Portals, E-commerce Sites, Database Applications and Intranet Solutions on the DotNetNuke and Microsoft.NET platforms.
www.infoscaler.com
DotNetNuke® in Sweden
All service of DotNetNuke® in Sweden.
Olsmar Konsult
Overlook Technology
Website Development, DotNetNuke Consulting, Module Development, Portal Management
OverlookTechnology.com

DotNetNuke Corporation   Terms Of Use  Privacy Statement
DotNetNuke®, DNN®, and the DotNetNuke® logo are registered trademarks of DotNetNuke Corporation
Hosted by MaximumASP