I am experimenting on an unofficial application that I added to
KDE, specifically to Konqueror source code.
This will perform download and upload over the Internet and SSL.
I would like to just place a simple progress bar that continually loops
while download or upload is being performed. No percentage, just indicator
to the user that the trasaction is taking place.
I plan to create a class derived from QThread w/c contains QProgressBar.
And plans to just show this just before download/upload starts and end it
just after the download/upload is finished.
I am confused as to how could I show this GUI/thread/ProgressBar?
Should I get "qApp" at "run" function and from threre set the widget as main
and could I do qApp->exec()? B
That suggetion for https transfers api is okay had i known it beforehand.
What i am using is curlpp for all http transactions.
My question yesterday is actually this:
I just would like to show a progress bar gui
besides the integrated application i did in KDE-Konqueror.
KDE-Koqueror will show this progress bar while doing the https transfers.
I had a class that is based on a timer that updates the progress bar automatically.
The progress bar also is just a looping progress bar. Not dependent on anything,
as long as the transfers are taking place.
So, is it okay if I just throw in a new thread as the progress bar gui,
and be able to continue on the next statement of the code w/c will perform
the https transfer? Both running together, and from that main thead just
terminate the progress bar thread?
You can use the additional thread to do you transfer routine, you then have the even loop thread available to run the timer which updates the progress bar.
Anyway, I still think switching to KIO would be less work, as it already works, uses KDE's proxy settings and certificate handling, etc.