home | narrative | services | contact | blog | (646) 515-5825 | info@critical-masses.com
That’s What Would You Do. I’d write WWJD in the title but I don’t want to offend…
Excuse me for the pedantic nature of this post, but I recently had an issue with developing a fairly complex agent for Notes coded in Java that caused me to revisit a basic understanding of how Java in Notes works. You see, the Java Virtual Machine, JVM for short, is essentially a stack-based emulator that runs bytecode compiled from the Java language source. Without getting into too much detail, the JVM has two memory pools to speak of, the stack and the heap, that can impact the performance and reliability of your Java program.
As an extension of Mikkel's post on how to get started with plugin development, I submit the following:
I’ve been trying to decipher how IBM’s Crypto works in the context of Lotus Expeditor. The spelunking trail has led me down the KeyStore provider path, which is a subtle quirk feature of the Expeditor package that allows for keychaining identities.
I thought I had gotten over the major humps to developing supersecret app, but it turns out that the Lotus Expeditor runtime had one more nasty trick up its sleeve: Expeditor’s runtime’s Java Cryptography Extension provider seems to be missing an algorithm for decrypting SSL communications with Google Apps. Bah! This is what happens when the JVM market fragments.
Finally, some sun here in North Jersey, literally and figuratively.
My goal for today's PDE programming has been met: Understand how to create a custom dialog in JFace for an Eclipse/Equinox plugin. So, you'd think it would just be as easy as declaring a Dialog-ish object, adding the layout and widgets you need to it and making it visible but its not. It's not rocket science either, but it is a step back in programming simplicity from what I'm used to. Essentially, there are three steps: