Re: [Development] Removing QT_{BEGIN,END}_HEADER macros in Qt 5.1

On segunda-feira, 14 de janeiro de 2013 23.09.48, Ahumada Sergio wrote: > Hi, > > While I was trying to mark tst_headers as significant again > I found out that I > had to add some QT_{BEGIN,END}_HEADER macros to some headers. > > After som

[Development] Removing QT_{BEGIN,END}_HEADER macros in Qt 5.1

Hi, While I was trying to mark tst_headers as significant again I found out that I had to add some QT_{BEGIN,END}_HEADER macros to some headers. After some investigation and talks with Thiago, I realized this macro expands to nothing, so

Re: [Development] QML Runtime

On Mon, Jan 14, 2013 at 7:12 AM, Koehne Kai wrote: > >... > > So your idea is to consolidate on one qml binary, effectively deprecating > qmlviewer and qmlscene? Sounds like a plan. I don't think we've 'deprecated' > binaries in Qt before, but I personally don't see a big problem even removing

Re: [Development] Move QAction from QtWidgets to QtGui

There was a general agreement to add QGuiAction in a previous thread on the dev list (Integrating QAction and the upcoming QML Action). It's just that work on it hasn't started yet, if you want to contribute you could see it done faster :) . As for the API of QGuiAction I got the impression it was

Re: [Development] ICU and Windows

On segunda-feira, 14 de janeiro de 2013 13.02.46, Shaw Andy wrote: > Therefore I would like to propose that for 5.0.1 we simply modify the pro > file so that it expects a d after the library name for the debug version > and the release one stays as it is. What we could do to make it more > robust

Re: [Development] QML and QAbstractListModel

On Mon, Jan 14, 2013 at 3:37 AM, Alberto Mardegan wrote: > On 01/14/2013 11:37 AM, André Somers wrote: > [...] >> top of them. Note that you can also use a proxy to map a table model to >> a list by mapping the data in columns to different roles. The base class >> would not be a QListModel, but th

Re: [Development] QML Runtime

> -Original Message- > From: Alan Alpert [mailto:4163654...@gmail.com] > Sent: Thursday, January 10, 2013 5:11 PM > To: Koehne Kai > Cc: Sorvig Morten; development@qt-project.org > Subject: Re: [Development] QML Runtime > > On Wed, Jan 9, 2013 at 11:57 PM, Koehne Kai > wrote: > > > > >

Re: [Development] Platform Content Selection

On 10 Jan 2013, at 01:32, Chris Adams mailto:chris.ad...@qinetic.com.au>> wrote: Hi, This is an interesting topic. I'm not sure that I'm convinced by anyone's arguments so far, to be honest. More comments inline: > import paths can achieve basically what we want, so for example > high_res/bl

Re: [Development] QtCreator "Generic Linux Device" plugin questions

On 01/14/2013 01:51 PM, a.gra...@gmail.com wrote: >> There is a pre-configured upload step in the plugin, which uses SFTP. >> See the deployment part of your project for the details. This currently >> works only for qmake-based projects. The files to deploy are specified >> via the .pro file's INST

Re: [Development] ICU and Windows

To get things back on track, I think we have a case for either way saying that we could ignore it as since as long as it's done the correct way then it should be fine. But there is also a case for doing the right thing as far as what is recommended by Microsoft in this case especially since we

Re: [Development] ICU and Windows

On Mon, Jan 14, 2013 at 1:31 PM, Konstantin Tokarev wrote: > >> On segunda-feira, 14 de janeiro de 2013 08.31.19, Yves Bailly wrote: > >>> Which is not always that easy... if a library function returns, say, an > >>> simple std::string *by value*, then who will destroy the allocated > memory? > >

Re: [Development] ICU and Windows

Le 14/01/2013 13:31, Konstantin Tokarev a écrit : > > 14.01.2013, 15:56, "Pau Garcia i Quiles" : >> On Mon, Jan 14, 2013 at 9:35 AM, Thiago Macieira >> wrote: >> >>> On segunda-feira, 14 de janeiro de 2013 08.31.19, Yves Bailly wrote: Which is not always that easy... if a library function re

Re: [Development] QtCreator "Generic Linux Device" plugin questions

Hi! On 14 January 2013 10:43, Christian Kandeler wrote: > Note that this question should really go to the Creator mailing list; > see http://lists.qt-project.org/mailman/listinfo/qt-creator. Staying on > this one for now. oh sorry for that, I really didn't know we have a mailing list for that. I

Re: [Development] ICU and Windows

14.01.2013, 15:56, "Pau Garcia i Quiles" : > On Mon, Jan 14, 2013 at 9:35 AM, Thiago Macieira > wrote: > >> On segunda-feira, 14 de janeiro de 2013 08.31.19, Yves Bailly wrote: >>> Which is not always that easy... if a library function returns, say, an >>> simple std::string *by value*, then who

[Development] input method support in Qt5 (linux)

After looking at Qt4 / Qt5 source code and doing some internet search I see that ibus plugin has become a part of Qt, where in Qt4 it was a separate plugin hosted somewhere else.. Qt4 offered two options XIM and IBUS, selectable by using 'qtconfig' tool, currently Qt5 has support only for ibus

Re: [Development] ICU and Windows

On Mon, Jan 14, 2013 at 9:35 AM, Thiago Macieira wrote: On segunda-feira, 14 de janeiro de 2013 08.31.19, Yves Bailly wrote: > > Which is not always that easy... if a library function returns, say, an > > simple std::string *by value*, then who will destroy the allocated > memory? > > It's really

Re: [Development] QML and QAbstractListModel

On 01/14/2013 11:37 AM, André Somers wrote: [...] > top of them. Note that you can also use a proxy to map a table model to > a list by mapping the data in columns to different roles. The base class > would not be a QListModel, but the data would be available from the > first column anyway. When us

Re: [Development] QML and QAbstractListModel

Op 14-1-2013 11:07, Alberto Mardegan schreef: > On 01/14/2013 09:29 AM, André Somers wrote: >> I am not fan of this change. I think the API of QAIM is already very >> complex. Adding more methods that basically only sort-of mirror existing >> methods but for a more confined use-cases only makes tha

Re: [Development] QML and QAbstractListModel

On 01/14/2013 09:29 AM, André Somers wrote: > I am not fan of this change. I think the API of QAIM is already very > complex. Adding more methods that basically only sort-of mirror existing > methods but for a more confined use-cases only makes that situation > worse. For instance, you now get a co

Re: [Development] QtCreator "Generic Linux Device" plugin questions

On 01/12/2013 05:11 PM, a.gra...@gmail.com wrote: > I'm trying to understand how the "Generic Linux Device" plugin of > QtCreator works and I've some questions to ask, to understand if it > already does what I need or if I need to fork it and customize for my > needs. Note that this question shoul

Re: [Development] QML and QAbstractListModel

> Perhaps an alternative approach would be to create a proxy model for > exporting to QML. It could include all the methods you need, but it > would not complicate QAIM itself. It seems to me that all the methods > you need can be implemented in terms of the already existing > functionality in QAIM

Re: [Development] The future of the "Ministro" brand on Android

On 01/13/2013 12:14 PM, Olivier Goffart wrote: > On Saturday 12 January 2013 11:23:33 BogDan wrote: > >>Currently Ministro's repo is hosted by KDE, I accepted to move it to a >> qt-project repo because Eskil was worried about the potential contributors >> (currently I'm the only developer) whic

Re: [Development] ICU and Windows

On segunda-feira, 14 de janeiro de 2013 08.31.19, Yves Bailly wrote: > Which is not always that easy... if a library function returns, say, an > simple std::string *by value*, then who will destroy the allocated memory? > It's really too easy to break something, somwhere, causing a random crash > a

Re: [Development] QML and QAbstractListModel

Op 10-1-2013 17:46, Alberto Mardegan schreef: > Hi all! > I'd like to make C++ models more usable from QML; in the net there > are several blog posts illustrating how to achieve that, but IMHO it > would be better if at least some of these handy features were in > QAbstractListModel itself: > >