That’s the point. Thiago, assure me, QtDom is NOT going anywhere.. However, its depreciated and not supported. While I understand your concern, and I have it as well.. Depricated in Qt world, is not as drastic as other frameworks... Sometimes...
Which is WHY they need another status, and Thiago agreed. However, that doesn’t mean it exists yet. For QDom, the QXmlStream classes are the replacement... Scott -----Original Message----- From: interest-bounces+scott.bloom=onshorecs....@qt-project.org [mailto:interest-bounces+scott.bloom=onshorecs....@qt-project.org] On Behalf Of Martin Holmes Sent: Monday, January 09, 2012 2:22 PM To: interest@qt-project.org Subject: Re: [Interest] QtSVG deprecated I'm glad to hear this, because I also use QtDom, and can't imagine processing XML documents without it. But the status of Deprecated definitely means: "Module or code will be eventually removed (Qt source and binary compatibility guidelines apply)" and binary compatibility can be broken when we move to Qt5, so it does look as though both SVG and DOM could be gone by the end of the year. That's scary, and seems silly to me. What are the "'other' classes that are better used" for rendering SVG toolbutton images, or modelling an XML document? Cheers, Martin On 12-01-09 02:16 PM, Scott Aron Bloom wrote: > This came up at DevDays… > > There needs to be a status of “No maintained because we consider it > complete” > > Meaning, the code is stable, known bugs are fixed, and new > enhancements will not be added as “other” classes are better used. > > However, the code will NOT be removed from a new version. Another > example is the QDom code base. > > Scott > > *From:*interest-bounces+scott.bloom=onshorecs....@qt-project.org > [mailto:interest-bounces+scott.bloom=onshorecs....@qt-project.org] *On > Behalf Of *Jason H > *Sent:* Monday, January 09, 2012 2:14 PM > *To:* Chris Meyer; mhol...@uvic.ca > *Cc:* interest@qt-project.org > *Subject:* Re: [Interest] QtSVG deprecated > > I don't think it's going away, it's just not being maintained. > > It's good for what it does, but many of the desired enhancements would > result in the module blowing up in run-time size. The module exists as > a good trade-off. And this I think is why it is deprecated. If it were > maintained it wouldn't be good for the little stuff anymore. I see > many requested changes wanting to DOM-ify it, which would definitely > result in bloat (QtDOM is also deprecated, btw) > > *From:*Chris Meyer <cmeyer1969...@gmail.com > <mailto:cmeyer1969...@gmail.com>> > *To:* mhol...@uvic.ca <mailto:mhol...@uvic.ca> > *Cc:* "interest@qt-project.org <mailto:interest@qt-project.org>" > <interest@qt-project.org <mailto:interest@qt-project.org>> > *Sent:* Monday, January 9, 2012 5:01 PM > *Subject:* Re: [Interest] QtSVG deprecated > > Recently I've had my apps rejected on the Mac app store for "using a > custom webkit" (QtWebKit). The main use was to render SVG into > QImages. > > Going forward, I'm planning on using the QtSvg module. Currently, it > partially supports SVG Tiny; but I'm hoping to develop any missing > features as needed. > > I am not in a position to volunteer to be maintainer right now, but > I'm interested in contributing code, doing testing, paying money in > the form of feature bounties, and providing guidance where possible. > > Other than the issue of a maintainer, is there any other reason QtSvg > is deprecated? I think it's important to have this functionality > independent of webkit. > > On Mon, Jan 9, 2012 at 1:29 PM, Martin Holmes <mhol...@uvic.ca > <mailto:mhol...@uvic.ca>> wrote: >> I notice here: >> >> >> <http://labs.qt.nokia.com/2011/05/12/qt-modules-maturity-level-the-li >> st/> >> >> that QtSvg is now deprecated: >> >> [quote] >> QtSvg >> Overall module state: Deprecated >> New maintainer required >> Reasoning: SVG Full (as opposed to SVG Tiny) functionality available >> in QtWebKit, which should be used instead; we welcome research for a >> replacement for the SVG-generating code. >> [/quote] >> >> I use QtSvg for toolbar icons and similar application-level >> graphics, to provide easy scalability. Will QImage still support SVG >> images after QtSvg is gone? I can't imagine how I could use WebKit >> for this functionality. >> >> Cheers, >> Martin >> >> >> -- >> Martin Holmes >> University of Victoria Humanities Computing and Media Centre >> (mhol...@uvic.ca <mailto:mhol...@uvic.ca>) >> _______________________________________________ >> Interest mailing list >> Interest@qt-project.org <mailto:Interest@qt-project.org> >> http://lists.qt-project.org/mailman/listinfo/interest > _______________________________________________ > Interest mailing list > Interest@qt-project.org <mailto:Interest@qt-project.org> > http://lists.qt-project.org/mailman/listinfo/interest > -- Martin Holmes University of Victoria Humanities Computing and Media Centre (mhol...@uvic.ca) _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
