Free sdk software for pda

Palm SDK (Mac) 4.0 is a very flexible and effective tool which is used to create applications that run on the Palm OS.

It includes headers and libraries for Palm OS 3.0, documentation for APIs, source code for built-in applications, and source code for the 21-step tutorial. It also features unsupported tools, including a low-level debugger, MPW tools, and the Palm OS Emulator.

The SDK 4.0 contains the latest headers, libraries, and tools for Palm OS platform development on the Mac OS.

The Download Now link will open the developer's License Agreement page where you must accept licenesing terms before downloading the product. You may then download the product from a list on the resulting page.

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

SuperWaba is a Virtual Machine that can be run in Palm OS, Symbian, Pocket PC, Windows CE, AppletViewer and Windows 98 (and beyond). Because of the way SuperWaba was written, you can use Java to develop for it. You can write and debug the programs in your favorite Java IDE. When finish testing, just upload it to your handheld device.
SuperWaba is an open source project, covered by the GPL and LGPL licenses.
SuperWaba is a VM for PDAs and Smartphones. Because of the way SuperWaba was written, you can use Java to develop for it. Can run in PalmOS, Symbian, Windows CE/PocketPC devices, and in Windows 98/NT/2000/XP, and is fully emulated under JDK and browser. Theres now a test version on Sony PSP!
Note: This version runs on Windows Mobile Pocket PC!
Enhancements:
- Removed support for the following platforms: UIQ (P800), HPC2000_MIPS, HPC211_SH3, HPC211_MIPS. These pdas are rather old and we dont believe someone is still using them. This will make the SDK smaller. If you try to install the vm and the installation now fails, contact us and well send you the files and maybe put back the removed platform (if many people needs it).
- 1. When an error 500 occurs, the SOAP class gets the error reason from the returned message and displays it in the exception. Increased SOAP, XmlTokenizer and HttpStream default buffer sizes from 512 to 1024, so the error message can be read at once.
- 2. now when the user hold the action key for a while in wince and symbian, the menu is popped up. before this, it was impossible to open the menu in penless devices. Note that now the ACTION key event is dispatched when the key is released and Settings.actionOnRelease is true (default). On Palm OS, actionOnRelease is ignored.
- 3. added Vm.tweak to enable, during the running instance, some parameters that are available when running the Welcome application.
- 4. added ColorList.setColors to set the colors that will be displayed.
- 5. fixed color of ScrollBars bar when both buttons are disabled (on Palm OS style).
- 6. added Convert.getStackTrace, which returns the stack trace for a given Throwable as a String. CAUTION: getting a stack trace can cause device reset, because theres a lack of information in the SuperWaba vm about method frames, and during the stack crawl, it can access an invalid memory region, causing the reset.
- 7. now the Esc key also exits from the MultiEdit and Edit on penless devices.
- 8. added SoundClip support for java applications at desktop (before, only java applets was supported).
- 9. changed the motoq button at the RIGHT SIDE of the pda from BACKSPACE to ACTION. Otherwise, it is impossible to exit from a MultiEdit, because (only) on this phone the center button is mapped to 13 (enter) instead of 134 (action).
- 10. brunosoares - fixed HttpStreams content-length not being correctly retrieved under some situations.
- 11. brunosoares - fixed HttpStreams and Sockets readLine not reading lines correctly (now returns null only when no more lines are available).
- 12. brunosoares - added support to 3xx response codes (redirection) in HttpStream. Included an attribute which contains the new location: URI location.
- 13. brunosoares - fixed MainWindows swap() method that was causing a container to be focused instead of its first focusable control on penless devices (only when a container was added to another container).
- 14. fixed Button on Vista ui style: now when it has BORDER_NONE, only a flat background is drawn in the control.
- 15. fixed the focus getting out of a Grid on penless mode when an item was selected on a cells combobox.
- 16. fixed problem on Grid with combobox on penless devices: put the focus on a grid, select a line, press ACTION and press 0 to open the combobox - the program freezes.
- 17. fixed Settings.appPath at desktop not ending with a slash.
- 18. fixed support for passive scanners (SocketCom).
- 19. now when the user press a 0-9 key in the Grid in penless mode, the selected column flashes.
- 20. fixed printStackTrace when sending the buffer to the string not keeping the line number.

J2METools is a collection of scripts I use during development of J2ME programs. Theyre somewhat generic but they will probably not replace any full featured IDE. Nevertheless, the can probably serve as a starting point for you as well.
These tools are for the Linux platform only.
The tools are:
Emulators: n6230, n6310i, n7210, s30emul. These scripts serves as wrappers around some of the various Nokia SDK emulators. The n6310i and n7210 scripts runs in the context of Wine.
j2mejdb - a quick way to launch jdb. This script ties nicely to n6230 and s30emul.
j2metrans - transfer jad/jar file to a (possibly) bluetooth enabled phone.
Emulators
General usage is ... (s30emul used as an example):
Usage: /usr/bin/s30emul [OPTIONS] file
[OPTIONS]
-h Help (this ..)
-m home SDK home
You need to set ${emulator}_HOME (or give the -m switch) to point to the correct SDK. Run the wrapper script without arguments to see the search path.
The file argument is the jad file to read. If a filename without the suffix (.jad) is given .jad is appended.
I have the following in my /etc/profile.local:
nd=/opt/Nokia/Devices
N6230_HOME=$nd/Nokia_6230_MIDP_Concept_SDK_Beta_0_2
N6310I_HOME=$nd/Nokia_6310i_MIDP_SDK_v1_1
N7210_HOME=$nd/Nokia_7210_MIDP_SDK_v1_0
S30EMUL_HOME=$nd/Nokia_Series_30_MIDP_Concept_SDK_Beta_0_2
export N6230_HOME N6310I_HOME N7210_HOME S30EMUL_HOME
unset nd
... so that the emulator homes are set correctly up.
The n6230 script can be launched in debug mode by specifying the -d argument. Use -D string to setup a default connection string.
The s30emul script can be launched in debug mode by specifying the -d argument. Use -p portnum to specify debug port.
j2mejdb
j2mejdb launches the jdb debugger. Specify -H hostname and -p portnum to override the default settings of localhost:4452.
j2metrans
Transfer jad/jar files to a mobile phones. You need to have Gammu installed and configured.
Usage is:
Usage: j2metrans [OPTIONS] prog1 prog2 ... progN
[OPTIONS]
-c configNum Gammu configuration
-d debugLevel Gammu debug level (nothing|text|textall|binary|errors)
-g group Group name (Application|Game)
-h This page
Enhancements:
- added the j2metrans script
- added the j2mejdb script
- added the -D and -d (debug) flags to n6230
- added the -d and -p flags to s30emul
- renamed the suite from emulators to J2METools

WmConsole is a console server for Windows Mobile devices, that listen over BlueTooth RFCOMM channels, and allows the user to interact with the device using a command line interface from a Linux or Windows workstation.
Once the WmConsole server is run, itll listen on a configurable RFCOMM channel by waiting for client connections.
The server also creates a new SDP service called "WmConsole", and advertises it as running onto its listening channel. From the client side, the QTTY program has to be used to connect to the WmConsole server.
The QTTY software can be built for Linux (needs the BlueZ package) and Windows (needs the Microsoft SDK - but a pre-built binary is also supplied).
Once logged-in, the user will be able to access a thoruogh set of commands to interact with the device (file upload/download, directory/tree creation/removal, process creation with STDOUT redirection, process kill, file search, registry manipulation/search, reboot, and many others - the help command will list them all, together with a brief description).
Since Windows Mobile does not allow handle inheritance and standard input/output redirection, a special device driver (RConsole) is used in order to achieve binaries execution with output on the console.
The RConsole device driver manages a kernel pipe (ten actually - from 0 up to 9), and together with the SetStdioPathW() library call, allows WmConsole to execute an external binary by capturing its output on the console.
This came really handy to me, since it allowed the creation and usage of simple command line utilities that where using standard POSIX stdio output.
The WmConsole binary is installed inside the "Program FilesWmConsole" directory, and it must be manually run using File Explorer.
WmConsole listen by default on the RFCOMM channel 11, but this can be changed either by specifying the "-P CHNUM" command line parameter, or by creating a registry string value named "Channel" inside the "HKEY_LOCAL_MACHINESOFTWAREWmConsole" key and by setting its value to the desired one. The default username and password for the WmConsole server are user="wmconsole" and password="server".
The "Program FilesWmConsolepasswd" file stores the usernames and passwords, that youre suggested to change if you plan to keep the WmConsole server permanently running on your device.
Look at the QTTY page for instructions on how to use it to login into a WmConsole (or QConsole) server.

Requirements: Pocket PC