... where, while one of your hosts is zoiky post medication for a pullled back muscle, we discuss the following:
Geek Speek: Advanced Notes Client UIs through separation of UI and document data.
The WTF?! of the Week/Project Broker Update
Mini-Tip
Community News
Show Notes
Domino Flex Fields
http://www.dominoguru.com/pages/DominoFlexFields.html
Lotus Notes Client Wizard - Components Example
http://www.dominoguru.com/pages/wizardcomponents.html
(more to come)
5 comments:
The most compelling application for xpages isn't really forms showing data from other forms -- but with iterations over views.
In essence, you get to treat view rows as subforms. That's the simplest way to grasp it. You're creating a subform that's a wrapper for a row.
Doclinks contain the ViewUNID as well as the DocUNID. So when you send a link, the user that clicks on the link opens that document THROUGH THE SPECIFIED VIEW.
This was done back in Notes version 3 for precisely the reason you mention on the 'cast: so that the UI will use the Form formula in that specific view.
If you specify the "default" view (UNID of 0) then the document will still open, but using whatever form formula exists for the default view (usually none at all.)
It is possible to manipulate the UNID of the relevant view. That's why we have the NotesRichTextDoclink.viewUNID as a read-write property.
Great show again. Tx for that.
One major comment: I didn't always agree with the separation of UI from data: e.g. A Notes view does not contain data, but is a UI element, if the user has direct access to it. Don't compare views in Notes with views in an RDBMS. In a relational db it's a twist on table-data.
Notes has its way of doing things, so don't try to force it into a .net or java development environment.
Another good episode guys. And thanks for cutting down on the time. The length of the second show made it much easier to find the time in one sitting to listen to the show.
Nice job! Looking forward to more
Post a Comment