Viktor Szakáts wrote:
>
> Sorry, but I don't understand: QWebKit is an embedded web
> browser component. Why do we need to implement a browser
> in Harbour?
>
> There are _plenty_ of free browsers on the market which
> do the job much better than any local effort in Harbour
> will ever do.
>
> Launch it and us it, that's all.
>
> If someone terribly needs a browser in a local window,
> it should be dead easy to implement it as a 3rd party
> project.
>
It is ok that we have not to implement it in Harbour.
But this is not ok that the use of QtWebKit is synonymous
to any web-browser in the market. QtWebKit is begins where
any web-browser ends. It transfers the control to desktop
application to present and exploit web-contents with
DBFCDX. No browser gives this flexibility.
To illustrate, you create a window as a web-page, design
its contents from some table's fields, capture the user-input,
naviage the www as your appln requires and accomplish
your target in modern environments. This alone opens up a
pandora of extensions.
The only point I disliked is its heavy load. But then, if you
ever visualized in the task manger, IE also consumes a
lot of memory.
QtWebKit is not a "browser" by definition, a framework
to design user-interface, even ReadModal() the WWW way.
It is much more than, to understand better, Alaska's WAA.
-----
enjoy hbIDEing...
Pritpal Bedi
_a_student_of_software_analysis_&_design_
--
View this message in context:
http://n2.nabble.com/SF-net-SVN-harbour-project-13834-trunk-harbour-tp4545547p4546782.html
Sent from the harbour-devel mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
