Java™-based development framework for PalmOS™ devices (PDAs)
Copyright© 2000 by Bernd R. Fix. All Rights Reserved.
The DynaWorks framework was designed with simplicity
in mind; but nevertheless there are many questions concerning the use
and technical background of the framework.
The following section will help you to get an answer to frequently asked questions about DynaWorks by listing answer and questions in a list. To find more technical information about DynaWorks, please go to the Technology section.
|Q: What is DynaWorks ?|
A: DynaWorks is a small framework to develop
applications running on a PalmOS™ platform and the
K Virtual Machine. The framework features
access to build-in or custom databases and supports multiple vierws (or dialogs) for user interaction.
The intension of DynaWorks is not to be a full-fledged GUI (you better use kAWT for that purpose) nor a general database interface. In both cases the aim was to respect the platform (PalmOS) and its limitation and still have a java-like interface for application development.
|Q: What do I need to use DynaWorks ?|
A: You need (at least):
You may want to use:
|Q: Can I integrate DynaWorks into my development environment ?|
A: Every development environment that supports the development of KVM applications in general
can be used to write DynaWorks applications as well.
Currently there are only a few IDEs around that are prepared for this job. You can find more information on how to integrate DynaWorks into the IDE of your choice, turn to the technical section of the tutorial.
|Q: Does it work on the PalmOS Emulator ?|
|A: Yes. There are no known limitations for DynaWorks on POSE.|
|Q: Is it compatible with ... ?|
|A: Currently there are no reports of incompatibility of DynaWorks with any other application running on the Palm. If you should encounter any problems of that kind, please let me know by sending an email.|
|Q: Are there any restrictions ?|
|A: Not really - but: DynaWorks is freeware, so you should give applications developed with DynaWorks away for free as well. If you want to use DynaWorks for a commercial project, please negotiate that topic with me in advance and contact me by email.|
|Q: I want to write an application with multiple pages for different user dialogs and views. How do I exchange information/data between pages?|
A: You should use the DataDictionary class to maintain application-wide,
cross-page objects and data values. For an example of this have a look at the
I recommend the following procedure: Find all data objects you want to share across pages. If all pages use the same set of information, you can simply group all data into on object (this is the way the DynaDb example works). Otherwise store two or more different data objects in the dictionary. You can then access (and change) this data objects from any page within the application. For more information on the DataDictionary usage, see the appropriate section in the tutorial.
Whenever a page is about to be activated, its perform() method is called. This is the place where you can access the shared data to initialize the page before it is displayed. For more information on the perform() method see the DynaPage tutorial.
|Q: I use the 'DynaDb' framework in my application. The database access is quite slow. What are the reasons for this behaviour?|
A: There are two possible explanations for this behaviour:
Back to top of page ...