Ok.  I'm stumped.  I'm working in Dnn 6.0.1 and I need to add functionality to the basic Text/HTML core module 'edit' settings.  There are two pieces I would like to incorportate into this.  The first is a version comparison tool that pulls two version from the database and compares them side by side highlighting changes (I have this code written in a simple aspx page).  The second piece of code I need to incorporate is code to display older versions of the HTML content in the full page as it looked at the time it was published (a better looking version of the preview panel in the edit panel).  I had hoped ot utilize the preview skin but pass in verison of the HTML being reviewed to display the full page that can be printed etc.

Here is my issue.  I need to change the Text/HTML Settings page to include two additional expansion panels where I can insert this new code without changing the core code. We do not want to keep up with the changes and have to repeat them when we upgrade hence I have been asked by my boss to find another way.  I have looked into the ClientAPI, RazorScript, and jQuery and still not come up with a simple way to accomplish what I am trying to do.  I would love to write a custom module that loads the Text/Html module into it as a control and extends the funactionality as needed with my additional code.  There are several things I have read that hint at doing something of this nature, but I can not find anything to tell me how or if this can really be done.  Any help or direction anyone can provide would be greatly appreciated.

Thanks,
Jeff

Cathal,

Thanks for your prompt response!  In researching this further it looks like I will also have to add header.text to the resource file to remain consistent with the other programming in the core module, if I adhear to standards.  Even with the most minor change to the resource file and just adding a line or two to the jquery in the bottom of the control, I am still modifying the core source which would have to be revisited when an update occurs and of course the code will be spred out across modules.  While I did find information that was helpful in extending the class so that additional functions could be added to the control, based on what you sent it does not appear that what I am trying to accomplish can be done in the framework without making at least some minor changes to the code.  If there is something I am missing in these articles please let me know. 

Since it looks like I am going to have to change the core code regardless of the method I use to enhance it, I am going to try to change the code in the least amount possible.  My current plan is to create a user control and use the LoadControl method to push the code into a placeholder within the Edit control.  This seems like it will allow me to embed the core functionality I am trying to accomplish within the custom user control/dll while only having to add a placeholder in the edit control when an update occurs.  Does this seem like a viable plan or do you suggest another method?

Thanks,
Jeff

Cathal,

Thanks again for your prompt response! You have been greatly helpful in determining how this quandry needs to be resolved. My company currently has a professional license and while I have the compiled code available for use via this license, it does not apparently include the source code so I can extend the module per our discussion. I have requested additional information from support.dotnetnuke.com to provide enough information to explain the development issue to my management. If I am able to obtain the source code I will be sure to create an additional fork of the code, and submit it to support so the community can benefit (hopefully).

Thanks again for you assistance!

Jeff