How many records should you show at once? One? Ten? All? How should the
user navigate from one group of records to another? What should the user see
when there are no more records to display? Obviously, there are no definitive
answers to these questions; each response must take into account the intent of
the page, the type of data involved, and the audience for that data. This chapter
can??™t give you precise solutions for every Web application, but it does give you
the tools to devise your own resolutions.
The Web is, almost by definition, a hotbed of constantly changing technologies.
It can be frustrating when you are introduced to a technology, such as
Dreamweaver??™s Flash buttons, and you cannot utilize its full potential. For
instance, you have had no easy way to use Flash buttons to navigate recordsets??”
at least, not until now. The final section in this chapter describes a technique for
combining the functionality of Dreamweaver??™s recordset navigation bar with the
coolness of animated (and possibly sound-enabled) Flash buttons.
Displaying Data Conditionally
What makes a Web page into a Web application? Connectivity to a data source
by itself does not make a Web application??”after all, you??™re merely setting up
the possibility for data integration, not actually utilizing it.
Pages:
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218