This is my experience as well, as of now I am doing native or Cordova app
dev on the android platform since for my particular audience the Ministro
workflow is too much.
WHat about the statically linking libs in or talking to Google to include
it there anyways ?
On Fri, Jan 11, 2013 at 4:36 PM,
also, is there a one bundle Qt SDK as used to be for open source
development in the Nokia times? It seems the creator is now a separate
options, not an issue to set it all up but what abut complete noobs coming
to the SDK?
-Sivan
On Wed, Dec 19, 2012 at 5:56 PM, Thiago Macieira
wrote:
> On quar
Hi All,
As I've request presence for the project in FOSDEM, I'd like to know if
people would be interested in giving talks and showcasing demos
specifically for latest Qt5 features and at the most 1 4.8 cool demo at the
FOSDEM stand, if we're granted one.
Let's keep the discussion on marketin
IIRC, this was supported long ago and is the basis for the extreme
reuse QML enables.
-Sivan
On Thu, Oct 4, 2012 at 12:27 PM, Tomasz Siekierda wrote:
>> What i really miss in QML is the ability to let a component inherit
>> functionality from another component.
>
> This is already a feature: jus
Jeremy,
Take a look here:
- https://gitorious.org/cquick#more
- a brain dump spec I am waiting for some free time (god I
need more of that!) to finish,
http://qt-project.org/groups/qt-contributors-summit-2011/wiki/CrowdQuick
I'd be happy if people would join and help me
>From what I remember from our 2 doc BoFs, the largest "decision" was
that demos and examples should be minimized, as docs have too many
demos as examples, and too many examples. I think we agreed to make
QWidget examples optional as well. Casper, I think this is the "most
significant" conclusion f
What's your windows version? I can see the code (in qt5) makes
distinction between WinCE and the rest.
Seeing this respective code:
}
998
999 //static
1000 QString QFileSystemEngine::rootPath()
1001 {
1002 #if defined(Q_OS_WINCE)
1003 QString ret = QLatin1String("/");
1004 #else
1005 QS
Hi All,
Following the rather interesting discussion that started by Rene[0] ,
I've summarized the bits I believed to be important for others seeking
the same information as he did, and put it on the wiki[1]. I've also
created a new category on the wiki main page, dubbed as 'Documentation
Extra'.
Hi Rene,
On Wed, May 23, 2012 at 1:25 PM, Rene Jensen wrote:
>
> DOCUMENTATION...
>
> The truth is that initially in ten out of ten cases I resorted to
> guessing about the type and ownership of a value when I cross a
> boundary. Since I have thoroughly cross examined the docs, it must
> mean tha
On Tue, May 22, 2012 at 2:07 PM, Thiago Macieira
wrote:
> There is no need for nominating for contribution. Anyone can contribute. Being
> a maintainer of something is what requires dedication.
>
> Unfortunately, for all sysadmin-related jobs, we have legal issues that need
> to be dealt with, so
Hello All,
As I'm keen on contributing to improve out documentation, I took the
liberty to put up on the wiki a session outline for what I hope will
be a productive doc sessions including (if time permits) thoughts of
beyond 5.0 and following hack sessions to get some of the new
decisions started
On Wed, May 16, 2012 at 5:53 AM, Girish Ramakrishnan
wrote:
>
> I would like to preschedule a session to discuss the state of Qt5 on
> various embedded devices. I can drive this session.
>
I could help with write down meeting/session minutes - if you need
someone to do so. The subject of cross to
On Mon, May 14, 2012 at 12:53 PM, a.gra...@gmail.com wrote:
> avoid regressions or incompatibility problems caused by a newer
> version of QtSDK. If we think about Qt and QtCreator just as an SDK to
> write applications I agree with you that developers should have the
> latest tools available, but
On Thu, Apr 12, 2012 at 4:12 PM, wrote:
> 4. The QDoc commands and functionality are not known well enough by
> For issue 4 I would like to point people to
> http://doc-snapshot.qt-project.org/qdoc/ this is the URL of the qdoc
> manual. If everybody follows what is written there and reports bugs
On Sat, May 12, 2012 at 10:13 PM, Girish Ramakrishnan
wrote:
> 1. Qt SDK vs Ubuntu repo install - Currently, Qt SDK is a separate
> here was that this is not entirely solvable since Qt SDK contains much
> more than creator and Qt (it has the sysroots and toolchains required
> for the devices). Is
On Fri, May 4, 2012 at 9:21 PM, wrote:
> Hi,
>
> Example: http://doc-snapshot.qt-project.org/5.0/mainwindows-application.html
>
> Currently we render the list of examples at the top of the page, as visible
> in the example. On that page you do not really get an idea about the example
> before sco
Hi All,
I have a project I've that I wish for someday to become part of Qt.
I understand that such a project starts its life as a Playground
project. Are there any consideration I take care of right now (I've
created a repo I'm going to push to soon on gitorious) to make it
easier later on the
Hey Casper.
On Sat, Apr 28, 2012 at 2:51 PM, wrote:
> It seems like the Documentation component assignee is set to "Qt
> Documentation Team" and I think this is not valid anymore, unless we get a
> public mailing list where all of the bug emails for this user are sent to.
> The default assignee
Hi Tuuka,
On Thu, Apr 12, 2012 at 9:21 AM, Turunen Tuukka
wrote:
> I think using the tracks is a good idea. Some 'keynotes' in the beginning
> for everyone, and after that the tracks. These help in finding the most
> interesting topics.
>
In favor of discussing this separately I started a new th
On Thu, Apr 12, 2012 at 4:35 PM, André Somers wrote:
> I think that loosing all the cross links and all the inherited-by links
> that span modules is unaceptable. For instance, you would no longer be
> able to see relations between some major classes, like QObject ->
> QWidget. You'd only be able
On Thu, Apr 12, 2012 at 4:12 PM, wrote:
> TL;DR: We need to change the way Qt does documentation. A lot of things
> will change and we need help from everybody.
>
This is granted, but as the whole Qt5 process looks, this will be for the good.
> As mentioned by Lars: We should make sure the quali
Hi Tuuka!
On Thu, Apr 12, 2012 at 9:21 AM, Turunen Tuukka
wrote:
> I think using the tracks is a good idea. Some 'keynotes' in the beginning
> for everyone, and after that the tracks. These help in finding the most
> interesting topics.
So we need to see what tracks we could define for the summi
On Fri, Apr 13, 2012 at 8:57 PM, Quim Gil wrote:
> Still "a third party" from a Qt Project point of view but I guess one
> that you are more used to trust. Sorry, it was the fastest and simplest
> way to save us from handling emails manually.
Who is the third party in that case?
>
> PS: But we n
Hi All,
Doing more organization thought and work, we'd like to get the
discussion going about how to best organize the the schedule for the
summit.
My personal experience from last year was such that it was a bit hard
to decide which sessions to attend, some I missed due to room locating
(perha
On Fri, Apr 6, 2012 at 4:01 PM, wrote:
> I think it would be great if we could extend the invitations to WebKit
> committers that are contributors to the Qt port.
>
> Quim, what do you think?
>
I second that as well, I also want to make sure how we can include
folks out of the Necessitas projec
We now have a human friendly URL for the registration page (Thanks
Thiago the reminder):
http://tinyurl.ms/50kb
-Sivan
On Tue, Apr 3, 2012 at 10:31 PM, Sivan Greenberg wrote:
> reserve your place.
>
> [0]:
> https://docs.google.com/spreadsheet/view
On Tue, Apr 3, 2012 at 9:31 PM, Sivan Greenberg wrote:
> this event is for you. Plus, you don't want to evening treat in the
> form of super cool Qt social activity in the evening.
Ah...I typed too fast.. Of course I meant you *do not* want to miss
the evening treat! ;)
Sorry fo
Hello Everybody!
Now that we have a successful Qt5 Alpha release, we have a
complementary event to celebrate it, the wonderful Qt Contributors'
Summit. If you want to influence where Qt is headed, and engage in
fruit full, yet fun sessions and discussions about the future of Qt,
this event is fo
On Tue, Apr 3, 2012 at 7:14 PM, Girish Ramakrishnan
wrote:
> Window desktop components still don't exist but Widgets work just fine
> with Qt5 just like in Qt4.
They are in the works right?
>
> Symbian is no longer supported in Qt5.
I'd be surprised greatly if the Next Billion transition platfo
I join Artur here, and Qt has *always been* revolutionary. So I don't
expect anything short of qt5.
-Sivan
On Mon, Apr 2, 2012 at 2:34 PM, Artur Souza (MoRpHeUz)
wrote:
> 2012/4/1 :
>>
>> To every-concerned-one-of-you, I hope you do realize that we share all
>> of those same concerns. We do! :-
On Sun, Apr 1, 2012 at 6:56 PM, Stephen Kelly wrote:
>
> I can help out, but only until the end of today I'm afraid.
>
Right, this is my clue that this is indeed an April 1st day joke.
-Sivan
___
Development mailing list
Development@qt-project.org
http:
Hey Joao,
On Sun, Apr 1, 2012 at 6:04 PM, wrote:
> The first one introduces a Q namespace, which replaces the Q prefix in
> Qt5. The second patch drops the prefix in class names. This brings the
> C++ API more in line with the QML/JavaScript one and will hopefully help
> move all remaining C++ d
Trying to find some info about it myself (fascinated by decoupling and
abstract stuff) I found this sparse "resources":
http://qt-project.org/wiki/Lighthouse_Architecture
More information would be appreciated yes.
-Sivan
On Wed, Mar 21, 2012 at 9:39 PM, Krenar Qehaja wrote:
> [Forgot to inclu
Hi Raju!
On Sun, Jan 22, 2012 at 2:47 PM, Raju Jaiswal wrote:
> GUI is ready using Qt. I have thought of using WAMP server .But I
> don't know how to proceed further. I am quite new to app development.
> Please help..
My normal approach is the use Django[0] + tastypie[1] + mongodb[2] to
create
On Sun, Dec 11, 2011 at 6:40 PM, Robin Burchell wrote:
> You're missing the bit where the binary format is not the only
> representation. JSON can be parsed into it, it's stored like this in
> memory, and it can be serialised back to it (obviously), but it can
> also be serialised back to JSON. Or
Hi Lars!
On Sat, Dec 10, 2011 at 11:32 PM, wrote:
> there were quite a few discussions and requests over the last months to
> add Json support as part of QtCore, and maybe integrating one of the
> existing parsers.
There were also discussions and even a couple of bug report about
adding "native
36 matches
Mail list logo
