The Lounge

There was just a post about this on the Development mailing list. Here: http://lists.qt-project.org/pipermail/development/2016-January/024380.html So it is coming to the repos, and officially part of 5.7 As for compiling, I don't know either.

Hi @3dFoin, and welcome to the Qt Dev Net! Could you please provide some tips on how we can use your models in Qt-based projects?

Hi @martin_ky I'll have to ask for our admins to dig up a database dump from qt-project.org to get those pages. It looks like it's the last quarterlies. We don't have plans on anything like Qt Quarterly at the moment. The Qt Blog (blog.qt.io) has taken over that need.

Yes, it's a bit heavy. http://wiki.qt.io/Setting_up_Gerrit is a pretty good guide, also http://wiki.qt.io/Gerrit_Introduction is pretty readable. As the planet repo is not in the official Qt core repos, it is a fair bit easier to get into. But everything still needs to go through gerrit, so the accounts are needed.

Thanks :)

@Charby that would also be fun. The biggest technical problem I see is that the location field in the account is just plain text, so no way of knowing what is in it. A more defined field would be needed. I need some more hours in the day to investigate how much effort it would be.

Hi @Charby To my knowledge France has a big number of people using Qt. They probably are just spread around. And I guess people doing software development do read and speak english pretty well (including the french people I have met). The main reason for missing french in the international section is to my knowledge the Developpez site that @SGaist referred to. (the origin is a bit too far in history for me to be sure). Some other languages that have big local communities are also missing as they have local sites. The international section is there exactly to make sure people find what they are looking for. I don't follow them day to day, but I have the feeling that some members who are more fluent in english help out others there in finding the right places too. I think we could open a french section if you want one. I don't see a problem with that. (assuming no one else sees a problem). You have a meetup, would you like help or support with it? Or tweet about it if you need the visibility. Also I would be interested in hearing your experiences from the meetup. Ping me on the chat and let me know if I can help.

Hi and welcome to devnet, I don't have the shortcut at hand but take a look at Window menu, it should be there.

Did You add library import/export macros? Create a file, i.e. mylibimport.h #include <QtCore/QtGlobal> #if defined(MY_LIBRARY) # define MYLIBRARY_EXPORT Q_DECL_EXPORT #else # define MYLIBRARY_EXPORT Q_DECL_IMPORT #endif add definition to pro DEFINES += MY_LIBRARY Then add MYLIBRARY_EXPORT before every class or function visible outside: i.e: #include <mylibimport.h> class MYLIBRARY_EXPORT someClass { //.... }; MYLIBRARY_EXPORT int someFunction() { }

Hi and welcome to devnet, There's no project builder app (unless you are referring to an IDE and in this case it's call Qt Creator) To use the qmake provided by macports you should look into /opt/local/ However, the most straight forward way to use Qt would be to get it using the online installer. That will also provide you with the Qt Creator IDE which will be more friendly to use than the command line. You can use MacPort to install tesseract though. Hope it helps

Something's not clear: are you using your distribution's Qt or building Qt yourself ?

Thanks very much for the information and links; the point you raised is very important/interesting to me in that Qt is already a "fast moving target" and for CopperSpice to get close it will need continuous work and effort it's difficult to see it keeping up. Also the growth of Qt has been amazing - I started using Qt about 5 years ago and it felt relativity unknown (I saw very few, or no, jobs requiring Qt), but now it seems to be everywhere. Even in forums like stack overflow the "qt" tag is about 10% as popular as "c++" tag (which is by far the most popular), so again... hard to see CopperSpice getting the same exposure, unless it offers something better then Qt... I am not sure that the removal of Moc is enough for me to want to move away from the Qt community/feature-set anytime soon.

In fact, it seems you have a widget that should show that progress. You should then create as many of these widgets as needed.

My point is that you have to follow and abide by the LGPL v3 license terms and rules if you want to sell closed source software without a commercial license.

Hi @Kelevra You could contact sales at The Qt Company and explain your situation and ask for them to extend the trial period. To me it sounds like you started your trial period a bit too early. Also what @JohanSolo says, as long as you have nothing released to anyone and you don't use the parts of Qt that are under the commercial license, you technically could use the open source version. However once you do start looking at selling your product (really productising the thing), we here at The Qt Company really would like for you to get the commercial license.

@RobertoDuran QML is the preferred option in Qt for mobile apps (assuming the app isn't really complicated). QML is pretty easy to grasp with some background in JS. @devOp well, as this is the Qt Forum, I need to say that Qt is the best option :) Of course you can do the described project in many ways. What is best really depends on what you want out of the project. Are you looking to learn something new? Do you just have to push it out as fast as possible? Do you need to maintain it (this is honestly the biggest workload)? How complicated is the app, what resources does it use on the mobile? Lot's of questions, so it really depends, but Qt will provide a solution to all the mobile platforms with a farily easy learning curve and a good community that can help out when you run into trouble.

@RobertoDuran Hi, you might not catch Peter Winston here easily, he hasn't been around for a while. However on the licensing, currently our thinking is that students can get the open source package for free and start learning and coding. We are thinking of some form of university/school licensing, but that will take a while to get off the ground. We are also looking at low cost options to private/small developers. The last time we had that option it really did not sell well, so it was pulled back for now. We know there is demand for a low cost option, but we need to figure out how to provide that option so that it would get sensible sales numbers. In general we really like it when people contribute back to Qt, be it patches or license payments. Naturally we want to make it easier for people to contribute, so different licensing options are something we continuously look for.