[Development] 5.7 new features and 5.6 changelog

Hi everybody, It would be great if those of you who haven’t done so yet fill in the 5.7 new features page on the wiki (https://wiki.qt.io/New_Features_in_Qt_5.7), so that we can get a good overview over the bigger new features in 5.7. In addition, I’d like to ask every maintainer to have a

[Development] Made with Qt - Bluescape at TED 2016

Hi all, I just wanted to share this piece of news, as a serious piece of hardware and UI is currently featured in the main lobby of the TED 2016 conference in Vancouver, and it's all made with Qt!

Re: [Development] some questions about QtGamePad

On 2016-02-15 15:23, Matthew Woehlke wrote: >> So I do not support expanding the scope of QtGamepad in the way you >> propose, as I think if it belongs anywhere it is in a generic input API >> (or you can always still just wrap SDL's input module pretty easily). > > I might be more inclined to

Re: [Development] some questions about QtGamePad

On 2016-02-15 14:46, Nichols Andy wrote: > QtGamepad is intentionally limited to gamepads, and does not include support > for joysticks, or generic devices with an arbitrary number of axes/buttons. That's... stupid IMNSHO. Especially since... > The design was primarily inspired by the HTML 5

Re: [Development] some questions about QtGamePad

Hi Matthew, Pritam, et alia QtGamepad is intentionally limited to gamepads, and does not include support for joysticks, or generic devices with an arbitrary number of axes/buttons. The design was primarily inspired by the HTML 5 gamepad API:

Re: [Development] some questions about QtGamePad

On 2016-02-15 13:04, Matthew Woehlke wrote: > On 2016-02-15 06:36, pritam.ghang...@gmail.com wrote: >> Looking at the API it seems it has a very hard assumption on 2 sticks and >> 18 buttons. > > Please support arbitrary axes and buttons, as done in e.g. SDL. I wrote a joystick API in Qt a while

Re: [Development] Closing the 5.5 branch

https://codereview.qt-project.org/146557 still need to be integrated. On 8 February 2016 at 14:03, Frederik Gladhorn < frederik.gladh...@theqtcompany.com> wrote: > Hi all, > > due to the strain that we put on the VMs that are supposed to get the > releases > out and do the testing, we decided to

Re: [Development] some questions about QtGamePad

On 2016-02-15 06:36, pritam.ghang...@gmail.com wrote: > Looking at the API it seems it has a very hard assumption on 2 sticks and > 18 buttons. Please support arbitrary axes and buttons, as done in e.g. SDL. Hard-coding this stuff is a terrible idea, as even devices with similar physical

Re: [Development] some questions about QtGamePad

Hi, From a gamepad perspective it's almost complete. Yes I know that there are gamepads out there with more buttons, QtGamepad it's a technical preview, so we can change it. IMHO we just need to add a few more generic buttons/axes and that's it. I also agree with Mike that Qt needs some

Re: [Development] some questions about QtGamePad

Hi, On 15/02/2016 11:36, pritam.ghang...@gmail.com wrote: Hi I have looking at QtGamePad for usage in another opensource project QGroundControl. It looks like a great module already, something that will reduce lot of cross platform headache for a lot of people trying to use joysticks with

Re: [Development] some questions about QtGamePad

+1, looking at it from the AppleTV remote perspective, it also needs support for handling device orientation (tilt sensors, etc) Mike > On 15 Feb 2016, at 11:36, pritam.ghang...@gmail.com wrote: > > Hi > > I have looking at QtGamePad for usage in another opensource project >

Re: [Development] some questions about QtGamePad

I meant potentiometers not photometers in there. On Mon, Feb 15, 2016 at 5:06 PM, pritam.ghang...@gmail.com < pritam.ghang...@gmail.com> wrote: > Hi > > I have looking at QtGamePad for usage in another opensource project > QGroundControl. It looks like a great module already, something that will

Re: [Development] [Proposal] Future QtSerialPort with plugins architecture

> why are you conflating backends and plugins? I don't know why I do it.. ;) > if you feel you need to refactor the code to achieve better structural clarity, i'm all for it - but don't over-engineer it just because you can. yes, I need in "to refactor the code to achieve better structural

[Development] some questions about QtGamePad

Hi I have looking at QtGamePad for usage in another opensource project QGroundControl. It looks like a great module already, something that will reduce lot of cross platform headache for a lot of people trying to use joysticks with Qt. Awesome work by the authors. Looking at the API it seems it

Re: [Development] [Proposal] Future QtSerialPort with plugins architecture

On Sat, Feb 13, 2016 at 02:24:38PM +0300, Denis Shienkov wrote: > I would like to discuss new idea of transition of QtSerialPort to > an architecture with the plug-ins/backends. > why are you conflating backends and plugins? i see no apparent need to make the backends dynamically switchable,

[Development] QAccessibleQuickItem setText

I was exploring accessibility options to run some automation and looks like setting text to an item is not implemented in QAccessibleQuickItem which is preventing me from setting text to text items. https://code.woboq.org/qt5/qtdeclarative/src/quick/accessible/qaccessiblequickitem_p.h.html#83

Re: [Development] Request for a new playground project

And then “backend” is awfully vague, could be anything other than application UI. (QPA is a kind of backend, so is ODBC.) Yes it’s a buzzword, but will it sound too dated or even more vague in 10 years? > On 15 Feb 2016, at 07:30, Petroules Jake > wrote: >

Re: [Development] [Proposal] Future QtSerialPort with plugins architecture

> The system must support the concept of a default plugin for the current platform. Yes, of course. For example, the name of a default plug-in will be defined in DEFINES in the *.pro file at a stage of compilation of the module. > Maybe you forgot to mention it in your mail but choosing the