: 1695 | 40754 | 5105
| 19 Aug 2008 | David Killingsworth | Improvements for the Diretory Catalog (configuration form) To be more clear and articulate what the author of this idea is requesting.... The Pull down tabs/buttons in the Red Boxes in the diagram above currently DO NOT exist. He's asking for pull down's so that we can select fields from the directories directly without having to manually type the field name in. |
| 19 Aug 2008 | David Killingsworth | Improvements for the Diretory Catalog (configuration form) Totally agree. |
| 19 Aug 2008 | Henry Ferlauto | Meeting Rooms & Conference calls That's a good one! Should keep a few developers employed for a while. |
| 19 Aug 2008 | Jordan Tenjeras | Enforce (or advise) the need for a default view Ben, I hear what you're saying but I'd argue for not making the other functions require a default view in the first place! This seems a very strange design choice to me but someone smarter than I created the product. Given the design decision has already been made I tend to agree with a warning as a minimum. |
| 16 Aug 2008 | Sjef Bosman | Linux support for Quickr Domino version And apparently it's still not there... |
| 15 Aug 2008 | Theo Heselmans | Option for a Field to have its content selected when getting focus @Joseph: your solution does not work in Notes, and it only works on clicking. I need a Notes solution, that also works when e.g. tabbing. There is a 2 line solution, but I don't want to add it to each field. BTW this works: Sub Entering(Source As Field) Dim ws As New NotesUIWorkspace Call ws.CurrentDocument.SelectAll End Sub |
| 15 Aug 2008 | Morten Clausen | Emailing a subform from the current UI document RenderToRTItem is your friend with a little fiddling of the Form-field, I think. I seem to recall doing something like this with a (possibly computed) subform on a very simple form: changing the Form of the document-to-be-sent, rendering the changed document to an RT-item on another document and mailing that. Long time ago so details are a little fuzzy... :-) |
| 15 Aug 2008 | Morten Clausen | Private Views - Inherit Design Changes Even better would be a way of tying the design of the private view to a public view, so that the private view would just be an index that had to be combined with a view design to be a "real" view. That way no upgrading would have to be done, just reindexing if the parent design changed. OK, could be horrible performance-wise, but the current implementation is close to useless anyway. :-) |
| 15 Aug 2008 | Joseph Hoetzl | Option for a Field to have its content selected when getting focus onClick event of the field: this.focus(); this.select(); A lot of work? |
| 15 Aug 2008 | Joseph Hoetzl | Implement onChange event on all fields in the Notes client Wow, was just going to post about this one! "This event occurs when the field loses focus and its value has been modified since gaining focus." Why do we need to lose focus...kind of defeats the name, it isn't OnChangeAndMoveOff! |
| 15 Aug 2008 | Rob Porter | Hide-When Formulas - Improve visibility in Domino Designer To avoid conflicting with Pass Thru HTML background shading, perhaps a small indicator in the margin to show that a "hide when" formula has been applied to a paragraph would be best. The indicator could be a different colour depending on the type of "hide when" formula. For example: * blue if one or more of the "hide when reading" checkboxes is selected * yellow if one or more of the "hide when editing" checkboxes is selected * red if one of the "hide paragraph from Notes/web browsers/Mobiles" checkboxes is selected * green if it has a "hide when formula" * black if various combinations of the above has been selected. |
| 15 Aug 2008 | Rob Porter | Private Views - Inherit Design Changes The problem with using @UpdateViewDesign is that with "private on first use" views the source and target view names are just strings and the private view created when a user first opens the "private on first use" view has the same name as the "parent" view. So if your "private on first use" view is called "Customers by Name" the private view created by the user is also called "Customers by Name". The formula to update the private view's design would look like this: @UpdateViewDesign("Customers by Name"; "Customers by Name") Unsurprisingly this doesn't work. The "Upgrade Folder Design" agent in the mail template uses @UpdateViewDesign but because it's working with folders which have different names to their "parent" folders the formula is able to function correctly. It would be ideal if the next time a user opens a database after its design has been refreshed, the designs of their private views were automatically updated. If that could happen then we wouldn't have to resort to workarounds (hacks) to solve this issue. |
| 14 Aug 2008 | Anjaneya Prasad Banda | Emailing a subform from the current UI document Good Solution I got same requirement This is very helpfull when the form contains tabbed tables or subforms or any big content form and we need to send part of it. Prasad |
| 13 Aug 2008 | Ben Poole | Remember "show images" for email addresses Totally agree; not hard to implement, and something that other email clients do (e.g. GMail, Mail.app). |
| 13 Aug 2008 | Vitor Pereira | Remember "show images" for email addresses Agreed and should also be possible to allow a mail domain not just one address. |
| 13 Aug 2008 | Scott Cochrane | Separate Design Client From Notes Client Sound idea |
| 13 Aug 2008 | Robert Jones | Better rendering when pasting in web content I wonder whether a heuristic approach might be appropriate here. One of the most annoying things I find is that when I copy a short phrase or perhaps a code of some sort from a web page, then paste it into an e-mail it first takes an absolute age, then renders it with a bunch of completely inappropriate formatting which is hard to remove. I then have to delete it and use Paste-special to get the plain text. My gut feeling is that if the total word count of the content to be pasted is less than say 5 then it's much more likely that the user wants the text to be formatted like the rest of the email being typed! They could always use Paste-special to retain the formatting if that's really what's wanted. |
| 12 Aug 2008 | David Killingsworth | Server Policies This idea has some weight, but consider these points. You can already configure the * server configuration document which new servers will inherit their settings from. Individual configuration documents will override any settings that are set in the * configuration document. The problem I see here is that anyone can go to any server and modify a notes.ini file. It might be what you are suggesting is that we do away with notes.ini and move all configurations to configuration documents and make them more granularly controlled. I'm giving this a neutral vote. You've got a good idea, but I think it requires a major change to the way the Domino server is configured. Some organizations may want many of their servers to be exactly the same. Some organizations may need to have each server configured completely differently. Edit: After second thought, I'm promoting this. Sometimes, it agitates me when we set a notes.ini setting in a configuration document. Then we remove that notes.ini setting altogether from the configuration document. We have to go in and manually remove that notes.ini setting for it to be removed from the server. This can sometimes leave unwanted debug settings, etc. behind. |
| 12 Aug 2008 | Stephen Bailey | Ability to do combined search in Mail and Archive Mails Agreed, but Notes should be able to do this anyway - after all, the database knows where the archive is, so it should be feasible to extend the search facility to cater for this. |
| 12 Aug 2008 | Chad Martin | Emailing a subform from the current UI document It doesn't have to be a subform. It can be any portion of the current UI document which the user wants to email. |
Buy IdeaJam
IdeaJam can be easily installed, setup and customized by your company.
Learn more >
Introducing IdeaJam
IdeaJam is a place where people can post and share their ideas, and gauge the marketability, popularity and viability with input from others.
When an idea gets posted, others can help promote or demote the idea and provide comments. Popular ideas will bubble to the top.
Make your opinion count.
