Client/Browser parity for ComboBoxes and ListBoxes 
Use this IdeaSpace to post ideas about Domino Designer.

: 7
: 12
: 5
: Domino Designer
: browser, client, development
: Samuel Allen484 30 Nov 2007
: / Email
I would really like to see the combobox and listbox (and a @%$#-ton of other objects behave the same (or at all) in a browser or the client.  If the whole concept of developing for Notes and Domino is to speed developement time, then I shouldn't have to build form and view objects twice because neither one works in the client AND the browser.

1) Slawek Rogulski9372 (30 Nov 2007)
So you really want to build once and use on the web and in the Notes client. Admirable goal. Isn't it this the original promise when the HTTP task got grafted onto the Domino server?
Wold be nice? But I would rather see the Notes client developed to its full potential as a great GUI builder with a modern GUI not hampered by legacy issues. So I'd rather that effort not be held back by web compatibility.
2) Thomas Bahn4937 (30 Nov 2007)
Not every application is for Notes client AND browser (and IMHO most are not).

The browsers only have a VERY limited amount of input elements, which are constructed to run in every browser, in every OS and in a HTTP environment (request-response-interaction).

The Notes client - like every "fat" client - has the CHANCE to use more, nicer, richer, and more effective elements. They can be build highly interactive (think of input translation and validation accessing "external" data that is information stored outside of the current document).

Would you really want to sacrifice this benefit for a minority of apps? I definitely not.
3) Axel Janssen6869 (30 Nov 2007)
Lotus has no command over html standards and Lotus can't eliminate existing design elements of the notes client for obvious downward compability issues.
4) Samuel Allen484 (03 Dec 2007)
So introduce new modules with no legacy dependence which have the mechanisms which people have to manually hack into their "Web/Notes Version" in order to get the same effect. I'd be happy with that. How many guru blog posts have been spent detailing how to get a certain "client feature" on the web. Such articles have been done dozens of times. Why can't we normalize one such process that IBM endorses and make it the default behavior.

The applications become so needlessly complex by having to build the logic of the interface 3-4 times depending on how you're accessing the application. Personally I'd rather have a Web-Based Stylesheet/Scripting INSIDE the client allowing for a superset of the web standards functionality for the rich experience than have the client generate different code that the browser understands.

Build on top of the standards that exist instead of akwardly connect two different paradigms. IBM likes open standards don't they? :P

Perhaps I should rephrase the Idea.


Welcome to IdeaJam

You can run IdeaJam™ in your company. It's easy to install, setup and customize. Your employees, partners and customers will immediately see results.

Use IdeaJam to:

  • Collect ideas from employees
  • Solicit feedback and suggestions from employees and customers
  • Run innovation contests and competitions
  • Validate concepts
  • Use the power of "crowd-sourcing" to rank ideas and allow the best ideas to rise to the top

IdeaJam™ works with:

  • IBM Connections
  • IBM Lotus Quickr
  • Blogs and Wikis
  • Websphere Portal
  • Microsoft Sharepoint
  • and other applications.

IdeaJam has an extensive set of widgets and API's that allow you to extend and integrate IdeaJam™ with other applications.

Learn more about IdeaJam >>

IdeaJam developed by

Elguji Software Logo