Hey David, Yep, I'm thinking along the same lines. I wrote a method and macro combination some time ago that I use to document my Component methods. Basically it scans method code for the topmost commented lines, strips the escape characters and writes the text to the method comment field. I also include the update date (which doesn't get incremented by this operation) and the method attributes. I habitually head each method with things like the method name, argument list and a description of what it does. A long time ago another programmer told me something like, "if you can't say in English what you're trying to do you probably won't be able to code it either." So I like starting out with what I think I'm doing.
Anyway, this is a real blessing for component methods since the comments pop up when you hover over a method if there are any. So that's what got me thinking about extending the idea to also figure out the param input types and put it into a c-obj just to make it easy. It could just be from text too. Have you played with the #4DCODE tag Tim mentioned? That has all sorts of possibilities. -- Kirk Brooks San Francisco, CA ======================= ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
