True, Patrick, but when you use "Treat content as HTML", you give up Formula Language, which can be right useful even in read mode. Let's take something like @Command([ToolsRunMacro]) -- if you use a Formula action, you get all of the data associated with the document context for free. To do the same thing in a "pure web" environment, you need to use Formula on the form to create JS-usable hooks to the current content/context, then use JS to corral all of that data and append it to a GET request to an agent. Oh, and a simple hide-when on a single button/hotspot will completely remove all of the associated functionality -- you don't need to worry about exposing "internal data" to anyone who shouldn't be using it, ever.
There is Ideal Output, and then there's using the platform's strengths. We don't have to revert to "Notes on the web" in order to create effective (and usable) web sites/applications -- we've come way too far for that. But we also don't have to throw away everything that came in the box.
*Disclaimer: oddly enough, the only times I've ever been _forced_ to get out of control with tons of hand-crafted client-side JS and super-complex HTML were when I've have to _exactly_ duplicate a Notes client application on the web. Default Domino may look like Notes on the web, but it sure don't act like it.
True, Patrick, but when you use "Treat content as HTML", you give up Formula Language, which can be right useful even in read mode. Let's take something like @Command([ToolsRunMacro]) -- if you use a Formula action, you get all of the data associated with the document context for free. To do the same thing in a "pure web" environment, you need to use Formula on the form to create JS-usable hooks to the current content/context, then use JS to corral all of that data and append it to a GET request to an agent. Oh, and a simple hide-when on a single button/hotspot will completely remove all of the associated functionality -- you don't need to worry about exposing "internal data" to anyone who shouldn't be using it, ever.
There is Ideal Output, and then there's using the platform's strengths. We don't have to revert to "Notes on the web" in order to create effective (and usable) web sites/applications -- we've come way too far for that. But we also don't have to throw away everything that came in the box.
*Disclaimer: oddly enough, the only times I've ever been _forced_ to get out of control with tons of hand-crafted client-side JS and super-complex HTML were when I've have to _exactly_ duplicate a Notes client application on the web. Default Domino may look like Notes on the web, but it sure don't act like it.