In the following table, you can see how much of the development is done. The table shows major pieces of PalmBeach and
if they need more development or if they are already finished.
| Program piece | Remark | Status |
|---|
| GUI Status |
This view is used to show the user which protocols are already loaded and started.
Perhaps this view will be removed in newer versions. |
80%
|
| GUI Settings |
This view shows all settings that the user can change in PalmBeach.
At the moment you can select the serial port and the serial speed. You can also set the mountpoint
where the PSION volumes are located after connecting. |
80%
|
| GUI Add-Ons |
This view manages all the add-ons. IYou can configure the add-ons and you will get
the version, the add-on-type and three lines of special information. |
99%
|
| Send thread |
This thread manages the sending of data bytes. The data is packed into the
PLP (Psion Link Protocol) and is completed with a CRC.
This thread also manages the correct sending of this data. |
90%
|
| Read thread |
This thread is the opposite of the write thread. All received data is unpacked from the
PLP (Pion Link Protocol) and is delivered to the correct
channels. |
90%
|
| NCP-Protocol |
The NCP-Protocol is used to manage the 7 NCP-channels. At the moment PalmBeach
can only manage 3 commands of all 8 NCP-commands. With this 3 commands it is possible to manage the main functions of the Link |
50%
|
LINK-Protocol
as add-on |
I don't know what the LINK-Protocol is for.
In this add-on no functionality is included, but it is needed because the PSION asks for
the protocol. |
5%
|
RFSV-Protocol
als add-on |
The RFSV-Protocol is the heart of PalmBeach.
This protocol is used to make it possible for the PSION to connect to BeOS volumes.
Unfortunately this protocol isn't used in the PSION 5. At the moment
there is one function which isn't programmed. Also the error handling is missing. |
90%
|
BeOS Filesystem
as kernel add-on |
At the moment it is implemented as a read-only filesystem. Tha attribute
functions are fully implemented. The write access functions for the simple files
have yet to be written. |
50%
|
| Translating functions |
A translation function is needed for every PSION file type. This function is used to read and write
the PSION files from different BeOS programs. |
0%
|
| More protocols |
I think there are many more protocols to implement as add-ons. I don't know exactly
which protocols are needed. As far as I know there is a print protocol and a TCP/IP protocol defined. |
10%
|
I need help implementing new protocols. If you are interested in working with me, then feel free to contact
me. I will send you the information you need to develop protocol add-ons.
