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...Module ForumsModule ForumsForm and ListForm and ListExport a UDT as a ModuleExport a UDT as a Module
Previous
 
Next
New Post
12/23/2006 12:10 PM
 
I posted this in reference to the deprecating of the the Contacts Module in favor of the UDT. And figured I should post it here as well...

On the deprecation of Contacts, While I think your right that you can better implement contacts through UDT, I think there is a lot of value in having Contacts appear as one of the modules in the Module dropdown. A lot of the users of DNN are not all the technical or even creative, and the idea of using the UDT for contacts just won't occur to them.

Perhaps the best solution is to somehow allow UDTs to be exported as a module. That could result in a huge number of great modules, with very little additional code having to be written.

David O'Leary
Efficion Consulting
 
New Post
12/24/2006 3:39 AM
 

David,

thank you for your idea, but this will require a core change. I can imagine improving the control center using a hierarchical menu instead of the dropdown that grants access to available templates in the submenus, but there are other ideas as well that needs to be discussed in the core team to decide, how to implement this improvement.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
12/26/2006 11:58 AM
 
While I think there should be some core modifications to make this type of thing easier, I'm pretty sure it could be done without core mods. If you added a new class with a placeholder in the ascx file and the ability to load a configuation file in the code behind (with basically the same info as used for the IPortable export but without the data, just the structure). Then you create the module zip containing: the .dnn file setting the new class as it's view file and the config file. They would have to already have UDT installed.

The only thing left would be to decide whether to always load the structure from the config file or to import that into the UDT tables and treat it as a normal UDT module.

This is just a couple minutes of thinking about this so I'm probably missing some stuff but I could also use this same idea for specialized versions of my Advanced DataGrid and my Articles module. If only I had the time...

David O'Leary
Efficion Consulting
 
New Post
12/26/2006 12:45 PM
 
IMO not everything, that can be done should be done - if an implementation is not straight forward, it often results in a dead end of development. Of course we can provide additional module definitions, which will appear in the list of available modules to be placed on pages and are loading a predefined set of data, this cannot be extended by users saving their own modules as templates - currently only by bypassing the core, which I alwys try to avoid. Extending the core with an improved template handling is preferable from my point of view.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsForm and ListForm and ListExport a UDT as a ModuleExport a UDT as a Module


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