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

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsClientAPIClientAPIClient side IMCClient side IMC
Previous
 
Next
New Post
3/29/2007 4:03 PM
 

Hi, I've been reviewing IMC and am interested in a client-side implementation of this to enable communication and updates of modules using ajax.  Is this possible with the current clien-side API or is this custom development that would be required?

 

Michael Iacoviello

 
New Post
4/2/2007 1:50 PM
 
I don't understand what IMC has to do with this.   When on the client, you have access to all elements rendered to the browser.  You can then invoke a callback to any module on the server-side to pass whatever info you want.  More information on client-side callbacks can be found in this document.  A sample module using the callback can be found here (HelloAJAX).

 
New Post
4/2/2007 2:21 PM
 

Well, I guess my interest was around a client side abstraction of having to work directly with the HTML elements, searching for divs. etc.  The question is really if there is a designed set of guidelines/APIs included with dotnetnuke that can be used to send messages on the client side to your modules without having to use IMC and do a post back.

For example, one module on the page, I would like to tell another module on the same page to refresh (and it will use ajax to refresh itself) with certain information without having to do a postback of the entire page, and hopefully while using client side APIs that are available (this is where the client side API to IMC link was being questioned).

I already have an ajax implementation working in my modules, I am not looking for ajax.

Michael Iacoviello

 
New Post
4/2/2007 2:49 PM
 

The question is really if there is a designed set of guidelines/APIs included with dotnetnuke that can be used to send messages on the client side to your modules without having to use IMC and do a post back.

Yes, thats the Client Callback document I linked above.  In other words, you can use a callback to call into a function of any module/control that supports the proper interface. 

For example, one module on the page, I would like to tell another module on the same page to refresh (and it will use ajax to refresh itself) with certain information without having to do a postback of the entire page, and hopefully while using client side APIs that are available

What triggered the first module to want to change itself?  A client-side event?  It almost sounds as if you are talking about what the UpdatePanel from MSAJAX does with its triggering properties.

I guess I am still confused as to what you are asking.


 
New Post
4/2/2007 2:57 PM
 

This is probably my fault.  Let me start over.

I would like a client-side event from one module to trigger a client side action to happen on another module (it may or may not refresh itself), without having to post back the entire page to the server.

I would prefer to use a predefined dotnetnuke design or API for this if it exists, before tackling a custom client-side solution.

Thanks,

Michael Iacoviello

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsClientAPIClientAPIClient side IMCClient side IMC


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