Apr 29

Mein Status

Auf dieser Seite passiert im Moment sehr wenig, und der einfache Grund dafür ist: Ich habe sehr gut zu tun.

Ich baue weiterhin mobile Apps für Android und iOS mit Appcelerator Titanium, mache Domino XPages mit HTML5, JavaScript, Framworks etc. und mache auch noch klassische IBM Notes Entwicklung.

Ansprechbar bin ich am sichersten via E-Mail, siehe Adresse rechts.


Jan 02

New toy: Sony HX-50V and some photos of Hvide Sande, Denmark

I’m in Hvide Sande, Denmark at the moment testing a new photo camera I got for christmas.
Hvide Sande is at the west coast of Denmark and has a harbour, a nice coast with beaches and dunes. There is a lot of wind each day which produces notable waves rolling onto the mole and beach. All of that produces good opportunity for interesting photos, unfortunately it’s very cloudy, too, so the light is far from being perfect.

Nevertheless I got some photos that are not too bad, have a look here: Hvide Sande, Denmark photo album

Camera: Sony HX-50V

Some photos are pretty washy because I used a wrong setting in the camera, there are still some options I have to get used to. Beside that, I’m very happy with the Sony.

One killer feature for me is the ability to transfer photos from the camera to my iPad or Mac wireless via Wifi: I get home after shooting, enable Wifi on the camera, connect my iPad to the camera’s WLAN network, open an App and then I can transfer photos to the iPad.
Alternatively I can connect the camera to my standard WLAN, push a button on the camera and then it transfers photos to my Macbook to a predefined folder. Very convenient!

And while the HX-50V is relatively big, it’s still small enough to easily take it with me when we go out for a walk. I don’t need a bag or something.

Amazon will tell you about all features of the Sony, my personal favorite features are:

  • Various options to shoot good photos in low light situations (I use a flash very seldom)
  • If I have to use the flash, there are options to keep nice, warm light even with a flash
  • Incredible 30x optical zoom
  • Enough resolution to use digital zoom and still get an acceptable photo
  • Optical and digital zoom combined result in 60x zoom – in a small camera which you can easily carry around
  • Dedicated rotary knob to adjust exposition
  • A lot of manual control if needed, and good automatic modes for everyday situations
  • Very good video support (1080i as MP4, otherwise up to 1080p)
  • Build-in GPS sensor for automatic geotagging
  • Transferring photos via Wifi
  • remote control of the camera via Wifi and iPhone/iPad App
  • Good UI, all options have a short explanation right in the menu and there is even an online help system

I’m really just an amateur photographer, and I would not have use for a big DSLR camera. On the other hand, a simple compact camera or the iPhone doesn’t suit me anymore, too. The Sony HX-50V is perfect for me, and I can recommend it.


Aug 16

Domino To Go 2.0 will bring an new, Alloy based demo app, single category synchronizing, changing NotesDocument items locally and…

Note: this post has been migrated from another blog. Some links may be broken.

At the moment, Domino To Go 2.0 is under active development and I’d like to point out some of the new features we created so far (most probably there will be even more goodness in the final release!).

In general, Domino To Go 2.0 will be even more suitable for dealing with bigger datasets. So if you want to create mobile, offline capable Apps for a Notes applications that has some ten thousand documents or more, Domino To Go got you covered.


General features

  • Changing document items on the mobile device immediately: as you may know, you can download complete Notes documents to the mobile device in order to use NotesDocument.getItemValue(), NotesDocument.replaceItemValue() and other familiar methods.
    So far, any change in a Notes document on the mobile device needed to be uploaded to Domino and downloaded back to the device until the local NotesDocument object reflected the change. This has been improved, so that any change made with NotesDocument.replaceItemValue() followed by a NotesDocument.save() is now in effect on the mobile device immediately.
  • Change views on the mobile device immediately: you can download the content of a Domino view to the mobile device with one line of code. But, if you make changes to a Notes document on the mobile device, the view does not update itself automatically.
    Now you can use simple methods (NotesView.replaceColumnValue) to change one or more columns for a specific view entry, without the need to synchronize the view with Domino.
    So if you changed items in a Notes document on the mobile device, you can now adjust the local views accordingly, even when the device is offline.
  • Download the content of a Domino view filtered by category: now you can use a singleCategory property in Domino To Go’s NotesView.update() method in order to only download view entries from Domino that match a specific category.
    This is very handy if you have a Domino view that is categorized by user names, and you only want to download view data to the mobile device for a specific user.
  • More performance improvements: among others, NotesView.getAllEntries() on the mobile device is now about 100% faster when dealing with bigger datasets (more than 10.000 documents).


New demo app:


Domino To Go is an extension for Appcelerator Titanium. Recently, Titanium introduced a new development style called Alloy, which is a nice implementation of the Model-View-Controller concept.


In Alloy, you can define the UI with XML, use styles like in CSS and seperate code from layout. It works very well and once you understood the methods and concept, it speeds up development and makes the app much more maintainable.
But, for Domino developers, an Alloy based app may be hard to understand on the first sight.


We think every Domino To Go developer should develop his apps with the Alloy. And to make learning the Alloy method much more easy, we will deliver a nice Alloy based demo app with Domino To Go 2.0.
Here are some screenshots:





As you can see, the app supports the typical layout for phones and iPad.

It includes:

  • All UI elements are defined in Alloy XML markup.
  • A basic navigation table with some dummy elements.
  • Clicking an element in the navigation opens a content window with some labels. The labels are filled dynamically based on the clicked element.
  • A configuration dialog for username and password, including field validation and saving these settings to the app’s configuration storage.
  • An HTML based “about” window.
  • A style sheet with style definitions to get your started.
  • Some global JavaScript files, for example to place your own synchronisation logic .
  • All Domino To Go libraries are already included so that you can use all Domino To Go classes instantly.
  • The code contains a lot of comments so that you can quickly understand and learn from it.


This demo app alone will save days for new Titanium / Domino To Go developers.


A release date for Domino To Go 2.0 is not fixed yet. I expect it in a month or so.


Any existing Domino To Go customer
can get an early release of the new demo app together with an early version of Domino To Go 2.0, just drop me a note!


Oct 05

Now available for iPhone 5 and iOS 6: NotesBook – the App that synchronizes your Lotus Notes or iNotes Notebook (Journal) to iPhone and iPad

Note: this post has been migrated from another blog. Some links may be broken.

Apple just released NotesBook 3.1, which is now compatible to iPhone 5 and iOS 6 devices. Please try it and if there is still a glitch, please post to support.youatnotes.com/notesbook.

As you may know, NotesBook synchronizes the your Lotus Notes Journal or iNotes Notebook to your iPhone or iPad. It’s already used by a lot of satisfied users and got some nice reviews! So if you want your Lotus Notes Journal or iNotes Notebook on your iPhone or iPad, go ahead, have a look at NotesBook!


Aug 24

ExtensionLibrary – iNotes Virtuallist control – onOpenEntry – how to get the UNID of selected document?

Note: this post has been migrated from another blog. Some links may be broken.

I want to use the xe:ListView (“iNotes ListView”) control from the Extension Library. Unfortunately, there is no documentation about how to access the UNID of the selected document in the onOpenEntry event.
I found a hint about an “ext.item” object, but that does not exist in that event.

So, how do I get the UNID of the selected document in the onOpenEntry event? Any hints?


Jul 01

Small, but nice enhancement in Designer 8.5.3

Note: this post has been migrated from another blog. Some links may be broken.

If you have Notes and Designer open, and you open an application in Notes which is in some workset of Designer, too, then Designer will automatically load that application in the background.

The effect is that after you opened the application in Notes and you want to get into it’s design, the design is already loaded in Designer and you can start working immediately.

That’s a small enhancement, but really useful in everyday’s work. (at least I think it’s new in 8.5.3, I never noticed that behaviour in 8.5.2…).


Jun 02

Lotus Notes is getting faster and faster – report from 8.5.2 CD5

Note: this post has been migrated from another blog. Some links may be broken.

Disclaimer: this is beta and there are no guarantees that the features described here will be in the final product that IBM ships.

Some weeks ago a customer of ours complained about the performance in one of our applications. He used Notes 8.5.0. Since I could not reproduce, I suggested to upgrade to 8.5.1, which did a significant performance boost. So, until now Notes 8.5.1 is as fast as Lotus Notes can get.

Not anymore. I’m very pleased to report that the most recent Lotus Notes 8.5.2 Beta is notable faster than 8.5.1 in many aspects:

  • Startup is faster due to a new “load parts of Notes at operating system start” option.
  • Opening Mail is faster.
  • Opening complex framesets with many forms, pages and so on is faster (in my test scenario: 8.5.1 about 4 seconds, 8.5.2 about 3 seconds).
  • Opening Notes documents with complex forms (lotus of tables and images) is faster (in my test scenario about .5 seconds).
  • And overall the client feels more responsive.

I hope that IBM is still tweaking performance where possible, since performance always makes a real difference for customer satisfaction. But personally I feel that with 8.5.2 we will get a client that’s as fast as (or as slow as 🙂 ) competitor products, but has tons of additional functionality.


Aug 18

Internetausdrucker ist der neue Warmduscher

Note: this post has been migrated from another blog. Some links may be broken.

Grade gelesen in einem Kommentar zu irgendeinem Blog Eintrag: “…alles Internetausdrucker”. Internetausdrucker… ein schöner Begriff. Werde ich ab sofort anstelle von Warmduscher o.ähnl. Begriffen verwenden.


Aug 12

New in our Service Communicator XPages application: displaying Trouble Tickets, getting Tickets via Webservice from any external system

Note: this post has been migrated from another blog. Some links may be broken.

Since we were a software development AND a service company we have a trouble ticket software, just as every other professional service company has. (Our trouble ticket software is a product of our own for sure, but that doesn’t matter here… 🙂 ).

So one big item on our todo list for
Service Communicator was to provide our customers with a list of their tickets in the web, so that they can have a look after the status on their own. Futhermore we wanted to give our customers the possibility to create comments to tickets, and to express their mood (if someone is happy or sad, we want to know that).

Having tickets in Service Communicator has the advantage that we don’t need to expose our trouble ticket software to the internet. We just sync tickets to Service Communicator, and customers view their tickets in Service Communicator, not in the trouble ticket software.


Our trouble ticket software is Notes based, and Service Communicator is a Notes application, too. So, synchronisation is piece of cake, isn’t it?


Yes and no. Yes, it would be easy if we use Notes techniques to transfer the data (like a simple LotusScript agent). But we didn’t want that. Service Communicator should be used by Non-Notes shops, too!
So we needed a way to push data of trouble tickets from any external ticket software to our Service Communicator.


I think the best approach for that is a webservice, and we are quite happy that Lotus Domino supports webservices so well, even with authentication and SSL encryption. We simply used LotusScript to implement an easy to use webservice provider which has just one method:


setTicket(key As String, values() As ynScValue)


where “key” is a key to identify if a ticket already exists in Service Communicator, and values() as an array of field values. One value contains:


name As String

value As String

type As String


with name as the name of the field, value as the string value and type as the field type (so that we can set datetime, number and text fields).
At this moment we have a defined list of mandatory fields and some optional fields. The beauty of this approach is that we can always add optional fields later while every existing webservice consumer can stay as it is.


Inside Service Communicator we’re working with reader fields to ensure that every customer only sees his own tickets, and other users cannot see any tickets at all. Think about implementing such functionality without the Domino security features… for example with PHP or so. Would be much more work I guess.


So far were quite happy with this latest addition to Service Communicator. I really like webservices in Domino, and we will use webservices for many other features in the future, too.