Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
IBM Lotus Domino: Classic Web Application Development Techniques

You're reading from   IBM Lotus Domino: Classic Web Application Development Techniques This tutorial takes Domino developers on a straight path through the jungle of techniques to deploy applications on the web and introduces you to the classic strategies. Why Google it when it‚Äôs all here?

Arrow left icon
Product type Paperback
Published in Mar 2011
Publisher Packt
ISBN-13 9781849682404
Length 344 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Richard G Ellis Richard G Ellis
Author Profile Icon Richard G Ellis
Richard G Ellis
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

IBM Lotus Domino: Classic Web Application Development Techniques
Credits
About the Author
About the Reviewers
www.PacktPub.com
1. Preface
1. Preparation and Habits FREE CHAPTER 2. Design and Development Strategies 3. Forms and Pages 4. Navigation 5. Cascading Style Sheets 6. JavaScript 7. Views 8. Agents 9. Security and Performance 10. Testing and Debugging

General precautions


Some design practices that seem expedient in the moment can be problematic in the long term as they create problems for managing or using an application. It is tempting to take shortcuts, especially if an application is needed quickly or if it is expected to be of only temporary value. Resist such temptations.

Do not hardcode URLs, filenames, or UNIDs

It should go without saying that applications should never hardcode specific URLs. A link to a specific website, server, directory path, or filename is almost guaranteed to break eventually, as applications move from server to server and from directory to directory.

Use @WebDbName

Links from one design element to other elements within an application are typically constructed as relative links, while links to external resources are naturally coded as absolute links. Links attached to buttons or hotspots typically derive from @formulas or JavaScript code. Of course, a button or hotspot formula also can do some processing (for...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image