"Microsofts tal er latterlige og opdigtede," siger Lotus Notes - og kaster egne tal tilbage i kampen mod Exchange om hvem, der har flest mail-kunder. ‎

DAOS Updates for Domino 8.5.1 ‎

Research and insights on Chief Information Officers as change leaders and their ability to drive change, innovation and efficiency to help build a smarter enterprise ‎

Live streaming keynnote Monday for Collaboration University 2009 - London with Darren Adams ‎

Brugergruppen DanNotes er medlem af LotusUserGroup og vores næste seminar er registreret her.
‎

This is not a complete application, but a toolkit of reusable LotusScript libraries that can be included in your applications. There may also be any required supporting design elements (subform used in dialog, etc), and sample code to show how the functions in the script libraries are invoked.

Planned contents include:

[*] AttachmentAdder: adds file attachments (and images) to documents and rich text items.

[*] ReportGenerator: a tool to make it easier to create rich-text reports (including tables), which also tries to intelligently maximize the extent to which line breaks are used as opposed to paragraph breaks, so that there are fewer paragraphs (which is more efficient).

[*] StringDiff: a tool for comparing two pieces of text and generating a list of the differences and the same parts. This can be used for tools that summarize differences between replication conflict documents, for instance, or for automatically assigning credit for wiki articles by comparing the amount of text contributed by different authors.

[*] ClassicDataStructures: The classic data structures: Stack, Queue, Prioritized Queue, a Tree or two, and sorted and unsorted collections, designed for use with any content type or easily subclassed for better datatype control.

[*] RTDataTable: supports configuring applications based on data stored in a table in a rich text item. So for instance, you might have a product catalog in tabular form, and store it all in one document (or multiple documents if there's some logical division). The data could either be extracted "live" at runtime using LotusScript, or copies stored in an easier-to-manage form when the document is saved, so that they can be retrieved with lookups. The idea is that the user has an easy-to-edit table in which they can copy, paste, reorder rows, change column widths and even reorder columns or add "comment" columns which aren't part of the official data, and have this free-form data drive processes in the code.

[*] OptionalMessage: Support for messageboxes that include a checkbox the user can tick to avoid being shown that message again. The system keeps track for each user which messages they have asked to not see anymore.

[*] SendKey: (Windows-only, uses OS functions) Send keystroke sequences to the operating system, detect whether Ctrl or other keys are depressed. If there are implementations for other OS we would like to add them, along with automated detection of which OS you're on.

[*] Newsletter: Similar to the builtin NotesNewsletter class but allowing more control, this class lets you build up reports to send to users by email, including doclinks and data arranged in tables.

[*] ProgressBar: A base class and a couple of variations for reporting progress to users during long-running agents. Includes support for automatically disabling the progress bar when in debug mode.

[*] TempFileManager: Creates a temporary folder for your temporary files, creates the files on demand, and cleans up when you're all done.

[*] UniqueKey: Code to test whether the user is entering a unique value in a field, or a combination of fields (i.e. the combined value must be unique), as part of a form validation.</ul>

Depending on available time, these may not all be in the 1.0 version. We are also open to adding libraries from other contributors (please!), which will be carefully vetted, tested and code reviewed.

The target version is Notes 8.5 or later, but most of this stuff should also work in earlier versions. ‎

‎

‎

‎

‎