Looks like Rev. Jim (no relation to the evangelist who used to visit college campuses, I’m sure) has also been thinking about blogware.
“A weblogging application? Okay, that’s pretty easy, really. Just build a model to access the data and work from there. Well, what should the model include? Weblogging stuff, obviously. How about comments, trackback and pingback? I guess I could stuff that in here, but that might be overloading things a bit. They should be their own models. That’s easy enough. I’ll start with just the weblogging piece and add the other pieces afterward. This means I need to write modularly so that these features can easily be added and removed in the future by any user who chooses to do so. How should I do that? I guess I can have the controller detect what modules are available and then assign those pieces to the view accordingly. But what if a piece is available but the user doesn’t want to use it? I guess I should have each model announce it’s capabilities in a systematic way. […]”
Sounds like the same problem I have in getting motivated to write dblog: I’ve got more ideas than I have time. The other problem I have is that all of the fun is in solving the problem, not implementing the solution.
Hmm…. Maybe I’d make a good manager, after all….
2 Responses to Blogware