![]() |
[Announce] TcpIpKeyboard (in development preview) ALPHA-release
ALPHA PREVIEW / TECH DEMO!
BRAVE (and skilled) TESTERS WANTED! :) The N9 has no keyboard. It's not very comfortable while typing sms or mails on the go and it's even worse to work on the shell or to develop directly on this device. In some cases you're at home and you have a keyboard directly in front of you at your desk - but it's connected to your Desktop and for your N9 it is useless. The same takes effect for all MeeGo tablets like at example the ExoPC. I want to try to make this pain less painful! TcpIpKeyboard is a Application to share the Keyboard from a Windows or Linux Desktop PC, Netbook or Laptop with the N9 handset thru a simple TCP/IP connection. http://sites.google.com/site/helexme.../shematics.png It's seperated in 2 applications. A Sender for your Desktop and a Receiver for your N9, MeeGo Tablet (both still under hard development) or your N900. It's very simple: At home you are normally connected with your Mobile via WiFi with your home network. The same network used by your desktop. If you want to use now the Keyboard from your Desktop simply start TcpIpKeyboardReceiver at your Mobile: http://sites.google.com/site/helexme...d/Receiver.png (Screenshot from N900 Version) You can see the IP adress of your Device and a Port Number. You're able to change the Port by pressing the gear wheels Button. Press it again to leave the settings mode. Now open at your Desktop TcpIpKeyboardSender https://sites.google.com/site/helexm...nder_ready.png Go to settings using the gear wheels and enter the IP shown at your Mobile: https://sites.google.com/site/helexm...r_settings.png The red background signaled that you're currently in the settings mode. If the background is green TcpIpKeyboard is ready to work. How to use it: Just keep the Application at the N900 open and switch to the task you wan't to use. It works at all applications and even at the Desktop. As soon as you have the TcpIpKeyboard application at your Desktop PC in the foreground all input from the Keyboard will be sent to your Mobile. Switch to a different task to use your Keyboard as usual at your Desktop. Switch back to TcpIpKeyboard to use it again at your Mobile. It feels so far very good even if there are still a lot of problems:
Where to get it: Receiver:
Enjoy but as always at your own risk! :) The usual warning applies: Quote:
This Application is in early Alpha stage. But the core components are working so far. See it as a preview what is comming to your N9. I announced it now because of the approaching deadline for the MeeGo Coding Competition 2011. Please test it only if you know what you're doing or wait what will happen in this Thread. And don't forget to create a backup (just in case). I only want to share my little application. But I hope for a lot of positive feedback! :) |
Re: [Announce] TcpIpKeyboard (in development preview) ALPHA-release
shhytt...this means my N900 has a long way to do...
|
Re: [Announce] TcpIpKeyboard (in development preview) ALPHA-release
There will be a lot of people eager to test this, I'm sure. Clever idea, so long as network latency is low enough for the hci to be acceptable. Can the N900 form an ad-hoc connection with the kb? Nice one!
A question though: keyboards, other than the native one, can have unexpected results with some keys. How do you handle each key-press and can it be altered to give the desired result? |
Re: [Announce] TcpIpKeyboard (in development preview) ALPHA-release
cool! how about extending this to a mouse as well? :)
|
Re: [Announce] TcpIpKeyboard (in development preview) ALPHA-release
Quote:
After the first problems with network latency (some characters were received in the wrong order) I added a first in-first out stack for the sender and for the receiver module. I will try to add to the communication a response channel if a keycode is sucessfully received or not. But I wan't to use only a single port. Don't know if this could work. I wan't to keep the settings as simple as possible. If there occurs problems with some fast typers I could bundle some keycodes together in a single packet to minimize the overhead. Currently every keycode is sent seperate. If you type to fast your text appears a little bit delayed. But perhaps this is because of the way I send the keycodes to different applications at the N900. Quote:
But at maemo I haven't found something similar to this. I'm currently using the command line tool xdotool to send the keycodes and created manually a table to translate at the N900 the received keycodes in keystrikes. Have a look at this thread: Best way to send keycodes - emulate keyboard press It's a pain and feels unprofessional. Any kind of suggestions are welcome! :D |
Re: [Announce] TcpIpKeyboard (in development preview) ALPHA-release
Quote:
Perhaps possible... I'm able to control my Lenovo IdeaPad with MeeGo using the touchpad and Mousebuttons. But I can't see a the Mousecoursor at the display. So I'm unable to control it and I'm forced to stumble in the dark. :D So, will it really make sense to have a Mouse at the N9? :) |
Re: [Announce] TcpIpKeyboard (in development preview) ALPHA-release
UPDATE v.0.0.4:
|
Re: [Announce] TcpIpKeyboard (in development preview) ALPHA-release
shut a hell up!!!!!!!!!!!!!! :O
great work mate!!!!!!!!!!!!!! :) |
Re: [Announce] TcpIpKeyboard (in development preview) ALPHA-release
wow, cool!
|
Re: [Announce] TcpIpKeyboard (in development preview) ALPHA-release
A way to implement Mouse will be awesome. Good Work mate!!! :D
|
All times are GMT. The time now is 21:44. |
vBulletin® Version 3.8.8