On Tue, Jun 18, 2013 at 11:32 AM, Alan Ezust wrote:
>
> Another type I'd like to see in QML is the QTimer type, with notify
> properties and all.
>
>
Oops, I forgot this is related to Cascades QML, so please ignore this line.
:-)
The QML Timer is great and I wish that was available in Cascades.
_
How to checkout qt5 and etc from github
$ git clone g...@github.com:qtproject/qt5.git
$ cd qt5
$ ./init-repository -f --no-webkit --mirror g...@github.com:qtproject
Cheers,
Qt Mirror Bot
https://github.com/qtproject/
___
Development mailing list
Develop
I like this idea very much and think we should look into it further.
There is a long way we can go with integrating Qt into Apple platforms better
at every level and this would be a great start.
--
Jake Petroules
Chief Technology Officer
Petroules Corporation · www.petroules.com
Email: jake.petr
On Mon, Jun 17, 2013 at 10:13 PM, Alan Alpert <4163654...@gmail.com> wrote:
> It'll be more effective if it's done at the time of loading each file,
> which would actually need some framework integration. Otherwise the
> best solution is bundling everything up into one resource and signing
> that.
On Mon, Jun 17, 2013 at 2:31 PM, Alan Alpert <4163654...@gmail.com> wrote:
> On Mon, Jun 17, 2013 at 1:32 PM, Hausmann Simon
> wrote:
> > I'd like to make URLs a better supported citizen in the world of QML's
> > JavaScript, and it appears that a few options present themselves:
> >
> > (1) We cou
On terça-feira, 18 de junho de 2013 12.44.22, Adam Strzelecki wrote:
> Ad detailed at
> https://bugreports.qt-project.org/browse/QTBUG-31814#comment-206336 I don't
> see any reason that qmake and QtCore could not use paths relative to
> current executable rather than hardcoding absolute paths.
Tha
On Tuesday, June 18, 2013 14:34:17 you wrote:
> On 18.06.13 16:01, "Stephen Kelly" wrote:
> >On Tuesday, June 18, 2013 13:16:42 you wrote:
> >> Hi Stephen,
> >>
> >> I think there should have been an answer on the list to the concern.
> >
> >Yes. There's no point in posing such questions if the a
I totally support Stephen point! you are not alone!
BTW, It's seems I discovered the problem, and say the `lib/Qt*.dll` can be
safety delete.
It will broken CMake build just in recently. but seems nobody care.
I don't know how to search in the list, so pls just ignored what I say.
anyway, it's do
On Tuesday, June 18, 2013 13:16:42 you wrote:
> Hi Stephen,
>
> I think there should have been an answer on the list to the concern.
Yes. There's no point in posing such questions if the answers are ignored.
Do you think it's important to ask for a list of important patches at all, or
should we
In working to solve [1] I created the change [2] which was approved for
merging with a note of something for later fixing. However on trying to
merge it CI showed what turned out to be an issue with the compression test
that was related to Thiago's comment about the usage of #ifndef
QT_NO_COMPRESS
On Tuesday, June 18, 2013 10:51:07 Turunen Tuukka wrote:
> That change was unfortunately merged too late to be included to RC. It will
> be in the RC2 / 5.1.0 final.
Hi there,
That's not a very good answer. Anyone want to try again?
Given that the question was asked, and given that I answered i
Hi,
That change was unfortunately merged too late to be included to RC. It will be
in the RC2 / 5.1.0 final.
Yours,
--
Tuukka
Stephen Kelly kirjoitti 18.6.2013 11:31:
On Friday, June 14, 2013 14:33:02 Stephen Kelly wrote:
> On Friday, June 14, 2013 11:52:37 Heikkinen Jani wrot
Hi All,
We have now released Qt 5.1 release candidate, see
https://blog.qt.digia.com/blog/2013/06/18/qt-5-1-release-candidate-available/
Big thanks for everyone involved!
Let's now continue our effort to get final out during next few weeks.
Br,
Jani
___
On Friday, June 14, 2013 14:33:02 Stephen Kelly wrote:
> On Friday, June 14, 2013 11:52:37 Heikkinen Jani wrote:
> > Hi all!
> >
> > Last night we succeed to create new packages with updated content(based on
> > qt5.git from yesterday) and now we are really close to Qt5.1 RC1.
> > According
> > to
14 matches
Mail list logo
