Yeah, everybody I mention it to says it's a well-paid line of tech to be in. Good enough for me.

Thank you Jake!

Tip to stop the section to confuse Notes users: set the hide-when properties of the controlled access section to be hidden (I did that by checking all options in the subsection "Hide paragraph when document is")

Then, make sure there NO hide whens on the rich text field.

Also, in the autoexpand tab, I set all options to autoexpand for both Editord and non-Editors.

Result: the access control still works, but the section title, and more important, the twistie, are hidden. So the user is not confused about the extra UI element. Using the menu, Edit:Collapse all Sections, does not affect Controlled Accesss Sections prepped like this.

Lars Berntrop-Bos

So simple, yet so powerful!!

Go to "Options" and take note of the number of code lines. Add that number to the output of Erl(). Go to the full code view and - magic - find the correct line.

Now the master question is: What about empty trailing lines? To count or not to count, that's the question.

I use intensively them too, there's only a quite annoying thing about the Erl() that returns a wrong line number in any class method. :(

It's a shame and annoying there is nothing similar in Chrome for the Mac for some reason: https://productforums.google.com/forum/?fromgroups=#!topic/chrome/nfaA5_Hmtms

Backup early, backup often.

Have an alternate email address ready.

I ended up using a subset of them to keep weight down even further. Using this tool http://www.icnfnt.com/#/

I have these comment templates that automatically make lsdoc-compatible stubs to my classes, subs and functions.

The real killer application for lsdoc.org is that I have a system documentation which is available with very little effort. Whenever a client says 'what about the documentation', I print out the HTML files relating to the project databases, and I am a hero.

The Lsdoc.org makes clickable documentation files, and I find makes a very nice display of the way different classes link to each other.

Here are my snippets:

Class:

'/*************************************************************************************

' * A Class to represent

' * @author ${author}

' * @version ${date}

' *************************************************************************************/

Function

'/*************************************************************************************

' * ${element_type} ${element_name}

' * @param

' * @return ${element_returntype}

' * @author ${author}

' * @version ${date}

' *************************************************************************************/

Sub

'/*************************************************************************************

' * ${element_type} ${element_name}

' * @param

' * @author ${author}

' * @version ${date}

' *************************************************************************************/

I even comment on atnotes and have visited uklug last year. I haven't opened a Notes Client for 2 years and my last line of code should date 3 or 4 years back.

Nostalgia. Don't know. Probably the awsome work environment back than at Kasten ;-)

And yes, there are lots of pointless comments, at least on the projects I participate. Architects and Project Managers love to activate checkstyle rules for comments and programmers love to find ways to trick this rule with the least amount of effort.

Writing good comments is hard. I am only theoretically good at that. Just at this very moment I don't understand part of some strange stuff in some jsf beans, I have written 2 month ago.

We need comments in the not obvious parts of the program. I tend to write these late in the day in an empty office. In the process I change a lot, so I don't see much point to write comments as there is a high probability that I will delete this source code. I should write comments when this for me hard part stabilizes, but I often tend to "forget".

Thou shall write comments is an ok guideline, but what we really need are good comments and this is hard.

Frankly, I don't quite get, what exactly the task for the dumb guy would be (Deleting obsolete comments? Adding them, where the IDE didn't do it?), but I can't think of any public property of any class, that wouldn't be worth at least a short comment ...

I just had hoped, that IBM would have adopted Mikkel Heisterberg's LSdoc project. Having said that, it might be worth noting, that the LS editor's pop up help is not restricted to comments using the %REM ... %END REM notation. If you have existing LSdoc style comments in your classes, you will notice, that those are displayed as well.