On Friday 06 February 2015 23:48:59 Lisandro Damián Nicanor Pérez Meyer wrote:
> - What's the custom with respect to copyright headers? I've added a simple
> test and normally all of them have a license header on them. Should I add
> one? Should I list myself?
All files need licence headers and
Hi! I've pushed a change to qtdeclarative [0] and I have two doubts:
- Who exactly should I add to review it? git blames Lars in lots of places but
I'm not really sure.
- What's the custom with respect to copyright headers? I've added a simple
test and normally all of them have a license header
On 2015-02-06 09:22, Robert Knight wrote:
>> It is just not practical to ship a second copy of dozens
>> of system libraries, all built as part of QtWebEngine. This is a nightmare
>> in terms of disk space, RAM use, potential for symbol conflicts and
>> delivery of security updates.
>
> These are
Hello,
Unless anyone is willing to help, I would like to propose deprecating and
consequently removing BlackBerry Playbook code from Qt sources.
This would mainly affect the QNX plugin.
Reasons:
- the Playbook NDK is old and its compiler does not keep up with newest
C++11 improvements i
Actually, we have to fix configuration on OS X: Secure Transport is enabled
with -no-openssl (-securetransport is not required) and this can be undesired
side effect
From: development-bounces+timur.pocheptsov=theqtcompany@qt-project.org
on
behalf o
On 02/06/2015 03:17 PM, Richard Moore wrote:
> The secure transport backend for Qt's SSL support was merged earlier
> this week [1] thanks to some great work by Jeremy Laine and Timur
> Pocheptsov. Please could those using Macos X and iOS give it a try and
> see how it works for them?
>
Some pract
> It is just not practical to ship a second copy of dozens
> of system libraries, all built as part of QtWebEngine. This is a nightmare
> in terms of disk space, RAM use, potential for symbol conflicts and
delivery
> of security updates.
These are all valid concerns but ultimately of secondary imp
The secure transport backend for Qt's SSL support was merged earlier this
week [1] thanks to some great work by Jeremy Laine and Timur
Pocheptsov. Please could those using Macos X and iOS give it a try and see
how it works for them?
Cheers
Rich.
1. https://codereview.qt-project.org/#/c/101485/
_
I consider a fully functional web engine component a very important piece of Qt.
Easily embedding a website into a desktop application is extremely useful.
Example applications are scrapers and website analysis tools. But there are a
LOT more applications. Also more common ones.
If the choice is
Hi,
there are some Mac framework fixes backported from Qt5 still waiting
for approval in 4.8:
WIP: Fix framework bundle hierarchy
https://codereview.qt-project.org/#/c/95572/
WIP: Don't make Info.plist for debug framework bundles
https://codereview.qt-project.org/#/c/95573/
Info.plist.lib white
> On 06 Feb 2015, at 09:32, Ziller Eike wrote:
>
>>
>> What simpler alternative do you have in mind?
>
> One possibility that would cover the use case of “show some simple styled
> html without javascript” case (e.g. documentation browsers) would be to give
> QTextBrowser some love again, fi
Sorry for accidentally posting this obviously unfinished mail.
Nils
On Fri, Feb 6, 2015 at 9:59 AM, Nils Jeisecke wrote:
> Hi,
>
> WIP: Fix framework bundle hierarchy
> https://codereview.qt-project.org/#/c/95572/
>
___
Development mailing list
Develop
Hi,
WIP: Fix framework bundle hierarchy
https://codereview.qt-project.org/#/c/95572/
On Fri, Jan 30, 2015 at 2:14 PM, Mark Gaiser wrote:
> On Wed, Jan 14, 2015 at 12:34 PM, Salovaara Akseli
> wrote:
>>
>> Hi,
>>
>> "4.8.7-snapshot-2015-01-12-2-all-changes" file uploaded next to installers
>>
> On Feb 6, 2015, at 09:21, Simon Hausmann
> wrote:
>
> On Friday 6. February 2015 08.42.53 André Somers wrote:
>> Knoll Lars schreef op 5-2-2015 om 16:28:
>>> But we don’t have much of a choice, if we want to deliver an up to date
>>> web engine.
>>
>> Perhaps it is time to ask the question t
El Friday 06 February 2015, André Somers escribió:
> All the while Qt is spending effort to catch up, deprecating compilers
> and platforms because they can't take the latest Javascript engine to
> it, users are hapily using browers like Firefox and Chrome.
>
> Perhaps it is time to conclude tha
On Friday 6. February 2015 08.42.53 André Somers wrote:
> Knoll Lars schreef op 5-2-2015 om 16:28:
> > But we don’t have much of a choice, if we want to deliver an up to date
> > web engine.
>
> Perhaps it is time to ask the question then: do we want to do that? Do
> we really need to?
>
> It see
On 06/02/15 08:42, "André Somers" wrote:
>Knoll Lars schreef op 5-2-2015 om 16:28:
>> But we don’t have much of a choice, if we want to deliver an up to date
>> web engine.
>Perhaps it is time to ask the question then: do we want to do that? Do
>we really need to?
If you ask me as a Chief Mainta
17 matches
Mail list logo
