Press.
Ansel Sermersheim
CopperSpice Cofounder
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On 7/26/15 3:01 PM, Kevin Kofler wrote:
> Ansel Sermersheim wrote:
>> We do in fact have a CLA in place. However, our CLA has one single
>> purpose. In the event that Qt is re-licensed under a BSD style license
>> (whether due to the KDE Free Qt Foundation or some other r
On 7/21/15 3:15 PM, Marc Mutz wrote:
> On Tuesday 21 July 2015 22:26:17 Ansel Sermersheim wrote:
>> As to your question about relicensing, can you please elaborate on what
>> this is referring to? As long as Qt is covered by the current license,
>> we can not relicense Cop
On 7/21/15 6:23 PM, Thiago Macieira wrote:
> On Tuesday 21 July 2015 18:10:27 Ansel Sermersheim wrote:
>> The most common use case of this is creating a QMap that is
>> sorted case insensitively. The STL allows this for std::map, and coming
>> to Qt from a background of stan
e of the kind of things that
are being done. For a more comprehensive list check out the overview
documentation on our website:
http://www.copperspice.com/docs/cs_overview/index.html
Ansel Sermersheim
___
Development mailing list
Development@qt-
On 7/21/15 11:37 AM, Thiago Macieira wrote:
> On Tuesday 21 July 2015 10:06:52 Ansel Sermersheim wrote:
>> We would like to announce our release of CopperSpice 1.1.0. We have
>> added and changed several things including a modification to to QMap to
>> user defined compari
elaborate on what
this is referring to? As long as Qt is covered by the current license,
we can not relicense CopperSpice since we are bound by the terms of the
licenses under which we forked the code.
Ansel Sermersheim
On 7/21/15 12:36 PM, Marc Mutz wrote:
> On Tuesday 21 July 2015 19:53:14 Gun
community including
myself.
We have talked with other developers and read discussions about this for
over a decade. Many members of the larger open source community,
including myself, are not comfortable with this clause.
Ansel Sermersheim
On 7/21/15 10:53 AM, Gunnar Roth wrote:
Hi Ansel.
Am
:
> On Monday, June 29, 2015 10:51:25 PM Ansel Sermersheim wrote:
>>> There is always CopperSpice the Qt fork which uses C++11. They've
>>> got rid of moc and plan to replace Qt containers with std ones.
>>> Afterwards maybe they will add support for namesp
ike smart pointers. Ok, you can use them, but you
cannot use them to interact with Qt. To a modern C++ programmer this
comes across as a significant limitation.
Ansel Sermersheim
CopperSpice Co-Founder
www.copperspice.com
___
Development mailing li
en, it sounds like this is not the
direction Qt is going for many years if at all.
Ansel Sermersheim
CopperSpice Co-Founder
www.copperspice.com
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On 6/30/15 1:01 PM, Thiago Macieira wrote:
> On Tuesday 30 June 2015 09:37:59 Ansel Sermersheim wrote:
>> Our goal with CopperSpice is to use modern C++ internally to leverage
>> everything we can from the language. We want developers of CopperSpice
>> applications to hav
On 6/29/15 11:37 PM, Alejandro Exojo wrote:
> El Tuesday 30 June 2015, Ansel Sermersheim escribió:
>> Our September release of CopperSpice will include changes to the
>> contain library, reimplementation of atomic types, our new changes
>> to the MetaObject System r
On 6/29/15 10:59 PM, Thiago Macieira wrote:
> On Monday 29 June 2015 22:51:25 Ansel Sermersheim wrote:
>> I would like to clarify, we did not use anything from the Woboq
>> blog posting as others have speculated. We had moc removed from
>> CopperSpice a year earlier than the
o.
http://cppcon.org/2015promo/
Our thanks go out to Trolltech, Nokia, and Digia for all the work they
have done.
Ansel Sermersheim
CopperSpice Co-Founder
www.copperspice.com
___
Development mailing list
Development@qt-project.org
http://lists.qt-pr
15 matches
Mail list logo
