3 Sample model illustrating navigation between dialogs (two pop-up menus
and a query)
166 MOBILE PHONE APPLICATIONS USING A PYTHON FRAMEWORK
minimizing the modeling work. For example, in Fig. 8.3, it is enough to draw only one
?¬‚ow from the restaurant type selection to the query, instead of modeling all three
possible choices from the pop-up menu separately.
Canceling (pressing the right soft key) was also supported with a separate directed
relationship type. Its use, however, was not de?¬?ned as mandatory as in most design
situations it is not necessary to specify. Normal canceling behavior could be derived
by following the application ?¬‚ow backward and only abnormal cases needed to be
speci?¬?ed. This ???convention not con?¬?guration??? approach worked well here and greatly
minimized the modeling work??”in most cases, only forward navigation needed to be
speci?¬?ed.
Relating Manual Code to Models Early on the customer raised the option of
manually entering Python code in designs. Perhaps this was a way to allow a back
door for manual programming, but the sample applications in the Python
framework did not indicate any need for it. However, to satisfy the customer and
show that the old approach can be applied as well, both default navigation and
canceling were extended with the possibility to add custom code.
Pages:
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316