Pàdé version 1.0.0

See change log for details.

You will also need to use the Openfire Meetings plugins with latest Jitsi code provided here for better compatibility and support of mobile chrome browser.

Known Issue - Openfire Meetings is not working with Openfire 4.3.1. Wait for 4.3.2 or downgrade to 4.3.0

Pàdé version 0.9.3

See changelog for details

You will also need to use the Openfire Meetings plugins with latest Jitsi code provided here for better compatibility and support of mobile chrome browser

Pàdé version 0.8.0

See changelog for details

You will also need to use the Openfire Meetings plugins provide here for better compatibility and support of mobile chrome browser

Pàdé Chrome Extension version 0.7.0

This is the generic unbranded Pàdé chrome extension available as a CRX file. This has the same features as Pade@Work and Pade@Home available from the Chrome web store.

Pàdé Native Messaging Binary Applications (Windows)

These are the desktop applications that need to be installed on the desktop. They are required to extend Pàdé with features that are not directly supported from a web browser, but can be accessed by the browser using native messaging. They have been built with the Inno setup tool.

Version 0.2 adds Pade@Home to each application's white-list

1. Remote desktop control
   Install if you want Pàdé to give remote control to a participant in a meeting. It is not required for the remote participant that intends to control. Chrome native messaging is used to pass signal messages between Pàdé and the Java application while the WebRTC data channel is used to pass the mouse/keyboard events between the remote controller and the controlled desktop
   See #24 and https://github.com/igniterealtime/Pade/tree/master/remotecontrol for details.

2. Elgato Steam Deck
   Install if you have an Elgato Stream Deck device plugged into the USB port of your desktop. Chrome native messaging is used to pass signal messages between Pàdé and the Java application to use the Stream Deck as a TouchPad. See #21 for details.

3. Jabra Device Support
   Install if you have a Jabra 410, 510, 710 or 810 device plugged into the USB port of your desktop. Chrome native messaging is used to pass signal messages between Pàdé and the binary application to control the device. You can accept meeting/conversation invitations with the green button and close/terminate meetings with the red button.

Pàdé Chrome Extension ver 0.6.0

This is the generic unbranded Pàdé chrome extension available as a CRX file. This has the same features as Pade@Work and Pade@Home available from the Chrome web store

Pàdé Stream Deck (Windows)

This is the first release of the Pàdé Stream Deck setup/installer for Windows. It was built with the Inno setup tool.

You only need to install this Java application on your desktop if you have an Elgato Stream Deck device plugged into the USB port of your desktop. Chrome native messaging is used to pass signal messages between Pàdé and the Java application to use the Stream Deck as a TouchPad

See #21 for details.

Pàdé Jabra Device Support (Windows)

This is the first release of the Pàdé Jabra device setup/installer for Windows. It was built with the Inno setup tool.

You only need to install this Java application on your desktop if you have a Jabra 410, 510, 710 or 810 device plugged into the USB port of your desktop. Chrome native messaging is used to pass signal messages between Pàdé and the Java application to control the device. You can accept meeting/conversation invitations with the green button and close/terminate meetings with the red button.

Pàdé Remote Control (Windows)

This is the first release of the Pàdé Remote Control setup/installer for Windows. It was built with the Inno setup tool. See #24 and https://github.com/igniterealtime/Pade/tree/master/remotecontrol for details.

You only need to install this Java application on your desktop if you want Pàdé to give remote control to a participant in a meeting. It is not required for the remote participant that intends to control. Chrome native messaging is used to pass signal messages between Pàdé and the Java application while the WebRTC data channel is used to pass the mouse/keyboard events between the remote controller and the controlled desktop