By Jon Henning on
4/13/2008
While sitting at the airport waiting for my plane to depart to the MVP Summit, I decided to spend a little time optimizing the new ClientAPI (codenamed Caspian) for the Cambrian release. One of the new features for this release was to allow the output of the ClientAPI and Webcontrols to emit compliant markup (more detail mentioned in this blog). There was two areas that this affected my code.
Read More »
|
By Jon Henning on
3/24/2008
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.
Read More »
|
By Jon Henning on
10/5/2007
Ever since version 1.0 of the Solpart menu, it supported animations. Unfortunately, these animations were specific to IE due to it being the only browser that supported transitions natively. When I created the DNNMenu I had decided not to go this route, but rather seek out a technique that worked across all browsers. When I was first reviewing the Atlas bits, there was a portion called Glitz, which I had anticipated would support the animations I was looking for.&n ...
Read More »
|
By Jon Henning on
6/15/2007
One interesting enhancement that the AJAX Control Toolkit team came up with in the latest release is yet another way to register your scripts (ToolkitScriptCombiner). Earlier I ...
Read More »
|
By Jon Henning on
6/15/2007
I have finished the initial conversion of the DotNetNuke WebUtility (ClientAPI) project to utilize the Microsoft ASP.NET AJAX Extension framework. This has several advantages and one major disadvantage. The disadvantage is tha ...
Read More »
|
By Jon Henning on
4/13/2007
I will be releasing the next point release of DotNetNuke WebControls (v1.5.3) shortly. There are a couple reasons for this. First, it was detected by some users that the currently released version with DNN 4.5 was compiled in Debug mode, thus affecting performance a little. The second, and primary reason is due to our desire to try (emphasis on this word) and maintain compatibility with other AJAX frameworks. In this case we ...
Read More »
|
By Jon Henning on
3/2/2007
Being able to retrieve and set personalization values on the client is a new feature that DNN will support for version 4.5. Since personalization is something specific to DNN, the code will reside in the DNN specific ClientAPI files of dnncore.js and DNNClientAPI (ClientAPI.vb). The current state of the dnncore.js is such that it does not utilize namespaces. Instead it prefixes all function names with __dnn_. Module developers use these client-side functions ...
Read More »
|
By Jon Henning on
1/3/2007
Before I get into the reason for the article I wanted to wish everyone a Happy New Year! I have been very busy the past couple months on the next version of the ClientAPI and WebControls and am getting anxious about publishing my work. However, I am going to need a couple weeks to gather my work up again after the long holiday and polish it off a bit. In the meantime I wanted to give a quick bit of history regarding my decision in how to obtain what scripts ...
Read More »
|
By Jon Henning on
9/18/2006
Back in 2004 when I was creating the ClientAPI I spent some time trying to find the best way to edit javascript, with hopes that I would find a solution that offered IntelliSense™ and an easy means to document it. Having found neither I decided to create my own console app to transform an XML file Read More »
|
By Jon Henning on
5/24/2006
A couple months back the core team was going over some of the excellent enhancements Charles was working on for the 3.3/4.1 release. One of those pages offered the ability to customize the user properties, including the order in which they were displayed. The traditional method for reordering a list was implemented, meaning the use of postbacks. I was tasked with coming up with a better way to accomplish this without requiring postbacks.
Read More »
|