TexasSwede
texasswede@gmail.com
  • About this blog
  • My Website
  • My Resume
  • XML Export Tool
  • Photos

Category Archives: Programming

Agent Logging – Budget Style

Posted on November 10, 2010 by Karl-Henry Martinsson Posted in IBM/Lotus, Lotusscript, Notes/Domino, Programming Leave a comment

At my work, we had several issues/needs related to agents in different Domino databases. I tried to come up with a quick and lean solution, that gave us the functionality we needed, nothing more and nothing less. Yes, I am aware of Julian Robichaux’s excellent OpenLog. But we had some needs that I did not feel were addressed in that project.

What I wanted was a database where the agents could be documented, and also where the log data was stored. So I created a Agent Log database where one document is stored per agent. The form let me document the actions of the agent, as well as what server it is running on, in what database, when it is triggered, etc. When the document is opened, I also read the last time the agent was run and if the agent is enabled or not.

This is a sample document for an agent. It is scheduled to run at 11am every day:

AgentLog_Doc

 

This is what the actual database looks like.

AgentLog

I plan to release the database on OpenNTF.org when I get the time.

 

Nothing complicated this far. The next step was to create a small script library, doing the actual logging. I created a script library called Class.AgentLog with the following code:

Public Const THREAD_TICKS=6
Public Const THREAD_TICKS_PER_SEC=7

Class AgentLog
	Private session As NotesSession
	Private logdb As NotesDatabase
	Private agentdoc As NotesDocument   ' Main doc in Agent Log db
	Private logdoc As NotesDocument
	Private running As Integer
	Private tstart As Long              ' Ticks at start
	Private tend As Long                ' Ticks at end
	Private tps As Long                 ' Ticks per second (system dependant)
	
	Public Sub New( agentname As String )
		Dim view As NotesView
		Dim key As String
		running = True
		tstart = GetThreadInfo( THREAD_TICKS )
		tps = GetThreadInfo( THREAD_TICKS_PER_SEC )
		Set session = New NotesSession
		Set logdb = New NotesDatabase( session.CurrentDatabase.Server, "IT/AgentLog.nsf" )
		Set view = logdb.GetView( "(LookupAgent)" )
		If agentname = "" Then
			agentname = session.CurrentAgent.Name
		End If
		key = session.CurrentDatabase.FilePath & "~" & agentname
		Set agentdoc = view.GetDocumentByKey( key )
		If agentdoc Is Nothing Then
			Print "AgentLog: Failed to locate agent document for " & agentname & "."
			Exit Sub
		End If
		Set logdoc = New NotesDocument( logdb )
		logdoc.Form = "LogItem"
		Call logdoc.MakeResponse( agentdoc )
		Call logdoc.ReplaceItemValue("AgentName", agentname )
		Call logdoc.ReplaceItemValue("StartTime", Now() )
		If session.IsOnServer = True Then
			Call logdoc.ReplaceItemValue("RunBy", session.CurrentDatabase.Server )
		Else
			Call logdoc.ReplaceItemValue("RunBy", session.CommonUserName )
		End If
	End Sub
	
	Public Sub Finish()
		running = False
	End Sub
	
	Public Sub Terminate()
		Dim seconds As Integer
		If logdoc Is Nothing Then
			Exit Sub
		End If
		tend = GetThreadInfo( THREAD_TICKS )
		seconds = (tend - tstart) / tps
		Call logdoc.ReplaceItemValue("EndTime", Now() )
		Call logdoc.ReplaceItemValue("Seconds", seconds )
		If running = True Then ' Check if not terminated gracefully
			Call logdoc.ReplaceItemValue("Terminated", "Yes" )
		End If
		Call logdoc.Save(True,True)
	End Sub

End Class

All code goes in the (Declarations) section of the script library.
There are a few things to notice. I actually make each log item a child (response) document to the main document. By doing this, I can easily later create reports for each agent about all the times it was executed, etc.
When the object is instantiated, a blank string is normally passed. This will set the agent name variable to the actual agent name. The agent name is listed in the agent log document. If for some reason you want to use a different agent name in the document (e.g. the agent is a manually triggered agent called AdminUpdateSelectedDocuments and you want it listed just as UpdateSelectedDocuments).

 

The only thing left now is to update every agent you want to log as follows:

In the (Options) section:

Use "Class.AgentLog"

In the (Declarations) section:

Dim agent As AgentLog

In the Initialize event, I put one line at the beginning and one right at the end. The first line instantiate the agent log object and. set a flag indicating that the agent is running. The second line will clear that flag, so the final function knows that the agent ended gracefully.

Sub Initialize
 Set agent = New AgentLog("")
 ' *** Do stuff here
 Call agent.Finish()
End Sub

The last thing is to add one line to the Terminate event. This line is where the logging is actually done. If the flag running is set, we know the agent was terminated before it actually reached the end.

Sub Terminate
 Call agent.Terminate()
End Sub

Happy logging!

My Favorite Tools

Posted on April 29, 2010 by Karl-Henry Martinsson Posted in Notes/Domino, Programming, Utilities 2 Comments

Kathy Brown today asked “What’s Your Favorite Tool“, so I thought I wanted to share the tools I use.

My favorite tool is probably NoteMan from MartinScott. If I have to pick one tool from the suite, it would be either NoteMan.Editor or NoteMan.DocDelta. It is very hard to decide between the two of them. Editor is great for editing documents, see the contents of different fields and even change data types. I use it to get the UniversalID of documents and much more. DocDelta help me solve replication conflicts quickly and easy. I can higly recommend the NoteMan suite of tools to any Notes/Docmino developer, and for the price ($395 for the whole suite), you get a lot of functionality.

I also use several tools from TeamStudio and Ytria. Yes, I am lucky enough to have a boss who believe in getting me the tools I need.

From TeamStudio I use Undo (previously called Snapper) to make snapshots of the design while developing for easy roll-back, Profiler to find performance issues in my code and Configurator for search-and-replace through-out a database (design and/or documents). Those tools run around $500 each, if I recall correctly. I also use their free class browser, a tool I highly recommend to everyone doing object oriented Lotusscript development.

From Ytria I use a number of tools.The two I use the most are scanEZ and actionBarEZ. The latter is great when I want to apply a specific design of action bars to many forms and/or views. I design the action bar in one view, with colors, fonts, backgrounds, etc. When I am satisfied I can update all views and forms the the database with the new design. I don’t use scanEZ as much, but still on a regular basis. It also have functions to identify replication conflicts, like NoteMan.DocDelta, but the two tools complement each other. Using scanEZ, I can locate and delete documents of a particular type, including profile documents, and much more. I also sometimes use designPropEZ to check the design of a database and make sure it does not inherit element from the wrong templates/databases.

Here is a screenshot of my currect toolbar with all my development tools:

 

In addition I use Photoshop CS2 for graphics editing, TechSmith Jing to create screencam demos for managers/users, and Notepad++ for some HTML/Javascript/jQuery editing.

Object Oriented Lotusscript for beginners – Part 2

Posted on April 12, 2010 by Karl-Henry Martinsson Posted in Lotusscript, Old Blog Post, Programming Leave a comment
In my previous post I wrote about whyI use object oriented Lotusscript. Let’s look at how it can be used in a real-life application.
Background
At my work I developed a system to handle insurance claims. Each claim can have one or more claimants, people or parties that have either BI (bodily injury) or PD (property damage) claims related to an accident. Each claimant get a reserve setup, an amount of money the adjuster think it will cost to settle the claimant. There are two reserves for each claimant, one for loss payments and one for expense payments. The latter can be payments for police reports, field adjusters, lawyer fees, etc while loss payments are the actual damages (payments to body shops, medical payments, etc).
When payments are made, the reserve amounts are reduced, until reaching zero. No more payments can be done then until the reserve is increased. Each adjuster have a limit to how large reserve he or she can set, higher reserve must be approved by a manager.
Data storage
When the claim system was first put in place, all reserves and payments werestored in the Notes database. They were then (manually) transferred into a backend system built in Visual FoxPro. But after a few years, a COM object (dsClaimLink) was developed and the Notes database is now sending all financial transaction into the backend, and retrieving financial information the same way when needed. Claim information is stored in the Notes database, as is claimant information. Some claimant information. a sub-set of the data stored in Notes,is sent to the backend as well.
Original design
Initially I built a large number of functions and subroutines, organized in different script libraries based on functionality.This actually worked really good, and the code was fairly easy to maintain, modify and expand. When the financial transactions were moved to the backend, I just had to modify the function GetAvailableAmount() to call the backend instead of looking up the amount in the Notes database. But it was still not very flexible, andI had some code that was duplicated in many places (most of it related to calling the COM object). So about two years ago, I started refactoring my code, both to make it faster and easier to maintain, by using object oriented Lotuscript.
Example
Beloware examples of the code in the script library Class.ClaimData class. This is not my exact production code, I have removed a number of lines to make the example more clear.
The ClaimData class (described in next posting)contains an array of claimants, each of those an object. Each claimant object in turn contains an object containing the different amounts (loss reserve/loss payments, expense reserve/expense payments, recovery amount, etc).
First, let’s look at the AmountData object.
Class AmountData
    Public lr As Currency        ' Loss Reserve
    Public er As Currency        ' Expense Reserve
    Public lp As Currency        ' Loss Payments
    Public ep As Currency        ' Expense Payments
    Public slp As Currency        ' Supplemental Loss Payments
    Public sep As Currency        ' Supplemental Expense Payments
    Public rec As Currency        ' Recovery amount
    Public lossavail As Currency
    Public expavail As Currency

    Public Sub New()
        rec = 0
        slp = 0
        sep = 0
        lr = 0
        er = 0
        lp = 0
        ep = 0
        lossavail = -1
        expavail = -1
    End Sub
    
    Public Sub Load(claimnumber As String, claimant As Integer)
        Dim success As Integer
        Dim servaddress As String
        Dim xmldata As String
        Dim claimlink As ClaimLink    ' Object to connect to backend
        
        Set ClaimLink =  New ClaimLink()   ' Create object/class
        If claimant = 0 Then          ' Get total amounts for all claimants    
            success = claimlink.GetClaimStatus(claimnumber, Today())
        Else                          ' Get amounts for selected claimant
            success = claimlink.GetAmountsByClaimant(claimnumber, claimant, Today())
        End If
        If success = True Then        ' Data returned successfully
            xmldata = claimlink.GetDataXML()
            rec = Cstr(Ccur(XMLGetValue(xmldata,"recovery")))    
            slp = Cstr(0-Ccur(XMLGetValue(xmldata,"losssup")))
            sep = Cstr(0-Ccur(XMLGetValue(xmldata,"expsup")))        
            If claimant = 0 Then     ' All claimants
                lr = Cstr(Ccur(XMLGetValue(xmldata,"lossorig")) + Ccur(XMLGetValue(xmldata,"losschg")))
                er = Cstr(Ccur(XMLGetValue(xmldata,"exporig")) + Ccur(XMLGetValue(xmldata,"expchg")))
            Else                     ' Specified claimant
                lr = Cstr(Ccur(XMLGetValue(xmldata,"lossres")) - Ccur(slp) + Ccur(rec))
                er = Cstr(Ccur(XMLGetValue(xmldata,"expres")) - Ccur(sep))
            End If
            lp = Cstr(0-Ccur(XMLGetValue(xmldata,"losspaid")) - Ccur(slp))
            ep = Cstr(0-Ccur(XMLGetValue(xmldata,"exppaid")) - Ccur(sep))
            lossavail = Ccur(lr) - Ccur(lp)
            expavail = Ccur(er) - Ccur(ep)
        End If    
    End Sub
    
End Class
As you perhaps noticed, I encapsulated the dsClaimLink functionality in an obect as well. I am also using my own XML parsing functions, as the system was built in Notes R5.
When the object is created, I do not lead the amounts directly. I just set all amounts to 0, with two exceptions. The available amounts are set to -1 (a value they will normally never have). This indicate that data have not been loaded, or that the attempt to load data failed.
The Load() method of the class call the COM object (dsClaimLink) withone of two functions depending on how the method is called. This let meuse the AmountData object notjust for amounts for a specified claimant, but also for claim level amounts,totals for all claimants.
Next we have a small object used to decide if a claimant is open or closed.The expense and loss parts of a claimant can be closed and (re-)openedindividually. If either is open, the claimant is open, if both are closed, the claimant is considered closed. That is why I built this object, to get an easy status indication in the claimant object.
Class ClaimantStatusData
    Public loss As String
    Public expense As String
    Public claimant As String
    
    Public Sub new(doc As NotesDocument)
        If Lcase(doc.LossClosed(0)) = "yes" Then
            Me.loss = "closed"
        Else
            Me.loss = "open"
        End If
        If Lcase(doc.ExpensesClosed(0)) = "yes" Then
            Me.expense = "closed"
        Else
            Me.expense = "open"
        End If
        If Me.expense = "closed" Then
            If Me.loss = "closed" Then
                Me.claimant = "closed"
            Else
                Me.claimant = "open"
            End If
        Else
            Me.claimant = "open"
        End If
    End Sub
End Class
Nothing very complicated, but a big help later on.
The final class I will show today is the actual ClaimantData class. As you can see,I am using the classed I described earlier here. I have removed some code in order to make it easier to follow. Just one more note, I use a field/value called ParentUNID to keep track of all documents that belong to a claim. The claim number is not associated with the claim at first, so I needed some other unique identifier. I choose to use the UniversalID of the main document (“Loss Notice”) at the time it is received into the database. Even if the actual UniversalID would change, e.g. through a replication conflict, that field will never change again.
The class is farly simple. The ClaimantData object will load amount and claimant status wheninitialized. They are then available, together with the methods of the class, to the calling code.
Class ClaimantData
    Public claimantdoc As NotesDocument
    Public unid As String    ' Store UniversalID of claimant document
    Public parentunid As String        
    Public amounts As AmountData
    Public claimcare As ClaimCareData
    Public status As ClaimantStatusData
    Public Parallel As Integer
    
    Public Sub New(doc As NotesDocument)
        Dim claimnumber As String
        Dim claimant As Integer
        Set claimantdoc = doc
        unid = doc.UniversalID
        parentunid = doc.GetItemValue("ParentUNID")(0)
        claimnumber = doc.GetItemValue("ClaimNumber")(0)
        claimant = Cint(doc.GetItemValue("Claimant_Number")(0))
        If Lcase(doc.GetItemValue("TransferredToParallel")(0)) = "yes" Then
            Parallel = True
        Else
            Parallel = False
        End If
        Set amounts = New Amounts(claimnumber, claimant)
        Set status = New ClaimantStatusData(doc)
    End Sub
    
    
    Public Function GetValue(fieldname) As Variant
        GetValue = claimantdoc.GetItemValue(fieldname)(0)
    End Function
    
    Public Function SetValue(fieldname, Byval value As Variant) As Variant
        Call claimantdoc.ReplaceItemValue(fieldname, value)
    End Function
    
    Public Function GetVariant(fieldname) As Variant
        GetVariant = claimantdoc.GetItemValue(fieldname)
    End Function
    
    Public Sub Save()
        Call claimantdoc.Save(True,True)
    End Sub
    
    Public Function DisplayName() As String
        If Fulltrim(GetValue("Claimant_Name")) = "" Then
            DisplayName = GetValue("Claimant_Company")
        Else
            DisplayName = GetValue("Claimant_Name")
        End If
    End Function
    
    Public Function GetXML()        
        Dim tempxml As String
        If claimantdoc Is Nothing Then
            Msgbox "Claimant document is not loaded, no data returned.",,"ClaimantData.GetXML()"
            GetXML = ""
            Exit Function
        End If    
        tempxml = "<claimntno>" & claimantdoc.GetValue("Claimant_Number") & "</claimntno>" & CRLF    
        tempxml = tempxml + "<extclmntno>" & claimantdoc.getValue("ClaimantNumberExternal") & "</extclmntno>" & CRLF    
        tempxml = tempxml + "<classcode>" & claimantdoc.pClassCode(0) & "</classcode>" & CRLF    
        tempxml = tempxml + "<cvgcode>" & claimantdoc.Claimant_LossType(0) & "</cvgcode>" & CRLF    
        tempxml = tempxml + "<table>" & claimantdoc.pTable(0) & "</table>" & CRLF    
        If claimantdoc.Unknown(0)="Yes" Then
            tempxml = tempxml + "<claimntnam>* unknown *</claimntnam>" & CRLF
        Elseif claimantdoc.Claimant_Name(0)="" Then
            tempxml = tempxml + "<claimntnam>" & dsClaimLink.EncodeXML(claimantdoc.Claimant_Company(0)) & "</claimntnam>" & CRLF
        Else
            tempxml = tempxml + "<claimntnam>" & dsClaimLink.EncodeXML(claimantdoc.Claimant_Name(0)) & "</claimntnam>" & CRLF
        End If    
        ' Check if we have amounts loaded
        If Not amounts Is Nothing Then
            tempxml = tempxml + "<lossamt>" & Format$(amounts.lp,"###0.00") & "</lossamt>" & CRLF    
            tempxml = tempxml + "<expamt>" &  Format$(amounts.ep,"###0.00") & "</expamt>" & CRLF    
        End If
        GetXML = tempxml
    End Function
    
End Class
There is a function to get an XML representation of the claimant. This one is used when data is sent to the dsClaimLink COM object. I also have a function to return the name to display, either the person name or the company name of the former is blank. I could have implemented this using the Get/Set statements, but they have to be defined as a pair and this is a read-only property of the object.

ProgressBar class for Lotusscript

Posted on September 4, 2009 by Karl-Henry Martinsson Posted in Lotusscript, Programming 1 Comment

Brian Moore wrote about the problem with users thinking Notes applications are slow, due to no visible feedback:
“People seem to be totally happy at letting something take bleeding ages just so long as there is a little moving object to distract them from the clock.”

This is very true, and I addressed this in one of my applications a while back by implementing a progress bar.
Suddenly, when the users got feedback on what was happening, all complaints about it being slow stopped, despite it taking the same amount of time…

I built a progress bar class. Here it is, as well as a small code sample showing how to call it. Note that this is a Win32 only solution.

 

Option Public
Option Declare

' ***** Declarations for (undocumented) progress bar in Notes *****
Private Const NPB_TWOLINE% = 1
Private Const NPB_STATUSBAR% = 32
Declare Private Function NEMProgressBegin Lib "nnotesws.dll" ( Byval wFlags As Integer ) As Long
Declare Private Sub NEMProgressDeltaPos Lib "nnotesws.dll" ( Byval hwnd As Long, Byval dwIncrement As Long )
Declare Private Sub NEMProgressEnd Lib "nnotesws.dll" ( Byval hwnd As Long )
Declare Private Sub NEMProgressSetBarPos Lib "nnotesws.dll" ( Byval hwnd As Long, Byval dwPos As Long)
Declare Private Sub NEMProgressSetBarRange Lib "nnotesws.dll" ( Byval hwnd As Long, Byval dwMax As Long )
Declare Private Sub NEMProgressSetText Lib "nnotesws.dll" ( Byval hwnd As Long, Byval pcszLine1 As String, Byval pcszLine2 As String )

Class ProgressBar
    Private hidden As Integer
    Private hwnd As Long
    Private value As Long
    Private title As String
    Private textline1 As String
    Private textline2 As String
    Private maxvalue As Long

    Public Sub New(range As Long, initialtitle As String)
        Dim session As New NotesSession
        maxvalue = Clng(range)
        title = initialtitle 
        textline1 = ""
        textline2 = ""
        If session.IsOnServer Then    ' Check if code is running on server (scheduled agent)
            hidden=True
        Else
            hidden=False
        End If
        If hidden = True Then
            Exit Sub
        End If        
        hwnd = NEMProgressBegin(NPB_TWOLINE)
        Call SetRange(maxvalue)
        NemProgressSetText hwnd, title, textline1 & Chr$(13) & textline2
    End Sub
    
    Sub Increase()
        If hidden = True Then
            Exit Sub
        End If
        If hwnd <> 0 Then
            If value < maxvalue Then
                value = value + 1
                NEMProgressSetBarPos hwnd, value
            End If
        End If
    End Sub
    
    Sub Decrease()
        If hidden = True Then
            Exit Sub
        End If
        If hwnd <> 0 Then
            If value > 0 Then
                value = value - 1
                NEMProgressSetBarPos hwnd, value
            End If
        End If
    End Sub
    
    Sub Close
        If hidden = True Then
            Exit Sub
        End If
        If hwnd <> 0 Then
            NEMProgressEnd hwnd    
            hwnd = 0
            title = ""
            value = 0
        End If
    End Sub
    
    Sub SetRange(value As Long)
        If hidden = True Then
            Exit Sub
        End If
        If hwnd <> 0 Then
            maxvalue = value
            NEMProgressSetBarRange hwnd, maxvalue
        End If
    End Sub
    
    Sub SetValue(value As Long)
        If hidden = True Then
            Exit Sub
        End If
        If hwnd <> 0 Then
            NEMProgressSetBarPos hwnd, value
        End If
    End Sub
    
    Sub SetText(message As String)
        If textline2="" Then
            Call PrintText()        
        End If
        If hidden = True Then
            Exit Sub
        End If
        If hwnd <> 0 Then
            textline1 = message
            NEMProgressSetText hwnd, title, textline1 & Chr$(13) & textline2
        End If
    End Sub
    
    Sub SetText2(message As String)
        Call PrintText()
        If hidden = True Then
            Exit Sub
        End If
        If hwnd <> 0 Then
            textline2 = message
            NEMProgressSetText hwnd, title, textline1 & Chr$(13) & textline2
        End If
    End Sub
    
    Function GetText() As String
        GetText = textline1
    End Function
    
    Function GetText2() As String
        GetText2 = textline2
    End Function
    
    Sub PrintText()
        Dim text As String
        If hidden = True Then
            text = textline1
            If textline2 <> "" Then
                text = text & "  -  " & textline2
            End If
            Print text
        End If
    End Sub
    
    Function Show() As String
        hidden = False
        hwnd = NEMProgressBegin(NPB_TWOLINE)
        Call SetRange(maxvalue)
        NemProgressSetText hwnd, title, textline1 & Chr$(13) & textline2
    End Function
    
    Function Hide() As String
        hidden = True
        If hwnd <> 0 Then
            NEMProgressEnd hwnd    
            hwnd = 0
        End If
    End Function
    
End Class

Below is a snippet of sample code, showing how it can be implemented. Enjoy!

units = GetNumberOfUnits()
Set pbar = New ProgressBar(CLng(units+1),"Loading data From backend server…")
Call pbar.Show()
For i = 1 To units 
    Call pbar.Increase() 
    Call pbar.SetText("Loading coverage For unit " & i & "…") 
    Set vehicle = New CoverageData(i) ' Get vehicle coverage 
    Call pbar.SetText2(vehicle.year & " " & FullTrim(vehicle.name) & " – Coverage " & vehicle.cvgcode)
Next
Call pbar.Increase()
Call pbar.SetText("Finishing processing.")
Call pbar.SetText2("Please wait…")
' Do some more stuff here
Call pbar.Close()

 

Stack Exchange

profile for Karl-Henry Martinsson on Stack Exchange, a network of free, community-driven Q&A sites

Recent Posts

  • Domino 14 is now available
  • Domino 14 Early Access Program
  • Announced: Engage 2024
  • Integrate Node-RED with Notes and Domino
  • Notes and Domino v12 is here!

Recent Comments

  • Theo Heselmans on Announced: Engage 2024
  • Lotus Script Multi-thread Message Box [SOLVED] – Wanted Solution on ProgressBar class for Lotusscript
  • Viet Nguyen on Keep up with COVID-19 though Domino!
  • Viet Nguyen on Keep up with COVID-19 though Domino!
  • Mark Sullivan on Looking for a HP calculator? Look no further!

My Pages

  • How to write better code in Notes

Archives

  • December 2023 (1)
  • October 2023 (2)
  • September 2023 (1)
  • June 2021 (1)
  • April 2021 (2)
  • March 2021 (1)
  • August 2020 (3)
  • July 2020 (2)
  • April 2020 (2)
  • March 2020 (1)
  • December 2019 (2)
  • September 2019 (1)
  • August 2019 (2)
  • July 2019 (2)
  • June 2019 (3)
  • April 2019 (2)
  • December 2018 (1)
  • November 2018 (1)
  • October 2018 (5)
  • August 2018 (2)
  • July 2018 (3)
  • June 2018 (2)
  • May 2018 (1)
  • April 2018 (2)
  • March 2018 (1)
  • February 2018 (2)
  • January 2018 (4)
  • December 2017 (3)
  • November 2017 (2)
  • October 2017 (2)
  • September 2017 (1)
  • August 2017 (2)
  • July 2017 (6)
  • May 2017 (4)
  • February 2017 (1)
  • January 2017 (2)
  • December 2016 (2)
  • October 2016 (3)
  • September 2016 (4)
  • August 2016 (1)
  • July 2016 (2)
  • June 2016 (2)
  • May 2016 (3)
  • April 2016 (1)
  • March 2016 (4)
  • February 2016 (2)
  • January 2016 (4)
  • December 2015 (3)
  • November 2015 (2)
  • October 2015 (1)
  • September 2015 (2)
  • August 2015 (1)
  • July 2015 (5)
  • June 2015 (2)
  • April 2015 (2)
  • March 2015 (3)
  • February 2015 (2)
  • January 2015 (10)
  • December 2014 (1)
  • November 2014 (3)
  • October 2014 (3)
  • September 2014 (13)
  • August 2014 (6)
  • July 2014 (5)
  • May 2014 (3)
  • March 2014 (2)
  • January 2014 (10)
  • December 2013 (5)
  • November 2013 (2)
  • October 2013 (5)
  • September 2013 (4)
  • August 2013 (7)
  • July 2013 (3)
  • June 2013 (1)
  • May 2013 (4)
  • April 2013 (7)
  • March 2013 (8)
  • February 2013 (9)
  • January 2013 (5)
  • December 2012 (7)
  • November 2012 (13)
  • October 2012 (10)
  • September 2012 (2)
  • August 2012 (1)
  • July 2012 (1)
  • June 2012 (3)
  • May 2012 (11)
  • April 2012 (3)
  • March 2012 (2)
  • February 2012 (5)
  • January 2012 (14)
  • December 2011 (4)
  • November 2011 (7)
  • October 2011 (8)
  • August 2011 (4)
  • July 2011 (1)
  • June 2011 (2)
  • May 2011 (4)
  • April 2011 (4)
  • March 2011 (7)
  • February 2011 (5)
  • January 2011 (17)
  • December 2010 (9)
  • November 2010 (21)
  • October 2010 (4)
  • September 2010 (2)
  • July 2010 (3)
  • June 2010 (2)
  • May 2010 (3)
  • April 2010 (8)
  • March 2010 (3)
  • January 2010 (5)
  • November 2009 (4)
  • October 2009 (7)
  • September 2009 (1)
  • August 2009 (7)
  • July 2009 (1)
  • June 2009 (4)
  • May 2009 (1)
  • April 2009 (1)
  • February 2009 (1)
  • January 2009 (3)
  • December 2008 (1)
  • November 2008 (1)
  • October 2008 (7)
  • September 2008 (7)
  • August 2008 (6)
  • July 2008 (5)
  • June 2008 (2)
  • May 2008 (5)
  • April 2008 (4)
  • March 2008 (11)
  • February 2008 (10)
  • January 2008 (8)

Categories

  • AppDev (10)
  • Blogging (11)
    • WordPress (5)
  • Design (5)
    • Graphics (1)
    • UI/UX (2)
  • Featured (5)
  • Financial (2)
  • Food (5)
    • Baking (3)
    • Cooking (3)
  • Generic (11)
  • History (5)
  • Hobbies (10)
    • LEGO (4)
    • Photography (4)
  • Humor (1)
  • IBM/Lotus (178)
    • #Domino2025 (14)
    • #DominoForever (8)
    • #IBMChampion (46)
    • Administration (7)
    • Cloud (7)
    • CollabSphere (9)
    • Community (49)
    • Connect (33)
    • ConnectED (12)
    • Connections (3)
    • HCL (15)
    • HCL Master (1)
    • IBM Think (1)
    • Lotusphere (46)
    • MWLUG (25)
    • Notes/Domino (99)
      • Domino 11 (7)
    • Sametime (8)
    • Verse (14)
    • Volt (3)
    • Watson (6)
  • Life (8)
  • Microsoft (7)
    • .NET (2)
    • C# (1)
    • Visual Studio (1)
  • Movies (3)
  • Old Blog Post (259)
  • Personal (23)
  • Programming (84)
    • App Modernization (11)
    • Formula (4)
    • Lotusscript (47)
    • NetSuite (4)
      • SuiteScript (3)
    • node.js (4)
    • XPages (4)
  • Reviews (9)
  • Sci-Fi (4)
  • Software (24)
    • Flight Simulator (2)
    • Games (4)
    • Open Source (2)
    • Utilities (6)
  • Technology (37)
    • Aviation (3)
    • Calculators (2)
    • Computers (6)
    • Gadgets (7)
    • Mobile Phones (7)
    • Science (3)
    • Tablets (2)
  • Travel (7)
    • Europe (1)
    • Texas (2)
    • United States (1)
  • Uncategorized (16)
  • Web Development (50)
    • Frameworks (23)
      • Bootstrap (14)
    • HTML/CSS (12)
    • Javascript (32)
      • jQuery (23)
  • Prev
  • 1
  • …
  • 7
  • 8
  • 9

Administration

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org

Tracking

Creeper
MediaCreeper
  • Family Pictures
© TexasSwede 2008-2014