by Deborah Penny
IN THIS CHAPTER
Domino 6 brings a lot of new functionality to the table that developers have long been waiting for, including support for reusable JavaScript, .js routines, style sheets, and files as shared resources. Some database objects previously considered as shared resources in Domino have been moved to their own Other or Shared Code hierarchies in Domino Designer's integrated development environment (IDE).
Actions, subforms, fields, agents , outlines, and script libraries all fall under a new shared code hierarchy, whereas images, files (new to Domino 6), applets, style sheets (new to Domino 6), and data connections (new to Domino 6) are categorized under a new Shared Resources hierarchy. The database icon, About and Help documents, and database script have all been moved to a new Other/Database Resources category; navigators and the design synopsis features have also been moved to the Other category inside the IDE. So just when you thought you knew where everything was, it's been moved!
Speaking positively however, with the complete redesign of the Designer's IDE comes new functionality that has been long awaited. This great redesign really works, and the amount of thought that was put into it is very evident. Let's get started using the shared resources and shared code features in Domino 6.
Shared resources are a good way to maximize the use of design elements throughout the design of the database or multiple databases. Shared resources are stored with the design of a database just once; therefore, resources commonly used in multiple databases can be stored in a template and applied to all the databases that need to use them. Most of the design elements stored as resources are those that you share with other design objects and elements. These are images, files, applets, style sheets, and data connections. A shared resource can be referenced by code repeatedly but must maintain it in only one place. This not only saves disk space, but it also conserves the developer's time by not having to code things multiple times. This is frequently referred to as Rapid Application Development (RAD). What's also great is that you have to make a change only once, and that change then is reflected in every instance in which the shared resource is called or used. Each database can contain its own set of shared resources. You can even access shared resources in other databases. What's more, if the resource is external to the database, you can make the change and refresh it right inside the Domino 6 IDE ”this is new to Release 6. You don't have to recompile, reload, or delete and add again. Just refresh and go! |
Part I. Introduction to Release 6
Whats New in Release 6?
The Release 6 Object Store
The Integrated Development Environment
Part II. Foundations of Application Design
Forms Design
Advanced Form Design
Designing Views
Using Shared Resources in Domino Applications
Using the Page Designer
Creating Outlines
Adding Framesets to Domino Applications
Automating Your Application with Agents
Part III. Programming Domino Applications
Using the Formula Language
Real-World Examples Using the Formula Language
Writing LotusScript for Domino Applications
Real-World LotusScript Examples
Writing JavaScript for Domino Applications
Real-World JavaScript Examples
Writing Java for Domino Applications
Real-World Java Examples
Enhancing Domino Applications for the Web
Part IV. Advanced Design Topics
Accessing Data with XML
Accessing Data with DECS and DCRs
Security and Domino Applications
Creating Workflow Applications
Analyzing Domino Applications
Part V. Appendices
Appendix A. HTML Reference
Appendix B. Domino URL Reference