Hi Francek, >> First we should discuss all concerns, if you care, pls >> answer them. BTW, it's supported on _some_ Linux distros. >> HB_WITH_QT_WEBKIT is no solution, but hack. Such setting >> should be resolved automatically. >> >> Or, it's still an option to move the whole QT related >> stuff from Harbour SVN to somewhere else and satisfy >> QT user special requests there. >> >> > > You are right. > As a leading architect of Harbour, you better know > how to make a portable solution for most platforms. > I started with xHarbour, but when i saw a quick advancement > (with very strict rules for quality) in Harbour, i switched. > I believe that Harbour is a best app platform. > But I also believe (and i have some experience) that > Webkit (or some other HTML5,SVG,AJAX,FLASH,.....) based > technology is a future.
WebKit is just an engine to process above standards (at least some them), render them, display them, handle some related features like caching, history, and maybe even doc parsing and creation. QT gives an API and classes to access them. Creation of doc can be useful, but IMO it has no point on the client side. And since it's mashed together with rendering engine, it's very difficult (and unsafe) to use it efficiently on the server side. So IMO Harbour's place in this scenario is rather the server side, to help creating documents complying with above standards, server them through an IP stack and make them work in standard browsers. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
