Digia has said that the company is willing to support and maintain the module.
It'll be part of the Qt 5 release as well. So it's mainly a problem with the
generated documentation currently.
Cheers,
Lars
On Oct 20, 2012, at 2:31 PM, Sze Howe Koh
mailto:szehowe@gmail.com>> wrote:
(Re-inclu
(Re-including the mailing list)
The snapshot is the more recent version of the page you linked. But in any
case, I found an old thread (
http://www.mail-archive.com/development@qt-project.org/msg01737.html),
which suggests that there's no active maintainer at the moment.
Regards,
Sze-Howe
On Sa
Hi all,
I'm curious about the status of ActiveQt. The QAxContainer and QAxServer
modules seem to still exist in the code base, but aren't listed in
http://doc-snapshot.qt-project.org/5.0/modules.html. Is this simply an
omission in documentation, or are they being removed?
Regards,
Sze-Howe
_
Well, ActiveQt is currently not actively maintained by anybody. If no one
steps up, it'll at some point be left behind. So whoever has an interest
in the module, please step up.
Cheers,
Lars
On 2/2/12 8:37 AM, "ext Friedemann Kleint"
wrote:
>Hi,
>
>the status of the module is that we are trying
Hi,
the status of the module is that we are trying to keep it compiling,
such that it does not totally fall apart.
Apart from the meta object issues, it needs another major refactoring
due to the Lighthouse architecture (it previously used widgets with
native handles).
We (at Nokia) do not have
On Wednesday 1. February 2012 12.48.07 ext Robin Burchell wrote:
> 2012/2/1 Jedrzej Nowacki :
> > Yes, and by updating QMetaObjectBuilder we will update data generated by
> > ActiveQt. ActiveQt would use the newest meta object version (faster &&
> > tested).
>
> As (I think) was raised on Gerrit -
Den 01. feb. 2012 12:48, skrev ext Robin Burchell:
> 2012/2/1 Jedrzej Nowacki:
>> Yes, and by updating QMetaObjectBuilder we will update data generated by
>> ActiveQt. ActiveQt would use the newest meta object version (faster&&
>> tested).
> As (I think) was raised on Gerrit - this requires that so
2012/2/1 Jedrzej Nowacki :
> Yes, and by updating QMetaObjectBuilder we will update data generated by
> ActiveQt. ActiveQt would use the newest meta object version (faster &&
> tested).
As (I think) was raised on Gerrit - this requires that someone take
the time to make it use QMetaObjectBuilder..
On Wednesday 1. February 2012 10.36.35 ext Kent Hansen wrote:
> Den 01. feb. 2012 09:47, skrev ext Olivier Goffart:
> > Facts:
> > 1) QMetaObjectBuilder is private, its API may still change from minor
> > version to minor version
>
> That's fine. It's still better (lower maintenance) than having
>
Den 01. feb. 2012 09:47, skrev ext Olivier Goffart:
> Facts:
> 1) QMetaObjectBuilder is private, its API may still change from minor version
> to minor version
That's fine. It's still better (lower maintenance) than having
home-grown / incompatible generators floating around, IMO.
> 2) Qt mainta
On Wednesday 01 February 2012 07:11:20 Kent Hansen wrote:
> Hi,
> Does anyone care about the ActiveQt module for Qt5?
>
> A problem with this module is that it doesn't have any autotests. I can
> run some on the examples, but I don't really know what they're supposed
> to do, or how to use them to
Hi,
Does anyone care about the ActiveQt module for Qt5?
A problem with this module is that it doesn't have any autotests. I can
run some on the examples, but I don't really know what they're supposed
to do, or how to use them to exercise relevant codepaths.
The main reason I'm asking is because
12 matches
Mail list logo