Contact Information
- Email: ctoohey@dominoguru.com
- BleedYelow.com: Chris Toohey
- Skype: ChrisToohey
- Gizmo: ChrisToohey
- Yahoo!: ChrsToohey
- Google: ChristopherToohey
(ctoohey@dominoguru.com) - AIM: ChrisToohey
- Twitter: ChrisToohey
- Facebook: ChrisToohey
- Podcast Information
http://www.yellowcast.net
YellowCast @ Twitter - RSS:

- Guru Tag:

My Twitter Updates
Publishings
Domino Development and Data Store Architecture 06/06/2008Domino Development RIM's Blackberry Connections Client - First Impressions (Part 2) 05/19/2008
My Gear RIM's Blackberry Connections Client - First Impressions 05/19/2008
My Gear Remove my name from the Domino Directory!! 02/05/2008
Lotus Notes Quick and Dirty Mail Application Document Importing 01/24/2008
Methods and Strategies Publishings Archive
Examples & Downloads
Self-Discovery leading to more content, downloads, and examples 07/01/2008Examples and Downloads Sorting Hat v0.1 06/30/2008
Lotus Notes SOTU - Remote Console Reporting v0.1 06/18/2008
Products Lotus Notes Client Wizard - Components Example Database 04/11/2008
Lotus Notes Updated: Quick and Dirty Mail Application Document Importing Example Database 01/29/2008
Examples and Downloads E & D Archive
Resources
PlanetLotus.org [ Community ] Alan Lepofsky's Notes Tips [ Community ] Chris' The Business Controls Caddy [ Community ] Petr Stanicek [pixy] [ CSS ] JoeLitton.net [ Community ] Resources ArchiveBleedYellow.com Dogears
That's it - I'm re-developing this blog template!
05/14/2008 11:39:34 AM | Chris Toohey | Bethlehem, PA
It was brilliant. I had commented a book on yesterday's post topic, and it was the stuff of legend. In it, I explained the following (watered down and from memory):
- I didn't want to replace documents as the Notes data store, per se.
- I DID want to implement a translation layer between the UI and the data store, thus separating the data store.
- This translation layer/data store separation architecture would allow us to maintain individual or multiple documents in external databases, as well as potentially update other data stores. Imagine you fill out a simple form and on submission I'm updating 5 different Notes applications as well as an XML file that's used by an ancilarry technology.
- The translation layer engine could be written to allow all of the business logic to be defined via configuration documents - allowing not only user control but also allowing us to "skin" like applications.
I mean it was poetry. It was insightful. It was brillaint. IT GOT ATED!
I'm saying that "my dog blog ate my homework brilliantly written comment", and I've had enough. I'm sick of this weblog template - written by yours truly, gang - and this was the last straw!
So I'm going to be writing a new blog template from the ground-up. Ctrl+N and I'm off.
Now, before anyone asks me why I'm not using <enter Domino blog template here>, I'll give you the honest answer. I think that the blog templates are great! They provide people with a quick-to-deploy solution that allows anyone to blog within moments. As a developer though, I cannot tell you HOW INVALUABLE it was to me to write my own. It's purely the development exercises involved in creating a blogging template that I'm interested in - it allows me to keep my skills sharp while integrating 3rd-party technologies and solutions that I honestly wouldn't see in "my day job". That's why I originally wrote my own (although that's not true, when I started this site there wasn't such templates lying around and available - you kids with your baggy pants and new fangled IBM blog templates have it easy... Now get off my lawn!), and that's why I'll continue to writing my own.
So, that being said, is there anything that people would like to see here that isn't already? Co-Comment was one suggestion. Anything else? I'm open to any suggestions at this point... but here's a few things that I'd like to do:
- Co-Comment
- Authenticated Comments - something maybe OpenID-based...
- Polls
- Good ol' Email Notifications/Newsletters
- (maybe) Threaded Comments
Like what you see? Help feed-the-beast by donating to the site and it's humbly thankful author!
Chris Toohey | Domino Guru

Comments
http://dowork.com
05/14/2008 01:38:55 PM
- Editable comments. I always want to tweak my comments and fix typos after I see them in the blog.
- Threaded comments. Make it easier to follow multiple conversations.
- No captcha. I've read there are other ways to stop comment SPAM.
- No markup for comments. Keep the comments simple. Two newlines to leave a blank line. Markup/Rich Text makes me spend too much time making it look pretty. The only exception to this is a way to put code into a comment that is correctly formatted/indented.
- No automatic quoting in comments. Too often I see people quote too much from a previous comment. If they have to type it that limits them to a smaller quote.
- Picture/video embedding in the blog (not the comments).
- Code displayed in the blog correctly formatted and indented.
- Automatic blog publishing at a configurable date/time. This way you can write blog posts in advance and have them appear at the exact time that you want them. This lets you get away on vacation and still have the blog be active.
Will you be sharing your template with the community?Peace,
Rob:-]
http://www.dominoguru.com
05/14/2008 01:43:35 PM
@Rob:
Awesome - please keep'em coming!
As for the sharing of the template with the community - absolutely! I would share this one if I wasn't absolutely embarrased...
http://www.assono.de/blog/
05/14/2008 03:37:47 PM
Come on, Chris, put your power into the Blogsphere template!
You can add so many necessary or nice things to the one, big free blog template. You can sharpen your wits and contribute - do not write the things that already have been written again!
And this way, not only one person, but thousands and thousands can benefit from your expertise and your sweat!
Contact Declan and come onboard. You could start with the mentioned email notifications. :-)
Thomas
http://www.dominoguru.com
05/15/2008 07:16:17 AM
@Thomas:
Thanks - now I'll look like a jerk if I say "no" ;-)
I have some ideas for this new template that go against the standard Domino architectures and methodologies at this point, so I don't want to much up someone's works. I'm going to open source this from the initial stages to the "go live" v1.0 - if it's successful and works how I hope it does, I'll be more than happy to bother Dec with my shenanigans.
I want this to be a community effort as much as possible, and I've come up with a way that I think will facilitate that want for "exposure" to the process while also coming up with a partner in crime.
More (possibly) later today on that though...
http://nathan.lotus911.com
05/15/2008 08:56:58 AM
Actually, I would suggest building it using xpages instead of more traditional Domino development. There's no point in flexing muscles you already have. Try out the new stuff.
You're on the beta. You're able to get the pre-release and install a server and Designer. Once the public beta is available, you're free to make the 8.5 server public-facing.
Instead of being yet-another-template, why not take a big step forward and advance the art?
http://www.dominoguru.com
05/15/2008 09:33:37 AM
@Nathan:
My only hesitation with using the xpages architecture is that, in order to gain any benefit from this work, you'll need to upgrade your environment.
My current plan is to utilize Web Services for all data maintenance, and Web Services are available with all currently "supported" versions of Domino. Not to mention that phase 2 of this plan warrants non-Domino development, so utilizing a proprietary (no matter how slick) architecture component would ultimately limit the intended solutions.
I know I'm being vague here, but that's slightly on purpose - I need to discuss a few things with the co-architect on this and get their input before I publically discuss anything that could get me into a "but you said it would..."-situation.
Also - quite frankly - Web Services is "new muscles" for a lot of developers out there. I know that I'm fairly inept compared to my mentioned co-architect when it comes to their utilization, so I think that utilizing them in the architecture will hit a lot more of the target area. Thoughts?
http://www.yancylent.com
05/15/2008 01:36:45 PM
Just a high level suggestion. Build a solid solution with focus on ease of use by default. Then have everything else be an add-on. There are so many examples of this, Firefox, Wordpress, where the original offing is a solid foundation that other members of the community, or other uses can build on... the bells and whistles. Build it (solid) and they will enhance. This will also increase your time to market; then you can build a couple cool add-ons.