On Dec 12, 2012, at 4:53 PM, Sze Howe Koh wrote:
> On 12 December 2012 19:22, Martin Smith wrote:
>> If you have trouble creating a link to something (usually title or subtitle)
>> because the title or subtitle you are trying to link to exists in more than
>> one document and your link goes to
On Wed, Dec 12, 2012 at 5:06 PM, Chris Adams wrote:
> Hi,
> ...
>> Since this is currently necessary, it does mean that anyone who wants
>> to see enums properly supported should help out with the v4vm work
>> (currently the best way to fix QTBUG-24799).
>
>
> The v4vm implementation is an orthogo
Hi,
> This entire thread should be revisited after QTBUG-24799 is fixed.
> >
>
> I disagree here, because
> A) How much we like enums affects the effective priority of
> QTBUG-24799 (it's the main usecase that it blocks)
>
True. Although it also affects instanceOf and Qt.createComponent, at the
On Wed, Dec 12, 2012 at 4:04 PM, Chris Adams wrote:
> Hi,
>
>
>> maybe there's a case for adding a small QQmlApplicationEngine in QtQml
>> which adds the application runtime aspects?
>
>
> It's early and I haven't had my second coffee yet, so maybe I'm
> misunderstanding something, but are these a
On Wed, Dec 12, 2012 at 3:53 PM, Chris Adams wrote:
> Hi,
>
>...
>>
>> (4) Lack of "Enums" in QML is (another) example of how QML might be
>> considered a "second-class-citizen" (mentioned by Chris, another example
>> being composite types in QML are not backed by a QQmlType and thus are not
>> a
On Wednesday December 12 2012, Mohamed Fawzi wrote:
> text/plain; charset=utf-8
> text/vnd.qt.qml-base : a file using the qml syntax in some context
> text/vnd.qt.qml : the current .qml files
> text/vnd.qt.qbs : a qbs file
> text/vnd.qt.qml-meta-info : qmltypes meta info
> te
Hi,
maybe there's a case for adding a small QQmlApplicationEngine in QtQml
> which adds the application runtime aspects?
>
It's early and I haven't had my second coffee yet, so maybe I'm
misunderstanding something, but are these application runtime aspects
completely non-gui, non-QtQuick related?
Hi,
On Wed, Dec 12, 2012 at 10:51 PM, Charley Bay wrote:
> Unto all so did sayeth Alan:
>
>> > What should enumeration declarations in QML look like?
>>
>
> Did respondeth Erik:
>
>> And, also important: how much slower is it allowed to be than the current
>> implementation?
>>
>> I remembered t
On 13/12/12 07:12, Alan Alpert wrote:
> Hmm... so you're suggesting that we tie the imports for a single
> application into a single file (manageable by the build system)? That
> might work...
>
> So all the application source files would look like this:
>
> import QtQml from MyImports
> import QtQ
On 12/12/12 23:01, Alan Alpert wrote:
> Major version means high-level incompatibilty, so if you import QtQml
> 2.0 now don't expect it to just work with QtQml 3.0. Minor version
> means features, which actually means some low-level incompatibilty
> because it's a different language to C++. So Q
On Dec 12, 2012, at 5:39 PM, Oswald Buddenhagen
wrote:
> On Wed, Dec 12, 2012 at 07:59:07AM -0800, Thiago Macieira wrote:
>> On quarta-feira, 12 de dezembro de 2012 14.03.52, Oswald Buddenhagen wrote:
>>> On Mon, Dec 03, 2012 at 04:29:24PM +, Knoll Lars wrote:
master is closed for new
On Wed, Dec 12, 2012 at 2:59 AM, Mohamed Fawzi wrote:
> ...
> I propose the following hierarchy:
>
> text/plain; charset=utf-8
>text/vnd.qt.qml-base : a file using the qml syntax in some context
> text/vnd.qt.qml : the current .qml files
> text/vnd.qt.qbs : a qbs file
> text/vnd
On Wed, Dec 12, 2012 at 10:57 AM, André Pönitz
wrote:
> On Wed, Dec 12, 2012 at 10:33:06AM +1000, Lincoln Ramsay wrote:
>> On 12/12/12 07:28, André Pönitz wrote:
>> > What about something like
>> >
>> > import QtQml from Qt 5.0
>> > import QtQuick from Qt 5.0
>>
>> +1
>
> Thanks ;-)
>
>> All t
On Wed, Dec 12, 2012 at 11:18 AM, Giuseppe D'Angelo wrote:
> On 12 December 2012 18:57, André Pönitz
> wrote:
>>
>>
>> I actually think it's still to specfic. Upgrading from Qt 5.0 to 5.1
>> would need touching all source files. So
>>
>>import QtQml from TheQtIUse
>>import QtQuick from Th
On Wed, Dec 12, 2012 at 7:41 AM, Attila Csipa wrote:
> On 12/12/12 12:22, Sorvig Morten wrote:
>> On Dec 11, 2012, at 4:25 AM, Alan Alpert <4163654...@gmail.com> wrote:
>>> import Qt 5.0
>>>
>>> Which imports all QML modules in the Qt Essentials released with 5.0.0
>
> If the idea is to import the
On Wed, Dec 12, 2012 at 2:13 AM, Mark wrote:
> On Wed, Dec 12, 2012 at 10:03 AM, Simon Hausmann
> wrote:
>> On Tuesday, December 11, 2012 04:40:50 PM Bache-Wiig Jens wrote:
>>> >>...
>> I think a dedicated syntax has two distinct advantages over a
>> Qt.storedProperty alike approach:
>>
>> (1
On Tue, Dec 11, 2012 at 3:25 PM, Thiago Macieira
wrote:
> On terça-feira, 11 de dezembro de 2012 14.51.31, Alan Alpert wrote:
>> The reason why most QML APIs are developed separate from C++
>> considerations is that there's already a C++ API for that
>> functionality. For new functionality QML and
On Wed, Dec 12, 2012 at 12:44 AM, André Somers wrote:
> Op 11-12-2012 21:59, Alan Alpert schreef:
>> On Tue, Dec 11, 2012 at 10:49 AM, Shawn Rutledge
>> wrote:
>>> On Tue, Dec 11, 2012 at 09:48:22AM -0800, Alan Alpert wrote:
Why can't this be QML-only? For the set of controls exposed in
On 12 December 2012 18:57, André Pönitz
wrote:
>
>
> I actually think it's still to specfic. Upgrading from Qt 5.0 to 5.1
> would need touching all source files. So
>
>import QtQml from TheQtIUse
>import QtQuick from TheQtIUse
>
> and some one-liner somewhere that relates "TheQtIUse" with
Op 12-12-2012 18:35, Stephen Kelly schreef:
> On Wednesday, December 12, 2012 09:44:10 André Somers wrote:
>> Op 11-12-2012 21:59, Alan Alpert schreef:
>>> On Tue, Dec 11, 2012 at 10:49 AM, Shawn Rutledge
>>>
>>> wrote:
On Tue, Dec 11, 2012 at 09:48:22AM -0800, Alan Alpert wrote:
> Why ca
On Wed, Dec 12, 2012 at 10:33:06AM +1000, Lincoln Ramsay wrote:
> On 12/12/12 07:28, André Pönitz wrote:
> > What about something like
> >
> > import QtQml from Qt 5.0
> > import QtQuick from Qt 5.0
>
> +1
Thanks ;-)
> All the benefits of "a group of QML modules attached to a single Qt
> r
On Tue, Dec 11, 2012 at 11:33 PM, Sorvig Morten wrote:
>
> On Dec 11, 2012, at 8:30 PM, Alan Alpert <4163654...@gmail.com> wrote:
>
>> On Tue, Dec 11, 2012 at 3:33 AM, Sorvig Morten
>> wrote:
>>> Please bundle the QML runtime in a class that the app author can
>>> instantiate.
>>>
>>> This give
On Mon, Dec 10, 2012 at 7:23 PM, Alan Alpert <4163654...@gmail.com> wrote:
> For finer-grained control over QML it would make sense to have an API
> allowing import restrictions. Two usecases come to mind, platform
> security contexts and scriptable applications. Platform security
> contexts is abo
On Tue, Dec 11, 2012 at 5:27 PM, Jan Kundrát wrote:
> On Tuesday, 11 December 2012 04:23:51 CEST, Alan Alpert wrote:
>> For finer-grained control over QML it would make sense to have an API
>> allowing import restrictions. Two usecases come to mind, platform
>> security contexts and scriptable app
On quarta-feira, 12 de dezembro de 2012 18.31.47, Trismer Technologies wrote:
> Hello,
>
>Does anyone has information about roadmap of Qt5 for iOS ? Digia promises
> this port in next year but I'd like to know how the current blockers will
> be removed: the most important one - V8 javascript f
Hello,
While analyzing the source code in qfontconfigdatabase.cpp (qt4), I stumbled
upon the following piece of code (beginning on line 433):
struct FcDefaultFont {
const char *qtname;
const char *rawname;
bool fixed;
};
const FcDefaultFont defaults[] = {
On Wednesday, December 12, 2012 01:15:14 André Pönitz wrote:
> On Tue, Dec 11, 2012 at 03:20:35PM -0800, Alan Alpert wrote:
> > On Tue, Dec 11, 2012 at 2:57 PM, André Pönitz
> >
> > wrote:
> > > On Tue, Dec 11, 2012 at 09:48:22AM -0800, Alan Alpert wrote:
> > > ...
> > >
> > >> But there are other
On Tuesday, December 11, 2012 23:57:48 you wrote:
> On Tue, Dec 11, 2012 at 09:48:22AM -0800, Alan Alpert wrote:
> > > We also need to find out whether we can come up with something which
> > > QtWidgets users can migrate to (the QWidget* in the QAction API is
> > > quite niche, and not necessarily
On Wednesday, December 12, 2012 09:44:10 André Somers wrote:
> Op 11-12-2012 21:59, Alan Alpert schreef:
> > On Tue, Dec 11, 2012 at 10:49 AM, Shawn Rutledge
> >
> > wrote:
> >> On Tue, Dec 11, 2012 at 09:48:22AM -0800, Alan Alpert wrote:
> >>> Why can't this be QML-only? For the set of controls e
On Tuesday, December 11, 2012 09:48:22 you wrote:
> On Tue, Dec 11, 2012 at 6:07 AM, Stephen Kelly
wrote:
> > For comparison, you could look at what we did with QML1 based
> > kdepim-mobile.
> Great, thanks! It's always good to see how this can is handled in real
> applications. I just hope that
Hello,
Does anyone has information about roadmap of Qt5 for iOS ? Digia promises
this port in next year but I'd like to know how the current blockers will be
removed: the most important one - V8 javascript for iOS ? Are there any plans
around that ? Eventually are there plans to port only Q
On Tuesday, December 11, 2012 14:51:31 Alan Alpert wrote:
> One thing that I started thinking about though is that we will need in
> this case to have a C++ and QML API that can work with the same
> settings (unlike the existing Local Storage API), so that the C++ and
> QML halves of an application
On 12/12/2012 05:30 PM, Thiago Macieira wrote:
> But that change should have targeted the dev branch. It's new API and a new
> feature.
Indeed! Though I was just interested in sharing the code with people for
early feedback, so I didn't pay much care to the target branch.
I'll move the next iter
On 12/03/2012 04:48 PM, Thiago Macieira wrote:
> (...)
>>>
>>> Would anyone like to second?
>>
>> +1 from me
>> Disclaimer: I'm at KDAB, like he is, too.
>
> +1 from me
> Disclaimer: I'm not at KDAB, but I am Brazilian like Rafael :-)
+1 from me
no disclaimer :)
Peter
>
>
>
> __
On Wed, Dec 12, 2012 at 07:59:07AM -0800, Thiago Macieira wrote:
> On quarta-feira, 12 de dezembro de 2012 14.03.52, Oswald Buddenhagen wrote:
> > On Mon, Dec 03, 2012 at 04:29:24PM +, Knoll Lars wrote:
> > > master is closed for new pushes and will go away in a couple of weeks by
> > > the lat
On quarta-feira, 12 de dezembro de 2012 17.24.17, Alberto Mardegan wrote:
> I got a WIP branch up for preliminary review:
>
> https://codereview.qt-project.org/#change,42633
>
> Any hints (especially on how to write automated tests for the feature)
> are very welcome :-)
>
> I tested it with a s
On Wednesday, December 12, 2012 17:08:54 Alberto Villa wrote:
> On Wed, Dec 12, 2012 at 2:52 PM, Stephen Kelly
wrote:
> > For anyone packaging Qt 5 and renaming the binaries moc, rcc, uic, etc,
> > please remember to also change the CMake config files using those to the
> > renamed binaries.
>
>
I got a WIP branch up for preliminary review:
https://codereview.qt-project.org/#change,42633
Any hints (especially on how to write automated tests for the feature)
are very welcome :-)
I tested it with a simple client and a Gtk socket, and it mostly works
(still some focusing issues...).
Cia
On quarta-feira, 12 de dezembro de 2012 14.52.16, Stephen Kelly wrote:
> For anyone packaging Qt 5 and renaming the binaries moc, rcc, uic, etc,
> please remember to also change the CMake config files using those to the
> renamed binaries.
For anyone packaging Qt 5: DO NOT RENAME the binaries.
W
On quarta-feira, 12 de dezembro de 2012 14.03.52, Oswald Buddenhagen wrote:
> On Mon, Dec 03, 2012 at 04:29:24PM +, Knoll Lars wrote:
> > master is closed for new pushes and will go away in a couple of weeks by
> > the latest.
> this has happened now - the master branches are all deleted.
>
>
On 12 December 2012 19:22, Martin Smith wrote:
> If you have trouble creating a link to something (usually title or subtitle)
> because the title or subtitle you are trying to link to exists in more than
> one document and your link goes to the wrong one, consider using the \target
> command. I
On 12/12/12 12:22, Sorvig Morten wrote:
> On Dec 11, 2012, at 4:25 AM, Alan Alpert <4163654...@gmail.com> wrote:
>> import Qt 5.0
>>
>> Which imports all QML modules in the Qt Essentials released with 5.0.0
If the idea is to import the essentials, then call it that: "import
QtEssentials (from Qt)
> I didn't know who to assign it to or even that I should assign it to
someone.
I am sure I have not assigned anyone explicitly, and it worked out of the
box. Perhaps I was just lucky.
http://qt-project.org/wiki/Creating-a-new-module-or-tool-for-Qt#6a17de784cf6db9124e9844959ec8ace
In my opinion o
> From: Ahumada Sergio
> To: development
> Sent: Wednesday, December 12, 2012 2:19 AM
> Subject: Re: [Development] Qt Playground - Updating Daemon/Service Support
>
>>
>> As I know others have expressed interest in helping out, here's the
>> bug report in case you want to join/watch:
Hi there,
For anyone packaging Qt 5 and renaming the binaries moc, rcc, uic, etc, please
remember to also change the CMake config files using those to the renamed
binaries.
The files to change are:
In qtbase.git:
* src/widgets/Qt5WidgetsConfigExtras.cmake.in
* src/dbus/Qt5DBusConfigExtras.c
On Mon, Dec 03, 2012 at 04:29:24PM +, Knoll Lars wrote:
> master is closed for new pushes and will go away in a couple of weeks by the
> latest.
>
this has happened now - the master branches are all deleted.
due to the mess found in the master branches, i simply deleted them
without merging
Unto all so did sayeth Alan:
> > What should enumeration declarations in QML look like?
>
Did respondeth Erik:
> And, also important: how much slower is it allowed to be than the current
> implementation?
>
> I remembered that there was talk about enums in QML before, so I dug
> around a bit, an
On Dec 12, 2012, at 12:22 PM, Martin Smith wrote:
> If you have trouble creating a link to something (usually title or subtitle)
> because the title or subtitle you are trying to link to exists in more than
> one document and your link goes to the wrong one, consider using the \target
> comman
Oops! The link to the target example should be this:
See the section called \l {a_unique_string} {Qt Script} for more details.
martin
On Dec 12, 2012, at 12:22 PM, Martin Smith wrote:
> If you have trouble creating a link to something (usually title or subtitle)
> because the title or subtitle
Hi,
QtWebKit requires SQLite for various web related storage mechanism (including
cookies). That dependency is quite old actually, but we've done some changes
now that clean up the way that dependency is satisfied. Ideally should affect
only very few people, but it is quite likely to include fo
If you have trouble creating a link to something (usually title or subtitle)
because the title or subtitle you are trying to link to exists in more than one
document and your link goes to the wrong one, consider using the \target
command. It didn't work across modules until today. The relevant q
I think it could be useful to do a small recap on mime types, as that is what I
am interested in, not extensions (ignore if it is obvious to you):
a mime type identifies a type of file, mime types are hierarchical, i.e. a mime
type can be a subclass of another.
For example "text/plain; charset=ut
On Dec 11, 2012, at 4:25 AM, Alan Alpert <4163654...@gmail.com> wrote:
>
> import Qt 5.0
>
> Which imports all QML modules in the Qt Essentials released with 5.0.0
> (except QtQuick 1). It would be the equivalent of
>
> import QtQml 2.0
> import QtQuick 2.0
> import QtQuick.Window 2.0
> import
On Wed, Dec 12, 2012 at 10:03 AM, Simon Hausmann
wrote:
> On Tuesday, December 11, 2012 04:40:50 PM Bache-Wiig Jens wrote:
>> >> I would also consider an even simpler API. How about we introduce a new
>> >> keyword for persistent properties and make it part of the language.
>> >>
>> >> Rectangle {
On Dec 11, 2012, at 4:47, Alan Alpert <4163654...@gmail.com> wrote:
> People keep asking for enumerations in QML. See QTBUG-15483 and
> QTBUG-14861, both assigned to old Nokia identities (so don't trust
> that 'in progress' ;) ). Now I don't know when these issues will be
> resolved, but there's a
On Tuesday, December 11, 2012 04:40:50 PM Bache-Wiig Jens wrote:
> >> I would also consider an even simpler API. How about we introduce a new
> >> keyword for persistent properties and make it part of the language.
> >>
> >> Rectangle {
> >>
> >> id: root
> >> persistent property width: 4
Op 11-12-2012 21:59, Alan Alpert schreef:
> On Tue, Dec 11, 2012 at 10:49 AM, Shawn Rutledge
> wrote:
>> On Tue, Dec 11, 2012 at 09:48:22AM -0800, Alan Alpert wrote:
>>> Why can't this be QML-only? For the set of controls exposed in
>>> C++-only we have a C++-only Action API. When we add a set of
On 12/12/2012 01:16 AM, Thiago Macieira wrote:
> On terça-feira, 11 de dezembro de 2012 15.55.52, Alan Alpert wrote:
>> Would you care to sketch out what your PersistentSettings element
>> would look like in practice?
>
> In a non QML approximant syntax:
>
> Rectangle {
> PersistentSettings {
58 matches
Mail list logo
