Neo
Neo
Neo is an OBEX implementation for Newton devices running NewtonOS 2.1. It works over IrDA and TCP/IP.
Version: 0.9.4
Author: Eckhart Köppen
License: GPL 2.0
Download: Neo-0.9.4
|
|
|
Neo
|
40Hz
|
|
|
|
|
|
NeoNeo is an OBEX implementation for Newton devices running NewtonOS 2.1. It works over IrDA and TCP/IP. Version: 0.9.4 Author: Eckhart Köppen License: GPL 2.0 Download: Neo-0.9.4 |
|
|
|
|
|
|
Neo installs three OBEX transports (one for Bluetooth, one for IrDA, one for TCP/IP) which can be used to send and receive objects in the same manner as any other transport (e.g. email). IrOBEX is supported by most devices which have IrDA support and does not need to be configured. It requires Nitro on the Newton. OBEX over TCP requires a peer computer running an OBEX stack over TCP/IP, such as OpenOBEX. Bluetooth requires Blunt.
At the moment, data exchange is possible with objects that have a textual representation. In addition to that, IC/VC allows sending of Names and Dates objects as iCalendar and vCard data as well as importing iCalendar, vCalendar and vCard data.
Note that Neo does currently not check carefully for object sizes. Sending and receiving large objects might fail and crash the Newton.
Sending an object simply requires that the receiving device is ready (e.g. by enabling automatic reception or by connecting manually) and sending the object via the action menu of the application. The current implementation of Neo converts the object to text and sends it.
Receiving data via IrOBEX is controlled by the I/O box application of the Newton. Neo adds an option for this under the receive picker, the menu item name is "IrOBEX". Reception starts as soon as the IrOBEX option from that picker has been chosen. As soon as Neo indicates that it is looking for a sender, data can be sent from the peer device. The received object can at the moment be put away to the Notepad if it is a text object. Support for other formats will be added.
Sending a data item wit OBEX over TCP requires a peer computer listening on the standard OBEX port (650). Neo asks for the host address in the route slip and connects to that host via TCP/IP.
Receiving is initiated via the "Receive" menu in the I/O box application. The menu item is named "TCPOBEX". When selecting TCPOBEX, the first step is to initiate an Internet connection. Then, reception starts. Finally, any received items are placed in the Inbox.
The preferences setting for TCPOBEX contain regular transport settings, e.g. controlling the sending process and the put away mechanism.
OBEX over Bluetooth works like OBEX over IrDA. It requires however that the peer devices have been discovered beforehand using the Bluetooth Setup application.
Version 0.9.4: Added .tx as recognized suffix for the WizCom pen
Version 0.9.3: Fixed vCalendar sending (needs IC/VC 2.0.3)
Version 0.9.2: Fixed incorrect MIME type assignment for images
Version 0.9.1: Added TapBar buttons for receiving TCPOBEX
Version 0.9: Added TapBar buttons for receiving IrOBEX and BtOBEX
Version 0.8: Added Bluetooth support
Version 0.7: Added receiving OBEX over TCP
Version 0.6: Added OBEX over TCP, split from Nitro
Version 0.5: Added packet size preference for OBEX
Version 0.4: Added automatic detection of packet size for OBEX
Version 0.3: Support for receiving large objects
Version 0.2: Initial OBEX release
Since I cannot field test all possible combinations of peer devices and protocols, it is important that as many people as possible report feedback regarding successful usage, bugs or crashes when using Nitro. The following list contains some useful information for feedback (positive or negative):
The following feedback has been reported so far: