Re: [Qt-creator] Creator stability
Hi,
as user of different IDEs, I don't understand why qtcreator is trying to
provide more advanced features (such as QML support) if more basic features
are not implement/working properly. Important point: how can the team adopts
qtcreator as main development environment if it is not even getting more
stable? Is there any continuous integration environment which provides
nighly builds so we can see also testing results?
Regards, Raul.
On Thu, Mar 25, 2010 at 12:32 AM, Brett Morgan wrote:
> As a user in the field who is bringing a development team from web
> development across to embedded development using QML and Qt/Embedded I
> second Bill's call for qt-creator's git to be put under some form of
> automatic build testing. I need this stable so that my team will have
> confidence to move ahead on our project.
>
> brett
>
> On Thu, Mar 25, 2010 at 10:46 AM, Bill King wrote:
>
>> Bringing this over here as was requested ;)
>>
>>
>> I was just criticized for criticizing the quality of creator ("on the
>> basis of one bug report").
>>
>> I thought we were an open company, part of that is being open to
>> criticism when things are not working.
>>
>> Creator mainline is not working. I have reports both from internal and
>> external users on a regular basis of either creator not building, or
>> creator crashing upon startup. I have pushed the externals to submit
>> bugreports, but, again, my experience here has been less than glowing.
>> Being close to the front lines of the project, sometimes this can be
>> missed.
>>
>> To fix these issues, can we implement some sort of staging/CI system
>> like we have for Qt?
>>
>> For qml usage, bleeding edge is the only choice currently, and the
>> perceived quality of creator from the bleeding edgers is that
>> creator's... not usable at all. That is not the Qt way, and not a
>> perception we should be having. Creator is an excellent product, and one
>> I use daily, and I'd like to go back to bleeding edge, as that's where
>> all the cool new features are :)
>>
>> --
>> Bill King, Software Engineer
>> Qt Development Frameworks, Nokia Pty Ltd
>> Brisbane Office
>>
>> ___
>> Qt-creator mailing list
>> Qt-creator@trolltech.com
>> http://lists.trolltech.com/mailman/listinfo/qt-creator
>>
>
>
>
> --
> Brett Morgan
> http://www.google.com/profiles/brett.morgan
>
> ___
> Qt-creator mailing list
> Qt-creator@trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-creator
>
>
--
Raul Fernandes Herbster
Signove - http://www.signove.com
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Creator stability
As a user in the field who is bringing a development team from web
development across to embedded development using QML and Qt/Embedded I
second Bill's call for qt-creator's git to be put under some form of
automatic build testing. I need this stable so that my team will have
confidence to move ahead on our project.
brett
On Thu, Mar 25, 2010 at 10:46 AM, Bill King wrote:
> Bringing this over here as was requested ;)
>
>
> I was just criticized for criticizing the quality of creator ("on the
> basis of one bug report").
>
> I thought we were an open company, part of that is being open to
> criticism when things are not working.
>
> Creator mainline is not working. I have reports both from internal and
> external users on a regular basis of either creator not building, or
> creator crashing upon startup. I have pushed the externals to submit
> bugreports, but, again, my experience here has been less than glowing.
> Being close to the front lines of the project, sometimes this can be
> missed.
>
> To fix these issues, can we implement some sort of staging/CI system
> like we have for Qt?
>
> For qml usage, bleeding edge is the only choice currently, and the
> perceived quality of creator from the bleeding edgers is that
> creator's... not usable at all. That is not the Qt way, and not a
> perception we should be having. Creator is an excellent product, and one
> I use daily, and I'd like to go back to bleeding edge, as that's where
> all the cool new features are :)
>
> --
> Bill King, Software Engineer
> Qt Development Frameworks, Nokia Pty Ltd
> Brisbane Office
>
> ___
> Qt-creator mailing list
> Qt-creator@trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-creator
>
--
Brett Morgan
http://www.google.com/profiles/brett.morgan
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator
[Qt-creator] Creator stability
Bringing this over here as was requested ;)
I was just criticized for criticizing the quality of creator ("on the
basis of one bug report").
I thought we were an open company, part of that is being open to
criticism when things are not working.
Creator mainline is not working. I have reports both from internal and
external users on a regular basis of either creator not building, or
creator crashing upon startup. I have pushed the externals to submit
bugreports, but, again, my experience here has been less than glowing.
Being close to the front lines of the project, sometimes this can be missed.
To fix these issues, can we implement some sort of staging/CI system
like we have for Qt?
For qml usage, bleeding edge is the only choice currently, and the
perceived quality of creator from the bleeding edgers is that
creator's... not usable at all. That is not the Qt way, and not a
perception we should be having. Creator is an excellent product, and one
I use daily, and I'd like to go back to bleeding edge, as that's where
all the cool new features are :)
--
Bill King, Software Engineer
Qt Development Frameworks, Nokia Pty Ltd
Brisbane Office
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Using flickable in QTCreator Designer
ext Tobias Wahlstrom wrote: > Hi, > > How do I get a stack trace from Quick Designer? I have been using the > precompiled version of Quick Designer in my tests. Can I get a stack trace > out of this version or do I have to build my own? > > I have some more feedback on Quick Designer. I understand that you havn't > had the time to add all fancy features one could ever wish for yet - but I > still would like to mention the things that I think is most important. We > are hoping to be able to use this tool for both our design team and our > UI-developer team letting the both teams take care of different aspects. > To me it seems like that UI-developer team will be pleased with the nice > text-editor with auto-completion and context help and everything. That's the idea :) > The part that needs most improvements if you ask me is the visual editor. > At least our UI-designers do not like to edit "magic code" so much and I > think that this applies to most UI-designers. The things below are > comments as seen out of a UI-designer perspective... > > One thing I really like is that qml-files I create in the project folder > that appear among the Items in the Library using the visual qml-editor. I > would like to be able to arrange my qml-documents in folders. This folder > structure should be used in the Library view to make it easier to handle > many qml-documents. You may use the filter but I still think that > organising the documents by some topic add a value and usability. Not sure how this should look like. The Library is just a list with sections ... We could create different sections for different directories maybe? Or would it help you if subcomponents would be listed in the file system tree under resources too? > I created a qml-document "NumberBox.qml" with a few custom string > properties. Then I choose to use these properties as a text value and a > color value for my NumberBox. I found out how this is done in the visual > editor - very nice! Even though the properties was defined in the document > the text "disappeared" in the editor area. If I run the project it appear > as the should do but not in the editor and not in the state preview. I can reproduce it, thanks for pointing it out! > Then I added a few NumberBox:es using drag-n-drop to my main document and > wanted to change the header text and the color for each box. But I could > not find a way to set the property values for my NumberBoxes using the > visual editor. It would be pretty neat if my custom properties appeared in > the Advanced tab so that I can change the header and color for my > NumberBoxes within the visual editor. Yeah, that's a long standing wish, which we just have to come around to implement :( > And finally it is a bit cumbersome that the library in the visual editor > never update its list of Qml Components if I add a new one. If I edit a > qml component (in my case the NumberBox) and go back to my main view I > would like that all instances of the NumberBox should update - but they > don't. I have to close the document in the text-editor and then open it > again to force the library to reload. I'll look into it :) Thanks for the report! Kai Koehne -- Kai Koehne Software Engineer Nokia, Qt Development Frameworks Nokia gate5 GmbH Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B Umsatzsteueridentifikationsnummer: DE 812 845 193 Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] QList and QStringList, or qDebug() odd Behaviour?
On Wednesday 24 March 2010 01:21:12 ext Victor Sardina wrote: > Guys: > > The program works as expected in Debug mode, but it bombs at the end > when running in Release mode...It quits with the message "The program > has unexpectedly finished.", and the reports from the system says: > > Exception Type: EXC_BAD_ACCESS (SIGSEGV) > Exception Codes: KERN_PROTECTION_FAILURE at 0x7fff5fbffb75 > Crashed Thread: 0 Dispatch queue: com.apple.main-thread Unless you post minimal but compilable code it's really just poking in the dark for anyone trying to help you. > I started to consider going back to "non-dynamic-memory-allocation" mode... The problem is not dynamically allocating something but in this case the question is really why you started to dynamically allocating a QStringList? It does not really make sense in most cases and comes at additional cost. Andre' ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
