Comments on: 8.5 Discussion template http://blog.pahudson.net/archives/117 Tue, 24 Jan 2012 09:25:59 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Ramble On » Things I learnt about XPages today - Do not use the quick edit tools http://blog.pahudson.net/archives/117/comment-page-1#comment-17 Ramble On » Things I learnt about XPages today - Do not use the quick edit tools Fri, 09 Jan 2009 00:48:45 +0000 http://blog.pahudson.net/?p=117#comment-17 [...] The html this toolbar produces uses inline styles rather than standard html and explains why the discussion template’s html seems to be missing any form of [...] [...] The html this toolbar produces uses inline styles rather than standard html and explains why the discussion template’s html seems to be missing any form of [...]

]]> By: Paul Hudson http://blog.pahudson.net/archives/117/comment-page-1#comment-16 Paul Hudson Tue, 06 Jan 2009 19:11:21 +0000 http://blog.pahudson.net/?p=117#comment-16 I've always thought the same. For me the big advantage of Domino is that you can easily generate new functionality. So why don't IBM do that. You wouldn't need a big team to generate a new template every few months. I’ve always thought the same. For me the big advantage of Domino is that you can easily generate new functionality. So why don’t IBM do that. You wouldn’t need a big team to generate a new template every few months.

]]> By: Mike McP http://blog.pahudson.net/archives/117/comment-page-1#comment-15 Mike McP Tue, 06 Jan 2009 16:28:01 +0000 http://blog.pahudson.net/?p=117#comment-15 I would say 50% of my blog comments are about IBMs templates:) I'm not sure why a company this large, with a development community this active, hasn't decided to open-source these templates. All it would take is a project manager to run them from OpenNTF.org and manage the code revisions, then a development team to scan the final code for security issues and take care of any 'consistency' issues. Instead, we complain about these templates during every release, and IBM fails to understand that these templates are the 'face' of Notes to the majority of users. Here's my challenge: IBM, you know 8.5.1 will come out, so put this template on openNTF and start an IdeaJam for enhancements requests. Sean will be your first contributor to take care of the accessibility issues! Give the big contributors a NFR copy of the server or something for their trouble. Is it really that difficult? I was forwarded a RIM PDF on how to blackberry-enable a doc lib or discussion template (can't remember which), complete with code samples. I just shook my head as I read it, wondering why on earth this wasn't built into the template already, with the strong IBM/RIM partnership. They went through the trouble of making a PDF to show DEVELOPERS how to make the template work. IS that not completely ridiculous? I'm sure RIM would have rather contributed to the template to make sure it worked out of the box... I realize someone could start an open-source discussion template, but the inclusion in the release is the key, for both bragging rights of contributors and wide-spread adoption. If it's open-sourced, then next release you can completely ignore us when we complain about how awful they are:) I would say 50% of my blog comments are about IBMs templates:) I’m not sure why a company this large, with a development community this active, hasn’t decided to open-source these templates. All it would take is a project manager to run them from OpenNTF.org and manage the code revisions, then a development team to scan the final code for security issues and take care of any ‘consistency’ issues.

Instead, we complain about these templates during every release, and IBM fails to understand that these templates are the ‘face’ of Notes to the majority of users. Here’s my challenge: IBM, you know 8.5.1 will come out, so put this template on openNTF and start an IdeaJam for enhancements requests. Sean will be your first contributor to take care of the accessibility issues! Give the big contributors a NFR copy of the server or something for their trouble. Is it really that difficult?

I was forwarded a RIM PDF on how to blackberry-enable a doc lib or discussion template (can’t remember which), complete with code samples. I just shook my head as I read it, wondering why on earth this wasn’t built into the template already, with the strong IBM/RIM partnership. They went through the trouble of making a PDF to show DEVELOPERS how to make the template work. IS that not completely ridiculous? I’m sure RIM would have rather contributed to the template to make sure it worked out of the box…

I realize someone could start an open-source discussion template, but the inclusion in the release is the key, for both bragging rights of contributors and wide-spread adoption. If it’s open-sourced, then next release you can completely ignore us when we complain about how awful they are:)

]]>