Hi Jason,


Maybe better to start a new thread for feature-specific feedback, our 
developers probably don't look too much into what's happening in this one... 
but thanks anyway, I'll also forward to the team.



Cheers,

Volker

"Jason H" <[email protected]> wrote in message 
news:[email protected]...
> So I am looking at this QWebElement/Frame and for my uses, it comes up a 
> bit short.
>
> I want an enhanced QDomDocument that can take a XPath query as a parameter 
> to findAll() (Which doesn't exist in QDomDocument) And also, the results 
> of QDomNodeList should be convertible to QList<QDomNode> for iteration. 
> The reason why you use QDomNodeList isn't clear, it makes working with 
> QDomNodes a pain, I convert everything to QList<QDomNode> anyway, and my 
> only use of QDomNodeList is to make it a QList<QDomNode>!
>
> Then QWebElement has QList<QWebElement> findAll()  but no way to make a 
> QWebElement from a list of QWebElements! This would allow you to select a 
> set of elements, then sub-select additional elements. You'd currently have 
> to:
> QList<QWebElement> subselectedWEs;
> foreach (QWebElement we, selectedWEs)
> {
>    subSelectedWEs << we.findAll(subselection);
> }
>
> It would be better to
>
> QList<QWebElement> subselectedWEs = 
> root.findAll(selection).findAll(subselection);
> or
> QList<QWebElement> selected = root.findAll(selection)
> QList<QWebElement> subselectedWEs = selected.findAll(subselection);
>
> Another question is does this assume a GUI is needed for QWeb*? I can't 
> have a GUI. I can't  interact with a desktop! Why does QWebElement 
> recreate so much functionality of QDomDocument, without inheriting from 
> it? Can't we push these features into QDomDocument? (Which doesn't need a 
> GUI!)
>
> I do all of this so I can make a SOAP service. And there are more SOAP 
> services scheduled, so this is a big deal for me. I've currently cobbled 
> together a crude XPath parser.
>
> Ideally what I really need is a QObject which works through QMeta* to 
> provide a local object that allows me to interact with the SOAP service as 
> if it were just another QObject (signals/slots, service discovery). I 
> noticed that QtSoap was recently updated, but it stays stuck at version 
> 1.1. I need 2.0. Minimally, 1.2.
>
> Any information is appreciated!
>
> Thanks!
>
>
>
>
>
>
>
>
> ----- Original Message ----
> From: Jason H <[email protected]>
> To: [email protected]
> Sent: Wednesday, September 30, 2009 11:31:03 AM
> Subject: Re: [Qt4-preview-feedback] Invitation to join the Qt 4.6 Beta 
> Program
>
> FYI: Missing category for type of app. I use Qt for server-side services, 
> i.e. HTTP-SOAP and the like.
>
> While this is not a focus of Qt, the Qt library makes writing these apps 
> easier. Even though there is no real SOAP support (your soap client add-in 
> is not soap 2.0 compliant) Qt could really use a AJAX or JSON 
> client/server. The recent Qt in the Cloud labs article shows that Qt needs 
> to be able Web-2.0 enabled.
>
> I do like that "DOM access API" was added. But I need to know where to 
> find those docs! (Specifically what is added for 4.6)
>
> Thanks!
>
>
>
>
> ----- Original Message ----
> From: Volker Hilsheimer <[email protected]>
> To: [email protected]
> Sent: Wednesday, September 30, 2009 10:47:07 AM
> Subject: [Qt4-preview-feedback] Invitation to join the Qt 4.6 Beta Program
>
>
> Hi!
>
>
> We are preparing the release of the Qt 4.6 Beta, and during the Beta phase
> of Qt 4.6 we would like to ask the community of Qt users for feedback
> regarding the stability, performance and overall quality of our designs,
> APIs and implementations.
>
> In addition to asking for feedback through the regular channels we would
> like to make sure that as many Qt users as possible have performed a few
> specific tasks during the Beta phase to help us understand the most
> important issues that we need to address before the launch of Qt 4.6 later
> this year. We would like to invite you to sign up to the Qt 4.6 Beta
> Program by completing this very short sign-up form - it should only take a
> few minutes:
>
>  http://survey.confirmit.com/wix1/p995540662.aspx
>
> If you sign up to the Qt 4.6 Beta Program, then we will during the next
> month ask you to complete two surveys that ask for your impression of the
> quality of Qt 4.6. Those surveys will not take very long to complete, but
> you should of course be able to set some time aside to test the Qt 4.6
> Beta release. This release is expected to become available within the
> first weeks of October, and will be announced on the usual mailinglists.
>
> It is of course not necessary to sign up to the Beta program in order to
> get access to the Qt 4.6 Beta packages, and our regular feedback channel
> will continue to be open for everybody:
>
>  http://lists.trolltech.com/qt4-preview-feedback/
>
> However, through the Beta Program we hope to understand better how much Qt
> 4.6 has been tried and tested.
>
> We hope you will enjoy experimenting with the Qt 4.6 pre-releases and are
> looking forward to your feedback!
>
>  http://qt.nokia.com/doc/4.6-snapshot/qt4-6-intro.html
>
>
> On behalf of the Qt Team,
> Volker Hilsheimer
>
> --
> Qt Developer Days 2009 | Last Chance to Register!
> Munich, Germany: October 12th - 14th
> San Francisco, California: November 2nd - 4th
> Register now! http://qt.nokia.com/qtdevdays2009
>
>
> _______________________________________________
> Qt4-preview-feedback mailing list
> [email protected]
> http://lists.trolltech.com/mailman/listinfo/qt4-preview-feedback
>
>
>
>
>
> _______________________________________________
> Qt4-preview-feedback mailing list
> [email protected]
> http://lists.trolltech.com/mailman/listinfo/qt4-preview-feedback
>
>
>
> 


_______________________________________________
Qt4-preview-feedback mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt4-preview-feedback

Reply via email to