Wednesday, August 28, 2013

And the correct answer is...

Last time I wrote about Designer Help.  One reader correctly pointed out that if I wasn't so lazy, I just had to add the word 'formula' to my search string.  An even better answer came from Julian Robichaux at his session at MWLug last week.  It is to set the search scope.

It is not real intuitive, but click the link, select 'Search only the following topics', click 'New', name your list, and select only the stuff you want.  I always wondered how items for Workbench and Sametime showed in my search results.

Monday, August 19, 2013

This is not a trick!

Go to Help Contents with your Social Edition designer client and enter '@Member' into the search box.  The old, familiar, formula language reference is the 15th entry on the third page!  And why did I notice this?  I use Help all the time.  I mean, does the value or stringlist come first?  Depends on the function.  And whats the difference between @IsMember and @Member?  If I had to remember all this, I might not have room to remember my wife's cell phone number, which is pretty important.

So have you noticed the reformatting of the help file?  It looks like a lot of work went into this, but I wish they spent more time improving the run time error handling engine.  I mean, really - "Object variable not set"? Can you please tell me what variable?  And they same for "Type mismatch".  Although I do this so often I tend to find this pretty quickly.  And here is where the help files could be improved - the examples are too simplified.  They use constants in a lot of places where real developers might use a variable.

And I know everyone is focusing on xPages, but I still work with a lot of clients that have traditional Notes apps, and need to have small changes or even big fixes.  So, I still use help on a regular basis so I appreciate any changes, and keep them coming.

Wednesday, April 24, 2013

I am sorry I am a user...

Because someone can get a patent for 'slide to the right' to unlock.  My Android phone used to be 'slide down' to unlock to get around this patent.  I guess too many people slide their phones in their pockets and 'butt dialed' too many people so now it is 'slide up' to unlock, meaning my phone is now in my hand.  All of this is completely arbitrary, non-intuitive, and in no way inventive or unique!  But to be safe, I have filed a patent for a motion sensitive method of unlocking a phone which involves a one finger salute.  I am going to be rich!  It is only a matter of time before you can just wave at your phone, or point at it, or whatever, to unlock it, so I am just getting ahead of the curve.

My real point?  The 'X' to close a window on Microsoft machines is on the top right, and on the top left for Apple machines.  WTF?  Did studies show too many users closed their windows when they were trying to get the Edit or File menu?  A user interface should be designed for consistency so users don't have to think about how to accomplish a task.  Is it a button?  An action menu item?  A tool bar button?  What does that icon mean anyway?  All I am saying is spend a few minutes thinking about your buttons and actions.  Does 'Close' do a save and close?  How do I get out of this document? Why is it different than all the rest?

This is one of those issues dating back to the early days of Notes.  Hitting ESC closes a window.  So does clicking the 'X' on the top.  So do I need to include an action to close a document?  Well, if you do it for one form, you have to do it for every form.  Consistency is all it is cracked up to be.

Make it easy for your users to accomplish the task your application is supposed to help them achieve, and everyone will be much happier!  It is not Notes that sucks, it is your UI!

Friday, January 25, 2013

And for those of us not going to Connect 2013...

Which pretty much means this won't apply to anyone who reads this.  In my experience, the people who need the most help don't tend to seek it out in either blog posts,, any of the forums or at user group meetings.

In any event, I was recently asked by a client why I sent him design changes in an NSF versus an NTF.  This is a topic I dealt with rather frequently when I was a Technical Director at Teamstudio.  Many people think it has to do with design inheritance, but it doesn't.  The biggest differences are an NTF will not show up in an 'open database' dialog box, hiding it from every day users.  Also, any scheduled agents will not run.  And lastly, design elements in an NTF can not be previewed in a web browser.  Which all make an NTF a great way to manage design changes.

But from an inheritance view point, that is controlled at the database level by the fourth tab on the properties dialog, indicating either inherit from template or it is a template.  At the design element level, it is controlled by a setting in the design tab of the elements properties.

At design refresh time, either manually invoked or by the Design task, databases are refreshed at the database level by the inherit from setting, and then at the design element level.  And as was the case with my client, I was making modifications to the mail template, and wanted to be sure the process was repeatable for the next release of Domino.  So my changes where in a database that could be an NSF or NTF (but best practice says design elements should be in an NTF).  These changes were used to refresh design elements at the element level in the mail template.  This results in a cascading design refresh situation - the template gets refreshed from the custom design element database, and then the user mail files get updated by the mail template.  Note that this element level inheritance is not inherited.  So, the user mail files get ALL their design changes from the mail template, not some from the template and some from the custom design element database.

And in a final comment about design inheritance, a review of what databases are being used in your environment (a common precursor to upgrades, server consolidation, or migration from Notes), needs to include design element level inheritance, and not just database level inheritance as shown in the database Catalog.

I usually recommend a manual refresh of the template from any updates I send, and then allow the design task to refresh all the user files.  This is the cleanest way to ensure updates take place in a controlled manner.

I hope this helps.  And if you are going to Connect 2013, have a great time!