Blogo 1.50 is out!

Ferdy has released an update to his popular weblog template, Blogo so that it’s now at version 1.50. You should seriously check it out. What’s more, if you’re a Domino developer you should take a look to see how an XHTML application can come to the table when Domino’s in the house. Sure, the technique used means reams of pass-thru (Nathan won’t like it), but if you’re even remotely serious about development, hypertext mark-up will not even nearly intimidate you.

If it does, you’re in the wrong game.

Anyway, take a look at Blogo, especially if you want to integrate TinyMCE with your Domino application—I believe Ferdy is planning on writing more about this integration point, but if you need to know more, drop me a line… I know more about doing this than I ever wanted to; Ferdy had the dubious pleasure of dealing with me on that score! LOL.


  1. Ben, thanks for the plug, I appreciate it very much. And yes, I intend to come up with that article asap. You'll see plenty of your help back in it :)Ferdy#
  2. Just too clarify the reference, even though I know Ben's just playing, my complaint has always been that the use of pass-thru in a Domino application demonstrates either the failure of the developer, or the failure of the PLATFORM. That statement was a chide at IBM for letting the HTML generation by the platform languish for the last, what, 8 years?

    I still think it's true today. It's just that with each passing version, the blame is more on the platform.

    But we went through all that at Jake's a while back, didn't we? ;-)

    Anyway, yeah, I still hate pass-thru, but it's WAY more IBM's fault now than it was when I originally started complaining about it.Nathan T. Freeman#
  3. Nathan, no problem. I respect your opinion on this and partly agree with you. The intention of Domino development is that you should not have to worry about HTML too much, the abstraction layer should hide it and the engine should generate proper HTML.

    Unfortunately, I also do not find the Domino engine fit for today's use and today's standards. On top of that I have a personal preference of having control over the HTML output. I first thought it was just my own neurotic habit. It turns out that as I am exploring other platforms, it is perfectly normal. PHP, J2EE, .Net…all to some level encourage you to take control over the HTML. As Ben said, at this point HTML should not be intimidating to anyone anymore.

    I like the .Net approach where you can work in an abstract way or do a deep dive into the actual code, it's your choice. You can always come back to your choice: change something in HTML and then see it visually in a more abstract way. Ultimately, I wish Domino would offer this.Ferdy#
  4. Hey Nathan, thanks for weighing in—and you know I‘m just being a tad ornery with my comments anyway ;-) Ferdy has it right: I would GLADLY let Domino take on HTML generation if I thought it would do it right. I'm just too much a of a tag nazi to let that happen right now… Yes, coding your own HTML around Domino’s limitations can be a pain, but it’s really not THAT bad, and you still get to use all the cool tricks Domino does right out of the box. So overall I’m happy with it.

    Re Jake’s site, dunno, I was banned from that place long ago, so I have no idea what he’s doing. Let me guess though: is he still pissing and moaning about how crap Domino is at HTML?? ;-) Ben Poole#
  5. @4 - Yeah, that's exactly what it was. :-)

    Just so both of you know, the reason I don't like hand-coded HTML in Domino apps is not because I'm intimidated by HTML. Far from it. I just think it's a waste of developer time to have to do it.

    5 years ago, it was spinning wheels to spend hours of coding time and create huge maintenance headaches for the sake of moving a table 3 pixels to the left. But that was also based on the expectation of IBM actually furthering the HTML generation engine. In the five years since then, we've gotten… what… CSS resources and JavaScript libraries? It's their fault now that anyone has to do it. Domino should have been generating AJAX code automatically at least 2 years ago.

    That being said, I still think it's a proper approach to Domino development to MINIMIZE hand-coded HTML as much as possible without sacrificing design goals. Here's an example of a method I used recently to do that -- It's a different way to do it than anyone normally would with generalized HTML, but it makes a ton of sense in the context of what Designer does for you.Nathan T. Freeman#

Comments on this post are now closed.


I’m a software architect / developer / general IT wrangler specialising in web, mobile web and middleware using things like node.js, Java, C#, PHP, HTML5 and more.

Best described as a simpleton, but kindly. You can read more here.