IdeaJam(tm) feed for Doug Finner

Notes Client / Other Database Applications: Allow shift click for multi doc select

Thu, 01 Nov 2007 11:12:53 +0000

Author: Doug Finner
Tags: selection
Idea:

When you read the 'why notes sucks' sites, this one shows up a lot. Every other multi-row-like app in the world allows users to click a row, scroll down to some end point and shift click to select a range of items. The 'click and drag' thing confuses folks.

re: Allow shift click for multi doc select

Thu, 01 Nov 2007 13:35:50 +0000

Author: Alan Lepofsky
Comment: This is available in Lotus Notes 8

Domino Designer / : Allow user defined 'property box on/off' setting

Thu, 01 Nov 2007 11:19:54 +0000

Author: Doug Finner
Tags: property
Idea:

I've watched lots of folks do designer presentations and in every case I can think of, when they open a view or agent, the first thing they do is close the property box. Every time I open a view or agent, I close the durn thing. Either set it to 'off' or provide a setting that lets me decide if I want it on or off by default.

re: Allow user defined 'property box on/off' setting

Thu, 01 Nov 2007 13:02:02 +0000

Author: Bruce Elgort
Comment: Yes - Closing that box EVERY time I open up designer is second nature at this point. Thanks for sharing your idea Doug.

re: Allow user defined 'property box on/off' setting

Thu, 01 Nov 2007 13:45:36 +0000

Author: Voytek Wicisnki
Comment: Add following to your notes.ini:

DesignNoInitialInfoBox=1

It will prevent designer to open property box by default.

re: Allow shift click for multi doc select

Thu, 01 Nov 2007 13:43:24 +0000

Author: Keith Brooks
Comment: because Lotus pulled out the gutter!

re: Allow user defined 'property box on/off' setting

Thu, 01 Nov 2007 12:53:38 +0000

Author: Matt White
Comment: Wow, what a great idea Doug. Couldn't agree more. Same applies to views as well.

re: Allow user defined 'property box on/off' setting

Thu, 01 Nov 2007 14:53:48 +0000

Author: Phil Randolph
Comment: I would say it can Bruce!

Wow, how cool is that, an answer to a pretty important question in less than 3 hours! Amazing..

re: Allow user defined 'property box on/off' setting

Thu, 01 Nov 2007 13:52:44 +0000

Author: Alan Lepofsky
Comment: LOL! Voytek, you just beat me to posting that!

re: Allow user defined 'property box on/off' setting

Thu, 01 Nov 2007 14:12:36 +0000

Author: Bruce Elgort
Comment: So can this idea be withdrawn now?

re: Allow user defined 'property box on/off' setting

Thu, 01 Nov 2007 14:06:27 +0000

Author: Matt White
Comment: Cool, never knew that. Idea Jam has earned its keep for the day ;-)

re: Allow shift click for multi doc select

Thu, 01 Nov 2007 19:11:00 +0000

Author: Mika Heinonen
Comment: Oh nm, it's working correctly, I forgot to hold down Ctrl+Shift at the last step. Where's the Edit/Delete button for replies?

re: Allow shift click for multi doc select

Thu, 01 Nov 2007 19:09:12 +0000

Author: Mika Heinonen
Comment: It's still not working as it should in Notes 8, for example try this:
Select doc 1, hold Ctrl hand select doc 3, hold Ctrl and select doc 5, now hold Shift and select doc 10. It should keep doc 1 and 3 in the selection also, but it just kills their selection and selects doc 5 to 10.
I need to add this to my "Why Notes Sucks" list also :)

Domino Administrator / Security: Make 'can't run agents' include 'can't create toolbar code'

Fri, 02 Nov 2007 16:24:25 +0000

Author: Doug Finner
Tags: action acl security
Idea:

I can define who can and can't create @Function and LS code - very cool.

Users can, however, create custom code in toolbar. I may want the user to only access dbs via my interface but they can step nicely around any restriction I have if they create code in a button.

This restriction could live global, at the db level, or in both places.

re: Make 'can't run agents' include 'can't create toolbar code'

Fri, 02 Nov 2007 17:10:14 +0000

Author: Matt White
Comment: From a developers point of view I whole-heartedly agree. But from a power-user's point of view it would really be a pain in the butt for me. I'm going to demote on the basis that anyone who can write an @Formula and put it in a smarticon is probably smart enough to know what they are doing.

Matt

re: Allow user defined 'property box on/off' setting

Thu, 08 Nov 2007 08:49:54 +0000

Author: Ninke Westra
Comment: completely forgot about that one.

re: Allow shift click for multi doc select

Fri, 16 Nov 2007 21:08:17 +0000

Author: Tom McArthur
Comment: Mika, you were right, it does not work as it should. For example:

click the check column for doc 1, ctrl-click the check column for doc 3, click once on doc 5 so the selection box is on it (but no check mark), now ctrl-shift-click the check column for doc 10. Since doc 3 is the last one checked, 3-10 should now be checked, but ctrl-shift-click checks everything from the selection box down, not from the last checked entry down - in other words, doc 4 should be checked, but it is not

re: Make 'can't run agents' include 'can't create toolbar code'

Thu, 29 Nov 2007 04:57:50 +0000

Author: Richard Schwartz
Comment: I'm afraid that it just becomes an arms race. Block users from creating toolbar code and they create button code in the rich text body of an email message! Block that, and they create a VB program or Java program -- or they download someone else's VB or Java program. Find a way to close that down, and someone's going to write Notes API code -- not a one-off thing, but a tool that allows users to write and execute their own programs against your data.

re: Make 'can't run agents' include 'can't create toolbar code'

Fri, 09 Jan 2009 19:39:13 +0000

Author: Christopher Baier
Comment: I have 20 custom toolbar buttons. Don't take those away from me. People who can create buttons are probably smart enough to know what they are doing.

re: Make 'can't run agents' include 'can't create toolbar code'

Tue, 10 Feb 2009 19:38:04 +0000

Author: Graham Richards
Comment: You would have to change the underlying architecture of Notes to force people to only access your database documents through your UI.

Notes was written so that the UI is only one of many possible ways to interact with a database's content.

Are you going to prevent user-written databases from talking to yours ?
Are you going to stop any NotesSQL queries from talking to your database ?
Prevent users from using NotesPeek or other 3rd party tools ?