Re: [MeeGo-dev] Enable contour shuttlexpress or shuttlepro in MeeGo 1.2? (vs total wiimote success)
The article describes the Contour ShuttleXpress support in the ivihome ividesktop packages used in the MeeGo IVI images. http://repo.meego.com/MeeGo/builds/trunk/1.1.99.4.20110426.4/repos/oss/source/ivihome-1.18-4.24.src.rpm http://repo.meego.com/MeeGo/builds/trunk/1.1.99.4.20110426.4/repos/oss/source/ividesktop-1.2-2.6.src.rpm I understand the device is seen as a mouse, not a joystick. regards Joel -Original Message- From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of Niels Mayer Sent: Saturday, April 30, 2011 7:25 PM To: meego-dev@meego.com Subject: [MeeGo-dev] Enable contour shuttlexpress or shuttlepro in MeeGo 1.2? (vs total wiimote success) In http://www.linuxjournal.com/article/10935?page=0,2 Ibrahim Haddad writes: Figure 9. The MeeGo IVI home screen with the taskbar as it appears on the left side of the screen. The taskbar, [...] can be controlled by a Contour ShuttleXpress scroll wheel, touchscreen or mouse, and it's designed to reflect the scroll-wheel usage, with the ability to spin through the menu options and make selections or go back, by pressing two buttons or tapping the touchscreen (photo credit: meego.com). Seeing this, I plugged into my MeeGo 1.2 netbook my first generation countour shuttlepro (ca 2002, something I'd given up on having an interface written for Linux until I read the above) and lsusb(1) reports; Bus 002 Device 002: ID 0b33:0010 Contour Design, Inc. But doesn't seem to recognize it. Any suggestions, or should I keep giving up? Chances are it needs a program to interpret events and translate them to keyboardjoystick events, much like wminput(1) does for the Wiimote (*). Is there any way of separating out the MeeGo IVI's ShuttleXpress code for use by other UX's, such as a custom input daemon which handles it? -- Niels http://nielsmayer.com PS: (*) one device not to give up on is the old Wii video game Wiimote. Trivial to pair and setup with wmgui(1): ( http://abstrakraft.org/cwiid/ ). The GUI looks like this in MeeGo 1.2 while pressing a few buttons and moving around: http://nielsmayer.com/meego/wmgui-for-wiimote-and-nunchuk-via-bluetooth-on-meegolem.png . You can also run another cwiid program wminput(1) and then it turns the Wiimote into a mouse control and the various buttons work as well. Turns the Wiimote into an xbmc(1) remote. Guess I know how I'll be controlling a future home-made MeeGo set-top box. :-) PPS: I guess a QtMobility sensors interface to the Wiimote accelerometers would be too much success for one experiment... wiining! ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] MeeGo compliance and Qt Commercial license
Hi folks, My apologies if this has been discussed in the past already but I'm struggling to get a definite answer to this question: - Can someone switch to the Qt Commercial license [1],[2] and yet pass the MeeGo compliance test? Cheers, Geoffroy [1] http://qt.nokia.com/products/licensing/licensing#qt-commercial-license [2] As opposed to the license used in MeeGo currently: LGPLv2.1 with exception or GPLv3 Intel Corporation NV/SA Kings Square, Veldkant 31 2550 Kontich RPM (Bruxelles) 0415.497.718. Citibank, Brussels, account 570/1031255/09 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [ANNOUNCE] First commit of QML based MeeGo Dialer application.
Hello All, For those interested, made a few screenshots of the app on the Nokia N900, running the N900 MeeGo 1.2 DE Alpha release: http://stage.rubyx.co.uk/meego/screenshots/handset/ Enjoy! Tom Swindell (AKA alterego) On Sat, 2011-04-30 at 16:24 +0100, Tom Swindell wrote: I've been working over the past few months, when I could, on replacing the current MeeGo Touch Framework based user interface of the reference dialer application with a QML based user experience. I've hit a good state to start publishing my work and have published and will continue to update a QML branch of the reference dialer on gitorious.org Currently my QML dialer branch can make and receive calls, if set up correctly, a handset can receive calls from power on. This is something that mainly Shane Bryan (sabotage) and others have been working on in the headless (now master) branch of the meego-handset-dialer reference project: (https://meego.gitorious.org/meego-handset-ux/meego-handset-dialer) Anyhow, the source for my branch can be found here: https://meego.gitorious.org/~tswindell/meego-handset-ux/qml-meego-handset-dialer All input and comments welcome. There is certainly still quite a bit of work that needs to be done; implementing second call and group call UX as well as modify history, contacts and favourite contacts data models so they expose QML friendly interfaces and can be used correctly in QML list views. Enjoy! Tom Swindell (AKA alterego) ___ MeeGo-handset mailing list meego-hand...@lists.meego.com http://lists.meego.com/listinfo/meego-handset ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] MeeGo compliance and Qt Commercial license
On 5/1/2011 2:11 AM, VanCutsem, Geoffroy wrote: Hi folks, My apologies if this has been discussed in the past already but I’m struggling to get a definite answer to this question: - Can someone switch to the Qt Commercial license [1],[2] and yet pass the MeeGo compliance test? you're not allowed to replace Qt and stay compliant... (you are allowed to add patches that fix bugs and don't change abi of course) if you can get a commercial license on the bits we ship, you could be compliant, but my understanding is that you have to use commercial bits to get the commercial support.. and that would not be ok. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] MeeGo compliance and Qt Commercial license
On Sunday, 1 de May de 2011 08:39:02 Arjan van de Ven wrote: On 5/1/2011 2:11 AM, VanCutsem, Geoffroy wrote: Hi folks, My apologies if this has been discussed in the past already but I’m struggling to get a definite answer to this question: - Can someone switch to the Qt Commercial license [1],[2] and yet pass the MeeGo compliance test? you're not allowed to replace Qt and stay compliant... (you are allowed to add patches that fix bugs and don't change abi of course) But if you replace it with the same Qt... ? Or replace it with the same Qt minus the extra patches we ship? The problem are patches like the XInput2 multi-point touch support... if you can get a commercial license on the bits we ship, you could be compliant, but my understanding is that you have to use commercial bits to get the commercial support.. and that would not be ok. You can get support on the open source version too. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Senior Product Manager - Nokia, Qt Development Frameworks PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 signature.asc Description: This is a digitally signed message part. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] MeeGo compliance and Qt Commercial license
On 5/1/2011 8:58 AM, Thiago Macieira wrote: On Sunday, 1 de May de 2011 08:39:02 Arjan van de Ven wrote: On 5/1/2011 2:11 AM, VanCutsem, Geoffroy wrote: Hi folks, My apologies if this has been discussed in the past already but I’m struggling to get a definite answer to this question: - Can someone switch to the Qt Commercial license [1],[2] and yet pass the MeeGo compliance test? you're not allowed to replace Qt and stay compliant... (you are allowed to add patches that fix bugs and don't change abi of course) But if you replace it with the same Qt... ? nope Or replace it with the same Qt minus the extra patches we ship? The problem are patches like the XInput2 multi-point touch support... nope you can only add patches that fix bugs and don't change interfaces... ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
