RE: [Blogcfc-develop] First Zip
Brought to you by:
cfjedimaster
|
From: Ben F. <bf...@ma...> - 2003-08-12 02:19:59
|
1) Yeah, but you hard coded your name etc. in the path. :-) 2) > and < in dates suck, don't do it. = sucks even more. Dates are the worst when it comes to SQL (especially if you use Oracle). And FWIW, I strongly disagree with you pulling out DB specific stuff, I think you should indeed use your DB and let it do what it does best. Diff DBs? Sounds like a job for a) stored procedures, b) a loadable db library, c) inheritance, d any or all of the above. -----Original Message----- From: blo...@li... [mailto:blo...@li...] On Behalf Of Raymond Camden Sent: Monday, August 11, 2003 9:07 AM To: blo...@li... Subject: [Blogcfc-develop] First Zip Ok folks, I'm a bit too rushed to investigate the CVS interface, so to make things easier, I'm just sending a zip. Remember, this is not a new feature package, just a 'clean up' package. Changes include: 1) Path changes. The client, cfc, and install crap are all in separate folders. 2) Cleaner DB code: Except for two places, there is no SQL Server specific code. The goal is to make the Blog work ok in most, but not all DBs. The db specific code that remains is date specific. I'm going to switch from datePart/diff calls to the use of "where date > X and date < X" type syntax. Anyone know how portable that is? 3) Migration Script. There is a migration script in the install folder. It worked ok for me, but has not been heavily tested. 4) There was a bug where I used "id" in a cfc method and it matched a url var, so now ALL arguments use "arguments." in cfc methods. 5) The old article editor didn't have a way to add a new category. There is now a way to do so. Rough order of what I'll do next: a) Change the db specific code and see if I can get Access/SQL Server both running out of the box. b) Add "More" support. This is a super easy thing to add. c) Purely for my enjoyment, support for <code>. What will <code> do? Any entry that has a <code></code> block in it will... Automatically color the code using the coloredcode custom tag. Automatically escape < and > So this means you can do <code> <cfset x = now()> </code> In a blog entry and won't need to worry about escaping the <> in code. It will be done for you by the client. d) And then of course we need to begin the real work of getting N blog support/N user/etc. ======================================================================== === Raymond Camden, ColdFusion Jedi Master for Mindseye, Inc (www.mindseye.com) Member of Team Macromedia (http://www.macromedia.com/go/teammacromedia) Email : jed...@mi... Blog : www.camdenfamily.com/morpheus/blog Yahoo IM : morpheus "My ally is the Force, and a powerful ally it is." - Yoda |