Credit goes to Michelle O'Rorke. She had blogged about how to do this, but it didn't sink in for me the first time around. You need to change the field display settings so that Domino will render the date into international format ("yyyy-mm-dd"). When the Dojo control processes the value in the field, it will format the date into the format using the i18n settings it detects in your browser.
When you submit the form, Domino will be able to process the date because of the display settings for the field. The only other thing to do is add a computed for display field that will display the date normally ("mm/dd/yyyy" for us Yanks) when a document is being read. Here's a picture of how to do the date field settings:
/A264C94305A29300852575CC005DF187/$File/DateFieldDisplaySettingsForDojo.bmp)
I did some testing and narrowed down what is happening. When you select the new Use JavaScript Control Display setting for a rich text field, Domino automatically adds dojo includes to your HTML Header. Domino's code is in blue. The code I'm adding via my own $$HTMLHead field is in green:
<style type="text/css">
@import "/domjs/dojo-1.1.1/dojo/resources/dojo.css";
@import "/domjs/dojo-1.1.1/dijit/themes/dijit.css";
@import "/domjs/dojo-1.1.1/ibm/domino/widget/layout/css/domino-default.css";
</style>
<script type="text/javascript" src="/domjs/dojo-1.1.1/dojo/dojo.js" djConfig="locale: 'en-us', isDebug: false, parseOnLoad: false">
</script>
<script type="text/javascript">
dojo.registerModulePath('ibm', '../ibm');
if (location.replace == null)
location.replace = location.assign;
</script>
<script type="text/javascript">
dojo.require('ibm.domino.widget.layout.DominoRichText');
</script>
<script type="text/javascript" src="/domjs/dojo-1.1.1/dojo/dojo.js" djConfig="parseOnLoad: true"> </script>
<style type="text/css">
@import "/domjs/dojo-1.1.1/dijit/themes/tundra/tundra.css";
@import "/domjs/dojo-1.1.1/dojo/resources/dojo.css"
</style>
My guess is the dojo.registerModulePath() function is cancelling out the dojo stuff I include. I tried to register the dojo stuff again using the following, to no avail:
<script type="text/javascript">
dojo.registerModulePath('dojo', '/domjs/dojo-1.1.1/dojo');
dojo.registerModulePath('dijit', '/domjs/dojo-1.1.1/dijit');
</script>
I found some more info on registerModulePath() here and here, but I admit I have no clue on what I'm doing. I need to submit a PMR on this.
(I converted the HTML/Javascript using this utility.)
Am I the only unlucky soul who's getting this error after working with the Domino Designer for Eclipse for extended periods of time:
/7FD62E81DA09CDA5852575CC0052CFED/$File/Notes85StandardError.bmp)
I can't believe that in 2009, with version 8.5, we still can't programmatically add bullets to a Rich Text Field!
I know, Genii has a solution for this. But how hard can it be to add simple bullet capability to the NotesRichTextParagraphStyle object? We can apply fonts to the NotesRichTextStyle objects, after all, as well as bold, underline, strikethrough, colors, ...
I've been including dojo components in my Domino form using the following $$HTMLHead field:
/4D9CAED2A27002E0852575C700626165/$File/LoadDojo.jpg)
However, when I change a Rich Text field to use the new "Using JavaScript control" setting, the dojo rich text area appears, but none of my other dojo controls (FilteringSelect, ComboBox, TextArea, etc.) will load. Nice...
One client I'm working with currently has a few users who are road-testing the Notes 8 Standard client before it is rolled-out throughout the company. One of the users mentioned to me that the Search button is missing from the View toolbar. This button is still there in the Notes 6 and Notes 7 clients:
/EC465085DD8F640285257586004F6D9E/$File/View Toolbar-7.jpg)
However, the same button is not available in the Notes 8 Standard client:
![]()
Even more interesting is that the button is still visible in the Toolbar Preferences dialog:
/4EEAD822DF222B8C85257586004F9922/$File/Toolbar Preferences-8_0_2.jpg)
Well, it turns out that the user now needs to enable the new Search toolbar for Notes 8 Standard:
![]()
Another change the user mentioned is how unread mail messages now appear in black bold typeface instead of being "red".
Since Notes 8 has been available since August 2007 (over 1 & 1/2 years), I'm sure that these items are common knowledge to everyone reading this. I guess my reason for bringing this up is that the user in question (and the company he works for) has been using Notes since version 4.0. I can see a lot of initial confusion when people are migrated to the new client. In Notes' defense, this UI confusion won't be any different than switching to the new Vista interface or the Office 2007 "ribbon".
Just out of curiosity, has anyone seen a document that compares the Notes 7 (and prior) UI with the Notes 8 (and 8.5) UI? I'm thinking of something that has screen shots akin to before and after photos...
Su | Mo | Tu | We | Th | Fr | Sa |
|---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | |||
5 | 6 | 7 | 8 | 9 | 10 | 11 |
12 | 13 | 14 | 15 | 16 | 17 | 18 |
19 | 20 | 21 | 22 | 23 | 24 | 25 |
26 | 27 | 28 | 29 | 30 | 31 | |