scott cochrane

Category Lotus Notes
Bookmark :              

Well the install didn't go too smoothly - mostly because I forgot that the beta's don't support upgrade over a previous version.  So then removing the old version was a pain ... blah blah blah .. then finally got it installing.

Got one error during the install about not being able to unregister a component - probably due to my hacked uninstall .. but otherwise the install was fine..

So then I got the stop watch ready (could have done with a drum roll here) - waiting for the blistering speed of the start-up ... but then it had to run some configuration stuff and my myriad of ids / locations / organisations didn't make things any easier .. but it got there.  So then shutdown and restart - no it wouldn't - hmmm.

So ok, one quick machine restart later and I was starting Notes cold again.  Started ok, but the speed certainly wasn't blistering (over 2 mins)

However - closed it (and I swear it shutdowns quicker - the processes are gone within 5-10 seconds), then hot-start - and damned is that quick.  

I would often have not closed notes because of the time to restart - but if that hot-start is consistently that quick (and it seems to be) then closing it really isn't an issue.  I'm a little disappointed so far with the cold-start - I can't discern any real difference in the start-up time, but I'll reserve complete judgement on that.

I'm off to find some other new features now..

[ Machine is Intel Core 2 1.8 with 2Gb RAM ]

Posted by Scott Cochrane At 11:27 AM Location Glasgow | Permalink | Comments (0) | TrackBacks (0)

Category Lotus Notes Design
Bookmark :              


There is often a lot of talk around the complicated parts of the Lotus Notes - agents, scripting, js frameworks, OOP etc.  So I thought I'd try and run a few posts on the absolute basics of Lotus Notes development (and for the cynics amongst you, yes your right, it makes for an easy blog topic ).  

So since its the absolute basics I'll probably avoid anything relating to serious web design and maybe only run into LotusScript later on.   And your more than welcome to shoot it to bits as well.

So number 1..

Always use aliases on design elements and reference the alias in your design - not the actual name. You can then change your view names without changing references in dblookups, change form names without changing view selection criteria.  If you don't have tools like Teamstudio's Configurator this is damned useful.

Its often good to name the aliases with that prefix relative to the design element, e.g. viewPeople / vwPeople / frmAccount, particularly as this makes every alias within the application unique.

Despite saying I'll avoid web design .. I'll break that rule straight way:  Aliases allow you to refer to the design elements via URLs without a URL command as long as you name the aliases uniquely within the database (sorry - slap my wrist) - application.  So http;//www.mysite.com/somedb.nsf/frmCompleteMe will open the form frmCompleteMe without using ?OpenForm on the end.

The only place I might break this rule is when importing documents from applications where you are then going to use a copy of the other applications form design .. e.g. the Memo form in the mail file doesn't use an alias.  But equally you could always change the form name on the document and use an alias.

1 down .. next time, fields.

Posted by Scott Cochrane At 11:15 PM Location Glasgow | Permalink | Comments (2) | TrackBacks (0)

Category SQL
Bookmark :              


Normalisation*  isn't really something you worry about in Notes - although you might look to store data in response documents where you have multiple entities ( e.g. personnel reviews) related to  parent entity (e.g. a member of staff).

In the SQL world normalisation means avoiding redundant storage of the data but you relate the rows of data with keys - similar I guess to the relation between a parent and response document in Notes where the parent document UNID is the key.   In a SQL database you normally work pretty hard to keep your data normalised but I was discussion this today with someone because we have a dilemma around how normalised we should keep the database.  On this front I found this blog entry with a link to a presentation on the Flickr architecture.  The bottom line is that if you are prepared to put up with the down-sides, then go for it just stuff the principal.  This is also backed up somewhat on Wikipedia where it makes the point that for online analytical processing applications denormalised data structures have long been used to improve performance.

In our situation the option before us is to duplicate storage of some order data so that we can to guarantee that we can replicate the order at any point in the future.  I think thats what we will be doing.

So that is an attitude re-adjustment for me today - normalisation is NOT a religion.


* Normalization for the US English folks

Posted by Scott Cochrane At 2:27 PM Location Glasgow | Permalink | Comments (1) | TrackBacks (0)

Category Lotus Notes
Bookmark :              


Haven't had it for years and after a few months of use and I thought I'd lost my right arm when type ahead failed to function:

   

A restart did the trick - I hope 8.5 beta 2 will be just that bit more stable (although beta 1 has hardly been bad).  Later this week from what I hear ....

Posted by Scott Cochrane At 4:33 PM Location Glasgow | Permalink | Comments (0) | TrackBacks (0)

Category Blogsphere
Bookmark :              


A friend told me that they had commented recently and that the comment hadn't appeared (thanks Matt).  With some investigation today it turns out that with co-comment enabled on the configuration ANY comment was being flagged as spam.  I've logged the bug on OpenNTF but for now the easiest work around is to disable co-comment - does anyone use it anyway?

So for anyone that commented recently, sorry and I wasn't ignoring you - honest

Posted by Scott Cochrane At 12:51 PM Location Glasgow | Permalink | Comments (6) | TrackBacks (0)

Category Lotus Notes
Bookmark :              


I was looking at this features list for Lotus Notes/Domino 8.5.  The ID valid looks quite compelling and I quote:

"Policies are used to assign users to a vault, and copies of the user IDs are uploaded from Notes clients to the vault automatically after authentication with a server once the policy has taken effect. "

If its as simple as that, is this a major part of the business case for 8.5 or maybe this is the business case for 8.5?

Now not being a 1000+ users administrator I don't really know, but I always got the feeling that id management was a pain in the butt.  So what are the thoughts out there - how many hours is this going to save per 1000 users or so?

Posted by Scott Cochrane At 12:43 PM Location Edinburgh | Permalink | Comments (0) | TrackBacks (0)

Category Lotus
Bookmark :              


I was looking a the list of Lotus wikis and realised that there isn't one for Notes client development best practice.  Is this reflective of the fact that nobody is doing Notes client development any more ( not likely) or Notes client development doesn't deserve a best practice guide .... or just isn't sexy enough for a wiki ??

Or am I missing a Notes Client development wiki out there ?

Posted by Scott Cochrane At 10:53 AM Location Edinburgh | Permalink | Comments (0) | TrackBacks (0)