RE: [Blogcfc-develop] More B3 Comments

[Raymond C. <jed...@mi...>]

> 1) Is there a way for me to tell what files have changed from 
> the B3 I downloaded last week and the one that is available 
> today? And other than looking at the files side-by-side, is 
> there a way to tell where a file has changed? I needed to 
> integrate the new build but didn't want to overwrite the 
> changes I have made to layout and such...


blog.cfc for sure (fix for N categories) and edit.cfm (fix for editing
entires w/ <more/>

> 2) I was wondering if the layout could not be a little more 
> abstracted (if that is the correct word). I like having 

Yes! It can be. That's probably something I'll work on post 3.0.

> control over what goes where. For instance, I like having the 
> Recent Items pod at the bottom of the page and I only want to 
> have 5 blog articles appear on the index. I guess that my 
> question comes down to this: Do we want normal people to be 
> able to create layouts for their blog, or will that require a 
> CF developer? If normal people are targets, then should we 
> find a way to create changes like the two I mentioned in a 
> preferences setting (in the blog.ini?) or as part of some 
> admin set-up process? 
> (This isn't a change request. More of a 'Where are we going?' 
> request.)

I kinda figured the typical user would be at least a low level developer.
But there is DEFINTELY something I can do make it easier. The docs will
help, and again, post 3.0 I'm going to work on it.

> 3) The "?reinit=1" code seems to work sporadically, but I am 
> more comfortable with it now, and it surely is less painfull 
> than restarting the service every time I needed to see a change.

If you can find a case where it doesn't work, please let me know.

> 
> 4) Am I correct in thinking that the RSS feed is generated 
> each time the cfm file is called? The RSS file gets updated 
> each time an entry is made. So why have it hit the server for 
> processing on each request. Why not have it generate an 
> actual RSS file each time an entry is made and have an RSS 
> file written at that time. Then refer people to the actual 
> RSS file. Wouldn't that reduce server load? [OK, I *know* I 
> am missing something here. I thought I'd stick my neck out 
> far enough it might generate a discussion.]

No, you aren't missing anything. That is a very valid criticism. There is
only ONE thing I can think where it would matter, and that is a case where
you change blog.ini settings. Of course, that is a rare thing, and we can
add a 'regenRSSFile()' method or some such. Either way, I'll defintely
consider it post 3.0. 

I'm going to be adding an instance of Lighthouse Bug Tracker for the project
since I'm more comfortable w/ that then sourceforge. I'll use it to track
stuff like this.

-ray