Comments

1. • 
   • Alan Harris
   • Wed 11 Nov 2009 03:41 AM

   Hi Jake,

   Tommy Valand talks about it here...

   http://dontpanic82.blogspot.com/2009/09/enhanced-html-generation-in-domino-85.html

   regards,

   Alan

   Reply

   1. • 
      • Jake Howlett
      • Wed 11 Nov 2009 04:06 AM

      Aha. Don't know how I missed that. Normally try to read everything he writes.

      So, it just closes HTML tags then.

      What I really want is a way to stop Domino creating form tags when they're not needed.

      Reply

      Hide the rest of this thread

      1. • 
         • Alan Harris
         • Wed 11 Nov 2009 04:49 AM

         Hi Jake,

         I don't think you can. Aren't they integral and intrinsically

         inbuilt into domino?

         More than happy to be wrong about this 'assumption',

         even though all docs I've ever read state this.

         regards,

         Alan

         Reply

      2. • 
         • Tim Tripcony
         • Wed 11 Nov 2009 06:58 AM

         In an XPage, that's easy - there's a boolean "createForm" attribute that does precisely what you'd expect: if it evaluates to false, no form tag is generated.

         There's just one small problem: that also tells Domino you don't want to rely on built-in platform features for any data interchange. This means that it breaks any server-defined event handlers (as opposed to event listeners you're manually attaching in client-side JavaScript), because it doesn't know where to post the event data (which I guess makes sense for full refreshes, but for partial refresh is bizarre, since that's XHR anyway).

         So if your interface uses homegrown XHR (manually constructed posts with endpoints and postdata of your own choosing) or is totally non-interactive (aside from very basic navigation), this is a handy setting. Otherwise the reduction in platform functionality is not worth whatever was perceived to be beneficial about suppression of the form element... especially since the types of use cases where we used to want multiple form tags are now dead simple in XPages (e.g. having a site search feature that's handled separately from submission of site content).

         Reply

      3. • 
         • Rob
         • Wed 11 Nov 2009 04:17 PM

         I think that's what XPages is for; better control over everything that's generated. I could be wrong as I haven't actually written any XPages yet.

         Reply

Your Comments