Procedural DOES NOT EQUAL Bad. I'd argue that there are many use-cases where
it makes sense and OO is overkill. If your blog is really that simple, and
is going to stay that way, you can write one or two queries, a couple of
views and be done with it. The OO equivalent will probably take 10 times
longer. Now if you are planning to eventaully add all the bells and
whistles, I'd make sure to refafctor before going too deep procedurally.

On Fri, May 8, 2009 at 8:45 PM, Barney Boisvert <[email protected]> wrote:

>
> I have a hard time believing you can't use at least the bottom half
> (i.e. not the presentation layer) of an existing solution.  Use it for
> all the business logic, pings, trackbacks, feeds, comments,
> moderation, spam checking, etc, but integrate the UI into whatever
> you're building.  Simple blogging is really simple (the three entities
> you enumerated cover it), but covering all the ancillary functionality
> is a bitch.
>
> Obviously I don't know your situation, but I'd encourage you to at
> least think it through all the way before you completely discount at
> least a partially third party solution.
>
> cheers,
> barneyb
>
> On Fri, May 8, 2009 at 8:41 PM, Henry Ho <[email protected]> wrote:
> >
> > Thanks guys.. but due to some requirements, I cannot just do an
> > integration job.  It wouldn't work with the overall project.
> >
> > Henry
> >
> > On May 8, 8:27 pm, Barney Boisvert <[email protected]> wrote:
> >> I'm with Marc.  Rolling your own blogging solution is the correct
> >> choice about as often as CAPTCHA is (i.e. virtually never).  There is
> >> too much good software out there already, most of which you'll never
> >> be able to compete with in terms of ongoing development.
> >>
> >> cheers,
> >> barneyb
> >>
> >>
> >>
> >> On Fri, May 8, 2009 at 7:09 PM, Mark Mandel <[email protected]>
> wrote:
> >> > Just steal the tBlog sample app?
> >> >http://docs.transfer-orm.com/wiki/Example_Code.cfm
> >>
> >> > Why not just integrate BlogCFC, or MangoBlog?
> >>
> >> > Mark
> >>
> >> > On Sat, May 9, 2009 at 12:06 PM, Henry <[email protected]> wrote:
> >>
> >> >> I need a simple Blog app done quick, but when I got down into it, I
> >> >> couldn't justify doing it in an OO way.
> >>
> >> >> Service / Bean / DAO... with the Beans don't have anything smart to
> do
> >> >> on themselves...
> >>
> >> >> I came up with the Blog, Entry and Comment beans.  Blog has many
> Entry
> >> >> (s); Entry has many Comment(s).
> >>
> >> >> Then I couldn't think much methods that the beans above should have
> to
> >> >> make them smart.
> >>
> >> >> Then I thought about loading of blog / entry / comments from DB...
> >> >> when to lazy load when not to... Array of Entry objects with an array
> >> >> of Comment objects... Seems complicated, bloated and unnecessary for
> a
> >> >> simple blog.
> >>
> >> >> Transfer? Ya, that will help, but I'm not sure if I want to use it
> for
> >> >> such a simple blog app...  and every bean will become Transfer's
> >> >> decorators... What if I decide not to use it later?
> >>
> >> >> CFGroovy + Hibernate? Ya, that sounds sweet, but... when this app
> >> >> needs to be upgraded to CF9, I might have problem without disabling
> >> >> CF9's hibernate support.
> >>
> >> >> CFINSERT and CFUPDATE crossed my mind... I must be crazy.
> >>
> >> >> Please help. :)  Should a simple Blog be in OO?
> >>
> >> >> I should study BlogCFC over this weekend. :)
> >>
> >> > --
> >> > E: [email protected]
> >> > W:www.compoundtheory.com
> >>
> >> --
> >> Barney Boisvert
> >> [email protected]http://www.barneyb.com/
> > >
> >
>
>
>
> --
> Barney Boisvert
> [email protected]
> http://www.barneyb.com/
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CFCDev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/cfcdev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to