Question for CFLib Users

When you view a UDF at CFlib, we nicely render out the parameters for the UDF, and the return value. We also auto-generate UDFDoc comments for our UDFs.

If this were to go away, would it matter to you? Obviously you would still be able to view source. Also, UDFDoc would continue to exist, it would simply be a more manual process for myself.

Archived Comments

Comment 1 by Bill Rawlinson posted on 2/4/2005 at 9:14 PM

if it is auto-generated now - why get rid of it?

Comment 2 by Raymond Camden posted on 2/4/2005 at 9:17 PM

I am going to be adding new types of resources to CFLib. I'm trying to simplify the data model a bit.

Comment 3 by Steve Ray posted on 2/4/2005 at 9:21 PM

Ray, could you give us an example of the types of resources you're thinking of? My first reaction was similar to Bill's. If this stuff is there and it's useful (which it is), why get rid of it?

Comment 4 by Raymond Camden posted on 2/4/2005 at 9:25 PM

The main thing happening is that CFCZone is going to roll into CFLib. Other resources are planned, but I can't comment as of yet. I _would_ continue to store UDFDoc comments in the UDF. I would just be doing it by hand. When you view a UDF, you wouldn't see the "parameters" or return type, but you could easily see it when you View COde.

Comment 5 by Ryan TJ posted on 2/5/2005 at 12:52 AM

As long as the description says the return type I don't mind reading the source UDF code for the rest.

Comment 6 by tony petruzzi posted on 2/5/2005 at 2:17 AM

Ray. If you are going to be adding different types to CFLib.org, like say Tag and CFC's, then really you don't need to get rid of the autogerente, you will just need to move it.

Let me explain. From your comment, it seems that you have the autogenerate code inside the display template. What I would do is move the autogenerate code to a backend that you guys probably have to insert the UDF's into the database.

All you would have to do have is rewrite some portion of your backend that will let you pick whether the TYPE is a TAG, CFC, UDF, etc. and then the appropiate form would disply for you to enter the information. Once this for is filled out, just store the entire thing into a text (SQL SERVER) field inside the database.

I'm probably telling you stuff you already know. But from your post it sounded like you were stumped.

Comment 7 by Andy Peters posted on 1/17/2009 at 6:58 PM

UDFDoc might be from 2005, but I would like to use it. Where can I find it 2009?

Comment 8 by Raymond Camden posted on 1/17/2009 at 7:01 PM

No guarantee this will work: (I mean the code, the links work)

http://old.cflib.org/downlo...
http://old.cflib.org/downlo...

Comment 9 by Andy Peters posted on 1/17/2009 at 8:26 PM

Thanks a lot for the quick reply...but the link does not work!!

Comment 10 by Raymond Camden posted on 1/17/2009 at 8:32 PM

Oops. Add a HOSTS entry for old.cflib.org. Use ip 67.59.153.214.

Comment 11 by Bijan Atri posted on 4/28/2010 at 9:52 PM

Hello,
I can not download udfdoc.zip or udfbrowser.zip from the url neither using FQDN or The IP provided. Could you please help.

Comment 12 by Raymond Camden posted on 4/28/2010 at 10:07 PM

Sorry - not supporting or providing those downloads anymore.