On Fri, Apr 20, 2012 at 06:33:54PM -0400, andy fillebrown wrote:
> Here are some attachments from a run using Creator 2.5 beta. The
> project was built with the mingwbuild containing gcc 4.6.2 and gdb
> 7.4. The .txt and .png suffixed with "call-stack" are the debugger
> log and a screen-capture
That's a strongly biased poll due to the wording. And it's missing the points
the Lars has been trying convey, but some seem to ignore.
--
Sent from my Nokia N9On 4/20/12 17:31 ext d3fault wrote:
*cough*
http://qt-project.org/forums/viewthread/16465/
Does Qt need a modern C++ GUI API?
-No, I a
On Fri, Apr 20, 2012 at 3:23 PM, André Pönitz
wrote:
> On Fri, Apr 20, 2012 at 03:08:01PM -0400, andy fillebrown wrote:
>> [...]
>> GCC 4.6.2 and 4.7.0 from mingwbuilds do not have the slow startup
>> problem. There are still two issues, though.
>
> I still don't think the gcc matters much in thi
*cough*
http://qt-project.org/forums/viewthread/16465/
Does Qt need a modern C++ GUI API?
> -No, I am perfectly happy with QML, JavaScript, interpreters, virtual
> machines, glue code, glue abstract and proxy object
> -Yes, I’d like the option of 100% native development without being left
> behin
On Fri, Apr 20, 2012 at 03:08:01PM -0400, andy fillebrown wrote:
> [...]
> GCC 4.6.2 and 4.7.0 from mingwbuilds do not have the slow startup
> problem. There are still two issues, though.
I still don't think the gcc matters much in this case. gdb version
certainly does.
> 1) Breakpoints have to
On Fri, Apr 20, 2012 at 8:07 AM, André Pönitz
wrote:
> On Fri, Apr 20, 2012 at 11:19:50AM +0200, Pau Garcia i Quiles wrote:
>> On Fri, Apr 20, 2012 at 11:12 AM, andy fillebrown
>> wrote:
>> > On Fri, Apr 20, 2012 at 2:01 AM, André Pönitz
>> > wrote:
>> >> On Thu, Apr 19, 2012 at 10:34:21PM -0400
On sexta-feira, 20 de abril de 2012 18.40.15, Laszlo Papp wrote:
> Hi,
>
> Sorry for bringing this thread up again, and my sincere apologize, if
> this is not the best way to come up with a new realization.
>
> [...]
>
> > https://wiki.qt-project.org/Creating_a_new_module_or_tool_for_Qt
>
> http://
Hi,
Sorry for bringing this thread up again, and my sincere apologize, if
this is not the best way to come up with a new realization.
[...]
> https://wiki.qt-project.org/Creating_a_new_module_or_tool_for_Qt
http://wiki.qt-project.org/Creating_a_new_module_or_tool_for_Qt#The_structure_of_a_new_mo
> 2) make it possible to add any user to the watcher list
> The only way today of requesting information from someone else is to assign
> the task. That means I can't ask for information from two people.
For this case there is JIRA Email This Issue Plugin. May be need to use it?
2012/4/20 Stephen Kelly :
> On Friday, April 20, 2012 07:35:39 lars.kn...@nokia.com wrote:
>
>> Proposal sounds ok to me as well. If someone still has concerns, please
>
>> speak up.
>
>
> I lost track of what the proposal currently is. Could it be restated?
1. We drop _qpa completely. So, it woul
>>2) make it possible to add any user to the watcher list
>> The only way today of requesting information from someone else is to assign
>> the task. That means I can't ask for information from two people.
>
>You already can add other people to the watcher list (or at least I can, but
>maybe it re
On 20/04/2012 08:21, ext Sergio Ahumada wrote:
> On 04/20/2012 03:12 PM, ext Thiago Macieira wrote:
>> Additionally, I'd like to request a review that every approver in the Qt
>> Project has an account and that it is correctly in the OGApprovers group.
>> While cleaning up my tasks, I noticed two a
>1) automatically add every commenter to the Watch list, upon making a comment
> Many people used to Bugzilla don't realise that they will not receive answers
> back unless they add themselves to the Watchers list. This means we never get
> replies that we need.
I have experienced the same frustra
On 04/20/2012 03:12 PM, ext Thiago Macieira wrote:
> Hello
>
> Here are a couple improvements I'd like to suggest to JIRA:
>
> 1) automatically add every commenter to the Watch list, upon making a comment
> Many people used to Bugzilla don't realise that they will not receive
> answers
> back
Hello
Here are a couple improvements I'd like to suggest to JIRA:
1) automatically add every commenter to the Watch list, upon making a comment
Many people used to Bugzilla don't realise that they will not receive answers
back unless they add themselves to the Watchers list. This means we never
Hi,
We have been working with Qt 4.8.2 content and it seems to be quite stable as
it should be for patch release.
Content freeze for Qt 4.8.2 is planned to be during Monday 23.4.
If you know that there are some fixes which should be in Qt 4.8.2 content
please send email to releas...@qt-project.o
On Fri, Apr 20, 2012 at 11:19:50AM +0200, Pau Garcia i Quiles wrote:
> On Fri, Apr 20, 2012 at 11:12 AM, andy fillebrown
> wrote:
> > On Fri, Apr 20, 2012 at 2:01 AM, André Pönitz
> > wrote:
> >> On Thu, Apr 19, 2012 at 10:34:21PM -0400, andy fillebrown wrote:
> >>> I would add to the "proper com
Now wait a minute, I never said such a thing.
I said that the MinGW-w64 binaries are Cygwin-based now. Meaning, the
MinGW they release needs Cygwin DLLs to run.
The output they generate is still native Win32 binaries, which does
_not_ require Cygwin. (Anything else would be silly, since you cou
Hi,
I'd say you are confusing "mingw-w64 is available in Cygwin" (like
mingw.org is) with "mingw-w64-produced binaries need Cygwin DLLs".
I've been using mingw-w64 for zsync on Windows (
https://www.assembla.com/spaces/zsync-windows ) for quite some time
and the zsync.exe and zysncmake.exe binari
Take another look. They haven't produced pure MinGW binary releases
since the end of 2011. The front page says "The mingw-w64 toolchain has
been officially added to Cygwin mirrors", and when you look under the
"Releases" (and then under "Automated Builds") section to the left on
the front page,
Hello Everybody!
David has been working hard on the Qt Creator editor functionality for the last
months. For this reason I am proposing David Schulz as a approver in the Qt
project.
Best Regards,
Tobias
Tobias Hunger
Software Engineer
Nokia, Qt Development Frameworks
Nokia gate5 GmbH
Firmensi
On Fri, Apr 20, 2012 at 11:12 AM, andy fillebrown
wrote:
> On Fri, Apr 20, 2012 at 2:01 AM, André Pönitz
> wrote:
>> On Thu, Apr 19, 2012 at 10:34:21PM -0400, andy fillebrown wrote:
>>> I would add to the "proper compiler" list the ability to set debug
>>> breakpoints quickly and proper display o
On Fri, Apr 20, 2012 at 2:01 AM, André Pönitz
wrote:
> On Thu, Apr 19, 2012 at 10:34:21PM -0400, andy fillebrown wrote:
>> I would add to the "proper compiler" list the ability to set debug
>> breakpoints quickly and proper display of call stacks across .dll
>> boundaries. IMO those are the two t
On Apr 20, 2012, at 9:59 AM, ext Laszlo Papp wrote:
Do you plan to set up a wiki any soon ? I personally like going to
those wiki pages for information about how to build a certain add-on,
what the known issues are and so forth. Something like:
http://qt-project.org/wiki/QtDesktopComponents
Good
On Friday, April 20, 2012 07:35:39 lars.kn...@nokia.com wrote:
> Proposal sounds ok to me as well. If someone still has concerns, please
> speak up.
>
I lost track of what the proposal currently is. Could it be restated?
--
Stephen Kelly | Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a K
Hi,
2012/4/17 :
> Desktop Compoents are not going to be a part of the Qt 5.0 release, but we'd
> still like to get it up to speed and open up for contributions through
> gerrit.
>
> Task: https://bugreports.qt-project.org/browse/QTQAINFRA-501
Do you plan to set up a wiki any soon ? I personally
Proposal sounds ok to me as well. If someone still has concerns, please
speak up.
Cheers,
Lars
On 4/20/12 9:02 AM, "ext Samuel Rødal" wrote:
>On 04/18/2012 04:03 PM, ext Girish Ramakrishnan wrote:
>> Hi,
>>
>> On Wed, Apr 18, 2012 at 3:28 AM, wrote:
>>> Still the QPA headers are sort of a di
On 04/18/2012 04:03 PM, ext Girish Ramakrishnan wrote:
> Hi,
>
> On Wed, Apr 18, 2012 at 3:28 AM, wrote:
>> Still the QPA headers are sort of a different beast from private headers.
>> While I don't want to promise anything on them yet (I think we might want
>> to keep SC and BC for them in patc
28 matches
Mail list logo
