Free api software for pda

Requirements: Pocket PC

CEAPI - Windows CE API Interface for PocketC 1.0 is utility which supplies an interface for calling Windows CE API functions directly from PocketC. It includes a set of Windows compatible header files, some example PocketC programs and a library DLL that provides data type conversion where required. A large number of API entry points are supported directly. Entry points not provided in the interface can be called using run-time binding. In general a call to a function from PocketC using CEAPI looks identical to the same function call from Visual C++ or evc. CEAPI also includes a set of functions for accessing real memory and a mechanism for calling functions in standard DLLs. A runtime only version is available to allow end-users to run programs that are written using CEAPI. In addition a kitbuilder download is provided so that programmers can generate a kit including the CEAPI runtime DLL.

Arcoiris - view color and hex value.
This program was made using Pila and adding new API traps to access palmos4 APIs.
Source included.
System requirements:
- M505
- Palm OS v4.0

microGraphs is a Java API used to create applications that can render graphs on a MIDP enabled device. Example uses could be business applications that transmit the stock values in a graphical form in real time. The download comes with the complete documentation about using the API along with example applications.

RoadMap is an open source (GPL) program that provides a car navigation for Linux, UNIX and now Windows CE (a.k.a. PocketPC). It displays a map of the streets, tracks the position provided by a NMEA-compliant GPS receiver, identifies the street matching this GPS position and announces the name of the crossing street at the next intersection. A rudimentary trip feature allows RoadMap to display some basic navigation information (distance to the destination, direction, speed, etc..). Voice messages are generated that duplicate some of the screen information.
It is possible to display a specific area by providing a (complete or incomplete) postal address, the intersection of two streets or an exact position (longitude / latitude).
The map files used by RoadMap are generated from the TIGER files provided by the US Census Bureau, and thus cover the USA only. The RoadMap map format is a binary format that is sensitive to the endianness of the processor. Maps available on this site cover all the USA and have been generated for a little endian processor (such as the Intel Pentium and StrongARM processors).
RoadMap has been designed to be usable on both a desktop or laptop PC, or on a PDA such as the iPAQ from HP (formely from COMPAQ). It can use either the Gtk 1.2 , Gtk 2.0 or QT graphic library for its user interface. The Qt interface supports the Sharps Zaurus PDA. All these machines share the same endianness and can use the maps provided on this site.
RoadMap is at an early stage of development. At this time there are no routing features implemented yet. The plan for the future is to implement some navigation features similar to those found in commercial street navigation systems. The main limit for implementing routing is the lack of navigation information in the US Census Bureau database (for example one-way street are not indicated). The US Census Bureau has clearly indicated that it does not plan to add these information in the future (the USCB does not need them).
RoadMap uses gpsd for the GPS link and flite (festival lite) for the voice messages. Note that flite can be rebuilt with better voices than the default one (such as a US voice instead of a british one--some may disagree :). See the flite README for more information. Here is an example, courtesy of Scot Wilcoxon:
cd flite
make clean # to remove old executable files
./configure --with-vox=cmu_us_kal16
RoadMap comes with its own GPS status screen, which provides an overview of the satellites received and highlights those the GPS has a fix on. This status screen allows for placing the GPS device in a position that optimizes satellite reception, even if that means making the GPS devices screen not accessible.
RoadMap uses a binary file format for representing the maps that is compact enough to allow the storage of many maps on a Compact Flash or MultiMedia card. For example, the map of Los Angeles county takes about 10 Mbytes of flash space. RoadMap comes with a set of tools to convert the US Census bureau data (both the 2000 and 2002 versions) into its own map format. Future versions of the US Census bureau data will be supported as well (usually a 1 or 2 months after the data has been released).
When RoadMap starts, it displays a map of the same area that was displayed on the latest session. Clicking on the map screen triggers a "sign" that displays the name of the street, road or freeway (if any) that is the closest to the mouse hotpoint.
Enhancements:
- Makefile cleanup: everything must now be built in src. If only one toolkit support is to be built, use the DESKTOP option. Please read the README file for more information.
- Small addition to the README file, section "troubleshooting".
- RoadMap uses a minimum refresh period to avoid recomputing the screen too often. This period is now a preference. Not that you normally would want to change this, but this helps on some very specific setups.
- The --debug option now accepts a list of source files as parameters.
- Reworked the roadmap_trip.c API, to have a common API between the current trip module and the upcoming one from Paul.
- Make RoadMap resynchronize with the graphic engine (X11) before drawing a new map. Dont redraw if the graphic engine is busy. This is intended as an attempt to avoid overloading the X server on a PDA (Paul Fox).
- Support defining a sprite as an alias of another sprite (Paul Fox).
- Show the preference categories sorted in alphabetical order, to makes it easier to retrieve a category tab.
- Expand all paths, including the hard-coded ones (Ehud Shabtai).
- Fix the handling of the end-of-file when the GPS source is a NMEA log file.
- User preference to decide what side to draw the toolbar on: top (default), right, bottom or left. (Not yet available on Windows CE.)
- A fix for the shape gap filler code in buildmap. buildmap generated wrong shapes for long lines (Ehud Shabtai).
- The menus are now user configurable, in a way similar to the toolbar. The actions can be renamed, to match the size of the screen better (Paul Fox and I).
- The minimal mouse/pen movement required to initiate a map drag is now configurable: some screen digitizers have a significant jitter, but a large value is incomfortable on a desktop machine (Paul Fox).

ProfileEngine 1.0 is a great addition to a programmer's toolkit. It is actually a Python extension that allows access to the ProfileEngine API which is available on 3rd edition FP1 phones (and newer). It has limited functionality: it allows getting/setting the current profile and retrieving a list of available profiles.

Note: On 3rd edition phones Python extensions need to be signed using the same certificate and the same capabilities as the Python SIS file itself. If signed differently or using different capabilities, installation will work but you'll get KErrAccessDenied errors at run-time.

Major Features:

1. Symbian 3rd edition FP1 SIS file (unsigned) is available
   
2. Source files, documentation and example are available
   

Requirements:

• Symbian 3rd edition FP1
• Python for S60 (PyS60)

Yahoo Messenger Plug-In SDK 1.0b1 makes it easy to create add-ons with collaborative features that can run inside Yahoo Messenger. Plug-ins run in the main Messenger window, or as part of an IM conversation. Plug-ins are supported in the pre-release version of Yahoo Messenger 8

Text-only display of the position, velocity, time, and status information from the Garmin iQue3600. Written to answer some questions that arose on the garminPDA mailing list. Shows all error and velocity components, and elevation referenced to either MSL or WGS-84 datum.
System requirements:
- Garmin iQue3600.