I'd think one project could handle all the removed features we want to support 
as static libraries
e.g.
qftp
qhttp
qsettings

"qt4support" isn't a terrible name, unless it has too bad connotations.
"qt4removedapis" is clear as well

I'll take care of moving QHttp and QFtp.
In general, the person removing an API from Qt should add it here for future 
removals. (assuming it's feasible and desirable to provide the API standalone)

> -----Original Message-----
> From: lars.kn...@nokia.com [mailto:lars.kn...@nokia.com]
> Sent: Wednesday, January 11, 2012 14:49
> To: Kearns, Shane; thiago.macie...@intel.com; development@qt-project.org
> Cc: sergio.ahum...@nokia.com
> Subject: Re: [Development] Qftp removal
>
> Yes, please. We need a name for it. How about qtnetwork4 ?
>
> I people are ok with the name, can you add the repo, Sergio?
>
> Who'd be willing to import the code and examples into that repo? Shane?
>
> Thanks,
> Lars
>
> On 1/11/12 3:26 PM, "ext shane.kea...@accenture.com"
> <shane.kea...@accenture.com> wrote:
>
> >Can we get an addon module (project in gerrit) for putting standalone
> >implementations of these removed features?
> >I wouldn't expect a huge amount of commits, but the code (and
> associated
> >examples/tests) needs to be moved there and converted from dll exports
> to
> >static libraries.
> >
> >> -----Original Message-----
> >> From: development-bounces+shane.kearns=accenture....@qt-project.org
> >> [mailto:development-bounces+shane.kearns=accenture.com@qt-
> project.org]
> >> On Behalf Of lars.kn...@nokia.com
> >> Sent: Monday, December 26, 2011 10:18
> >> To: thiago.macie...@intel.com; development@qt-project.org
> >> Subject: Re: [Development] Qftp removal
> >>
> >> On 12/24/11 12:24 PM, "ext Thiago Macieira"
> <thiago.macie...@intel.com>
> >> wrote:
> >>
> >> >On Friday, 23 de December de 2011 22.10.19, David Boosalis wrote:
> >> >> I've been using it for a year now, have had no problems on Linux
> and
> >> >> Windows.  I use it to check for application upgrade.  Is there a
> >> >> recommended way to do FTP transfers when QFtp is gone.  Any chance
> of
> >> >>QFtp
> >> >> getting into Qt Commercial ?
> >> >
> >> >Qt Commercial and Qt Open Source are the same. If it's removed from
> >> one,
> >> >it's
> >> >removed from both. We can probably place it in a separate module for
> >> >people
> >> >who still need it.
> >>
> >> Yes, the code is there and while we really need to remove it from
> >> QtNetwork, we should provide a way for people to use it in their
> >> projects.
> >> IMO a static lib containing both QHttp and QFtp could be a solution.
> >>
> >> Cheers,
> >> Lars
> >>
> >> >
> >> >The recommended way is to use QNetworkAccessManager, which does not
> >> have
> >> >API
> >> >for listing directories.
> >> >--
> >> >Thiago Macieira - thiago.macieira (AT) intel.com
> >> >  Software Architect - Intel Open Source Technology Center
> >> >     Intel Sweden AB - Registration Number: 556189-6027
> >> >     Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
> >> >_______________________________________________
> >> >Development mailing list
> >> >Development@qt-project.org
> >> >http://lists.qt-project.org/mailman/listinfo/development
> >>
> >> _______________________________________________
> >> Development mailing list
> >> Development@qt-project.org
> >> http://lists.qt-project.org/mailman/listinfo/development
> >
> >
> >________________________________
> >Subject to local law, communications with Accenture and its affiliates
> >including telephone calls and emails (including content), may be
> >monitored by our systems for the purposes of security and the
> assessment
> >of internal compliance with Accenture policy.
> >_______________________________________________________________________
> ___
> >____________
> >
> >www.accenture.com
>


________________________________
Subject to local law, communications with Accenture and its affiliates 
including telephone calls and emails (including content), may be monitored by 
our systems for the purposes of security and the assessment of internal 
compliance with Accenture policy.
______________________________________________________________________________________

www.accenture.com

_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to