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

HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...Where's the full documentation for the API and methods?Where's the full documentation for the API and methods?
Previous
 
Next
New Post
2/9/2014 2:34 PM
 
Chris Hammond wrote:
The way we've always done it, trial and error.

 

How does trial and error even work? You try something which you might think will work and if it doesn't work, you look for something else? Very inefficient and crude way to use an API.

 
New Post
2/9/2014 3:31 PM
 
Sorry - I saw you joined six years ago w/ 400 plus posts. Assumed you had some experience.

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
2/10/2014 11:06 AM
 
We know the API documentation is incomplete, much of this comes from being an opensource project - OSS projects tend to have a history of developers only interested in writing interesting new features and not doing "boring" work like documentation. As DNN has existed for 6 years before the Corp theres a lot of legacy methods need documented (code contributed by the corp has a requirement for xml documentation so you'll notice those methods correctly documented usually). Ernst-Peter Tamminga and I (as part of the reference team) worked on this area a few years bak(the sandcastle scripts are from Ernst-Peter). At one point we published a blog with a suggested format of code commented and asked for contributions to help in this area. Sadly we had almost no contributions so the effort died out - I would love it if people would consider helping out now (with github it's a lot easier to take a contribution). BTW the wiki often has useful content as it allows for more space to contextualize API methods e.g. editurl is covered as part of module navigation @ http://www.dnnsoftware.com/wiki/page/...

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
2/10/2014 2:12 PM
 
cathal connolly wrote:
We know the API documentation is incomplete, much of this comes from being an opensource project - OSS projects tend to have a history of developers only interested in writing interesting new features and not doing "boring" work like documentation. As DNN has existed for 6 years before the Corp theres a lot of legacy methods need documented (code contributed by the corp has a requirement for xml documentation so you'll notice those methods correctly documented usually). Ernst-Peter Tamminga and I (as part of the reference team) worked on this area a few years bak(the sandcastle scripts are from Ernst-Peter). At one point we published a blog with a suggested format of code commented and asked for contributions to help in this area. Sadly we had almost no contributions so the effort died out - I would love it if people would consider helping out now (with github it's a lot easier to take a contribution). BTW the wiki often has useful content as it allows for more space to contextualize API methods e.g. editurl is covered as part of module navigation @ http://www.dnnsoftware.com/wiki/page/...

 

I understand what you're saying. I am a developer and I know documentation is boring. However IT IS boring if you sit down in a long session and just write documentation. No one wants to do this.

BUT people are approaching this the wrong way. You write documentation in a piece meal way. When a developer looks at some code in DNN and sees a method that he's familiar with and has no description, he can jot down a quick description in a few seconds and then go back to what he was doing. This way it's not a boring task. It's quick. When enough developers do this over time, eventually the documentation gets more complete. It's distributed and efficient. I expected the developers in the corp to have done this, including legacy code. I am assuming they look at legacy code once a while.. right?

It's like the goal of reCaptcha project. No volunteer wants to sit down and transcribe all the non readable words in a big book but when lots of people enter a single word, even just one word a day, the book will be done in no time.


 
New Post
2/10/2014 4:57 PM
 
We actually do that (we refer to it internally as "the boy scout rule) - if an engineer is working on a file they're supposed to check any recommendations our refactoring tool (resharper) makes - we often remove unused private variables, add documentation, inferred variables etc. However there is years worth of undocumented code, some in sections that rarely get touched, and short of the team stopping work on fixing bugs and adding new features (which is not realistic) I don't see us doing substantial documentation in the near term. This is an area we would really welcome contributions in - see https://github.com/dnnsoftware/Dnn.Pl... for guidance

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...Where's the full documentation for the API and methods?Where's the full documentation for the API and methods?


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