| . |
...and server tools ...
|
| A |
A little warning about open files - obey it!
|
Accept license
|
Add the include- and library directories to the global directory settings
|
Additional Tools you might want
|
After reboot - time to install Helpsystem
|
All components in an application needs the same compiler- and linker settings
|
API - What is that ?
|
Appendix
|
| B |
Building applications
|
| C |
C
|
C++
|
| Common compiler- and linker settings for all components |
All components in an application needs the same compiler- and linker settings
|
Common compiler- and linker settings for all components
|
How to create your own library
|
| Compiler |
Compiler
|
General guide to any toolkit!
|
| Cool modifications |
Cool modifications
|
Header files
|
How to create your own library
|
Copying files ...
|
Copyright Notice
|
Create a new project
|
| D |
| Debugger |
Debugger
|
General guide to any toolkit!
|
| Deliver the API as Direct Exposure - or bi-product ? |
Deliver the API as Direct Exposure - or bi-product ?
|
The Notes C API
|
Determine if you will need Unicode-support
|
| Determine Notes release you want to develop applications for |
Determine Notes release you want to develop applications for
|
Determine what programming languages you want to work with
|
Dive into the documentation and browse the samples!
|
Divide customer code from own code - and keep separate copies of all releases
|
Documentation
|
Download the tookit for the Notes release and platform
|
| E |
Ensure that the C++ runtime DLL are in place
|
Ensure that the Notes program directory and Notes data directory are in the PATH environment variable
|
| F |
Finally, we coming somewhere - Register those environment variables!
|
| G |
General guide to any toolkit!
|
General knowledge nice to know before we start!
|
General quirks you need to be aware of
|
| General structure of most toolkits - including Notes C and C++ APIs |
General structure of most toolkits - including Notes C and C++ APIs
|
Installation of APIs
|
| H |
Header files
|
History - where does Notes C and C++ API fit ?
|
How to build the samples shipped with the Notes C and C++ API ?
|
How to create the samples via the Command prompt, as specified in the toolkit help ?
|
| How to create your own library |
How to create your own library
|
What to do with your own common libraries ?
|
How to install the Visual Studio product ?
|
How to you change options and settings in Visual Studio ?
|
| I |
If you got the MSDN-CD or DVD, install it - but be certain about the version!
|
If you have Visual Basic installed before you attempt to install Visual Basic, you should uninstall the old VB first
|
If you plan to work with databases, take it slow around the database access options
|
In order to run any C++ API applications, the C++ runtime DLL must be "installed"
|
In the header file, add these compiler-commands (aka "pragma directives") - they'll guide the compiler to the correct libs later.
|
Info about debug symbols ...
|
Install the tookit
|
Install the toolkit
|
Installation
|
Installation of APIs
|
| Installation of the Notes C API |
Installation of APIs
|
Installation of the Notes C API
|
| Installation of the Notes C++ API |
How to build the samples shipped with the Notes C and C++ API ?
|
Installation of the Notes C++ API
|
Installation of Visual Studio C++
|
Interpreter
|
Introduction
|
It all starts with the source code...
|
| L |
Let the editor insert either spaces or tabs
|
Let the workspace remember your projects and files
|
Library files
|
Link with Notes libraries
|
| Linker |
General guide to any toolkit!
|
Linker
|
Load the CD or DVD containing the service pack 5
|
| M |
MSDN Install - here we go again ...
|
| N |
Necessary modifications
|
New file format for SourceSafe
|
| O |
Object Code
|
Oh, the result (executable, dll, lib) can be either debug or release ?!?
|
Ok, Notes C API might be complex, but what are my options ?
|
Once again - reboot windows
|
| One way to organize your tookits and source code |
Installation of APIs
|
One way to organize your tookits and source code
|
Organize your toolkits based on task and release
|
Other important Notes APIs
|
| R |
Register Visual Studio over the web
|
| S |
Samples!
|
Select features of library
|
Select setup type
|
Select which Runtime Libraries you want
|
Selecting other tools - you want some of these
|
Selecting what data access you will need
|
Selecting which enterprise tools to add
|
Separate own code from product code
|
Service Pack 5 setup starts
|
Set some important debug options
|
| Set the Global Directories |
Common compiler- and linker settings for all components
|
How to build the samples shipped with the Notes C and C++ API ?
|
How to create your own library
|
Installation of APIs
|
Library files
|
Set the Global Directories
|
Set the very important common settings for all Notes API applications
|
Set up the links between the Notes data directory and "notedata" directory in the toolkit
|
Short history of Notes
|
| Single thread or multi thread |
Common compiler- and linker settings for all components
|
Single thread or multi thread
|
| Source Code |
General guide to any toolkit!
|
Source Code
|
Start using the library by including the header file
|
| Step by step to install service pack |
Installation of Visual Studio C++
|
Step by step to install service pack
|
| Step by step |
Installation of Visual Studio C++
|
Step by step
|
| Struct Member Alignment setting |
Struct Member Alignment setting
|
The 1-byte alignment challenge
|
| T |
Tell the build-process to copy the header file(s) to the common include-directory
|
Tell the linker to move the result (the library file) to the common lib-directory
|
| The 1-byte alignment challenge |
Common compiler- and linker settings for all components
|
The 1-byte alignment challenge
|
The C++ tab - Code Generation category
|
The C++ tab - General category
|
The COM Toolkit
|
The COMPILER transform the source code to intermediate files, the object files
|
The Debug Tab
|
The files are flowing ...
|
The first step - launching the setup application
|
The general directory structure and logic for your own libraries
|
The introductory steps
|
The Java Toolkit
|
The LINKER combines your object files with other libraries into an executable
|
The Lotus XML toolkit
|
The LSX Toolkit
|
The Notes C API
|
The Notes C++ API
|
The overview over application tools in Notes
|
The result is an EXECUTABLE file (or a DLL or a LIB ...)
|
The VIM Toolkit
|
Time to customize the install
|
Time to reboot - no, it can't be avoided!
|
To use MFC or not, that's the question!
|
Typographical Conventions
|
| V |
Validate the output of the installer in your toolkit directory
|
VC++ MFC and Template Libraries
|
Verify that the program directory of Lotus Notes is in your environment variable PATH
|
| W |
Websites and other references
|
What can the C++ API do ?
|
| What CAN you do ? |
What can the C++ API do ?
|
What CAN you do ?
|
What is this they say about Notes C API being difficult ?
|
What kind of applications can be made ?
|
What to do with your own common libraries ?
|
| What you CAN'T do |
What can the C++ API do ?
|
What you CAN'T do
|
What! - Even more components to install !!! - Other client tools
|
When finished, proceed to the Service Pack 5 install
|
When you start using the debugger, tell it to display the content of almost any variable or structure
|
Where does the Notes C API operate ?
|
Where should the common components be installed ?
|
Why not access the Notes data directly ?
|
Will you need graphic elements ? Probably not from here ...
|
Work together with the Notes C API!
|
| Y |
You didn't install MSDN - or what help system do MSDN use ?
|
You now have an empty project workspace
|
You're ready to create the library
|
Your sight isn't that good, turn up the fonts!
|