Lotus Domino. Making some stuff easy, and some fairly obvious stuff stupidly convoluted.
I have a subform which has a version number in it. It’s in the subform so it only needs to be changed in once place to show up in all of the site design where it needs to be, and it’s not in a document because they don’t travel with the design. So far so good, you might think.
Pages do not support subforms. Or shared fields. Or any other way of incorporating reusable design elements. So I’d be better off using a form. But I can’t use a form, because you can’t specify a form as the default element to open when the application is opened, and short of reconfiguring every other bit of the intranet which links to all the deployed instances of this app, the only thing I can think of to do is put a redirect into the onload event of the page so that it redirects to the form version, which has the subform on it. This is a nasty hacky icky brittle way of doing it but I cannot think of any other way.
Sometimes being a programmer can be immensely rewarding. This is a million miles away from being one of those times.
EDIT: Thanks to Matt for pointing me in the right direction for the Notesy workaround for this. It’s still a bit of a hack but less so than redirecting via javascript in the browser. I feel slightly happier now.
2 Responses to “Forehead/Wall Interface Scenario”
Sorry, the comment form is closed at this time.
for a Notes client app a frameset would do. Put the form inside. On a web app it is semi cool… use the frameset and make sure that all your URLs on the page have target=”_top”. Then you break free of the frame.
What did Matt suggest?
Where we eventually wound up was at $NavigatorTemplate, but neither of us could remember exactly what they were called (and I, clearly, couldn’t remember them at all).