Lotushints

Lotus Notes tips & tricks you always hoped you will not need

Entries for the ‘Code optimization’ Category

Design patterns – Part 3: Singleton pattern

The simplest way to describe singleton class is to look at the definition: The Singleton Pattern ensures a class has only one instance, and provides a point of access to it. So why would you need that? Well, there are many objects you only need one of in your application (e.g. Logging, text trimming, for [...]

Lotus Developer 2008 Europe Report

Day 0, Check-in The flight was OK, check-in without issues and registration to the conference was prompt, which scared the hell out of me. You know what they say. If everything goes right, something is bound to go terribly wrong. Conference registration people were kind enough to give me shoulder bag with loads and loads [...]

Design patterns – Part 2: Decorator pattern

For those, skilled in Java development, Decorator patterns are nothing new, as they are quite common in Java, i.e. FileInputStream with it’s decorator BufferedInputStream class. The definition says: The Decorator Pattern attaches additional responsibilities to an object dynamically. More theoretical background can be found on Wikipedia.

Design patterns – Part 1: Strategy pattern

One of the simplest and most commonly used patterns is definitely strategy pattern. We cannot pass a boring definition, so here you go: The Strategy Pattern defines a family of algorithms, encapsulates each one, and makes them interchangeable. Strategy algorithm vary independently from clients that use it. You will find out that all strategy pattern [...]

Multilingual applications

The other day, at work, there was a discussion about possible ways to create an application that could easily be ported into different languages. At the end, we got stuck on two possibilities. One was to simply make a new copy of the database and translate all design elements. The second one was to have [...]

Design patterns and LotusScript

Design patterns are here to ease work to us developers. They present already made solutions to known problems. I will not go into philosophical debate about why they are practically not used in LotusScript. Instead, in future articles, I will try to present basic design patterns translated to LotusScript. For those that are already interested [...]

Object-Oriented development in LotusScript

Even though IBM posted an article regarding OO development in LotusScript back in 2001(!) on their developerWorks web site, I am still amazed as to how many Lotus application developers choose to avoid using custom made classes today.