Lotus

PILING IT ON II: Getting started with plugin development

As an extension of Mikkel's post on how to get started with plugin development, I submit the following:

  1. Symphony Developer's Guide PDF (in Symphony SDK) -even though it's not Domino development, it can get a beginner up to speed on creating plugins in the Expeditor platform.

OPEN THREAD: What is Missing in Domino Designer?

On this eve of Lotusphere '10 (not going, thank you very much) has anyone compiled a list of the major pieces that are missing from a Domino developer's toolkit? This is not a rant, as IBM has more than fulfilled its pledges to make Notes and Domino technically relevant again, but there are glaring holes that are obvious candidates for a list. I’ll start things off by naming three easy ones:

LOTUSSCRIPT QUICK TAKE: DIR() FUNCTION NOT REENTRANT

Just a quick tip/reminder to anyone out there who may have had to use the LotusScript (nee VisualBasic) Dir() or Dir$() function. The function IS NOT reentrant. If, as is a typical use-case, you want to deep traverse a directory tree by recursively calling a function that examines a directory using the Dir() function, take care not to nest calls within the recursion. For example:

OMNICLIENT VALIDATION, PART 2

In my previous installment I discussed the simple framework for a client validation framework that works in the Notes client and the on the web using a common codebase in Javascript. The implication, of course, being that the validation is client-side and only has to be written once. The framework is skeletal and does not represent a functionally complete example, although it can be made to be.

OMNICLIENT VALIDATION, PART 1

Part one of two, in a series.

DEEP THOUGHTS 1

And now, Deep Thoughts, by Jake. Cue soothing music.

PD is not PDQ

or, Plugin Development is not Pretty Darn Quick.

Syndicate content