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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...To use Lists... or not to use ListsTo use Lists... or not to use Lists
Previous
 
Next
New Post
11/17/2006 3:45 PM
 
Hi folks,

I'm not looking at getting flamed here, but I think it's something worth discussing.  So, I'm going to stick my neck out.  However, it would be nice if we stick to discussing pros/cons of Lists as opposed to anything else.

For background, read this thread, and then come back here to post.

Cheers!





Rob Poretti - Poretti Productions
 
New Post
11/17/2006 4:52 PM
 

Use List if its a portal list (same list for all portals)  that dont need to be traslated to other languages.

In all other cases dont use LIST.

An example how LIST not should bee used are the categorys in Feedback module. By the way I hope the reviews in the Marketplace are better than the review of the Feedback module.

Jan

 

 
New Post
11/17/2006 5:43 PM
 
A very pragmatic approach... sounds good.

What about the consideration that Mr. Leupold has flagged, that lists are not (and apparently cannot) be localized?


Rob Poretti - Poretti Productions
 
New Post
11/17/2006 6:14 PM
 

I dont like if its not possible to localize. If you take the decition to do it you can do it. I can do it, but there are other areas that should bee done before.

The function can bee good in som special installations but as a common tool to have standard modules using it for categories are stupid. But for currency its good but it have been better if I could translate it.

Jan

 
New Post
11/18/2006 9:12 AM
 

there is another limitation of lists, I already mentioned: ech entry consists only of key and value and is not extensible. IMO this is an effective limitation especially for countries, where a number of other attributes are needed by various modules, e.g. store, but also by the core itself. Typical attributes are

  • national flag
  • currency
  • Daylight saving time (DST) regulations
  • "terms of use" conditions

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...To use Lists... or not to use ListsTo use Lists... or not to use Lists


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