Re: [Interest] Bringing Qt, C++ To The Web

> -Original Message- > > Anyway, that [zero-install] is definitely a legitimate issue. However > >I have to puke and kick a puppy when it comes to overall web development. > > We were approaching something really good with Java and .NET, but > >these got sidelined by a handful of easy-to-

Re: [Interest] Bringing Qt, C++ To The Web

On Fri, Jan 18, 2013 at 7:19 AM, Jason H wrote: > Bringing this discussion back to Qt, there is something that elegantly does > this already. QML. Drop the idea that it > is for GPUs and graphics and instead use it to serialize to HTML/JS/CSS (or > my JML) and you have your new, 1-technology web,

Re: [Interest] QNetworkAccessManager in a command line, non-eventloop application

On sexta-feira, 18 de janeiro de 2013 17.08.46, Scott Aron Bloom wrote: > On sexta-feira, 18 de janeiro de 2013 01.49.35, Scott Aron Bloom wrote: > > I don't want to block > > Yet you're describing exactly a blocking situation: > > I would like a background thread and have the request run in there

Re: [Interest] Bringing Qt, C++ To The Web

On 17/01/2013 09:50 م, Jason H wrote: What is the "web" you speak of? LOL Anyway, that [zero-install] is definitely a legitimate issue. However I have to puke and kick a puppy when it comes to overall web development. We were appro

Re: [Interest] Bringing Qt, C++ To The Web

On 16/01/2013 09:30 م, Pau Garcia i Quiles wrote: On Wed, Jan 16, 2013 at 9:16 PM, Jan Krause wrote: I read this post yesterday, I found Emscripten-Qt really promisin

Re: [Interest] QNetworkAccessManager in a command line, non-eventloop application

On sexta-feira, 18 de janeiro de 2013 01.49.35, Scott Aron Bloom wrote: > I don't want to block Yet you're describing exactly a blocking situation: > I would like a background thread and have the request run in there, > using the QThreads event loop. The background thread runs an event loop, su

Re: [Interest] QNetworkAccessManager in a command line, non-eventloop application

> -Original Message- > From: interest-bounces+scott.bloom=onshorecs@qt-project.org > [mailto:interest-bounces+scott.bloom=onshorecs@qt-project.org] On > Behalf Of Thiago Macieira > Sent: Thursday, January 17, 2013 5:27 PM > To: interest@qt-project.org > Subject: Re: [Interest] QNe

Re: [Interest] Bringing Qt, C++ To The Web

18.01.2013, 18:24, "Pau Garcia i Quiles" : > On Fri, Jan 18, 2013 at 3:19 PM, Jason H wrote: > >> Bringing this discussion back to Qt, there is something that elegantly does >> this already. QML. Drop the idea that it >> is for GPUs and graphics and instead use it to serialize to HTML/JS/CSS (or

Re: [Interest] Bringing Qt, C++ To The Web

Heh, I looked back, he wrote as a reply to my thread. His sample code was: load('wt.js'); var w; var widget = new Wt.WContainerWidget({     width: '100px',     height: '200px',     children: [         w = new Wt.WText({             width: '100px',             height: '200px'         })     ] });

Re: [Interest] Bringing Qt, C++ To The Web

Well I've been posting about QML as a web technology for over a year now. Maybe 2. And I'm on the Wt list for about a year ;-) I can understand why they want that - it would work in existing browsers. I would have preferred QML as well, however this would require a plug-in for what is a small f

Re: [Interest] Bringing Qt, C++ To The Web

That is not a fair simplication of mime. Base64 encoding anyone? Chuncked-length encoding? From: Mandeep Sandhu To: Nikos Chantziaras Cc: "Interest@qt-project.org" Sent: Friday, January 18, 2013 9:22 AM Subject: Re: [Interest] Bringing Qt, C++ To The Web

Re: [Interest] Bringing Qt, C++ To The Web

On Fri, Jan 18, 2013 at 3:19 PM, Jason H wrote: > Bringing this discussion back to Qt, there is something that elegantly > does this already. QML. Drop the idea that it > is for GPUs and graphics and instead use it to serialize to HTML/JS/CSS > (or my JML) and you have your new, 1-technology web

Re: [Interest] Bringing Qt, C++ To The Web

>> OT, but isn't that done by examining file extensions or file headers >> (like how the 'file' command works in Linux)? > > Once you've detected what the data is, you need to tell whomever asked > about it what it actually is. You need a communication protocol for > that. Like MIME. So you get

Re: [Interest] Bringing Qt, C++ To The Web

SOAP with attachments can get quite tricky with it's attachment headers. No, I meant what I wrote. MIME ditched for JSON. Convert the MIME array of headers to a JSON dictionary. It is more flexible. While no one in the real world has called for it, it would eliminate the need to learn MIME (asid

Re: [Interest] Bringing Qt, C++ To The Web

Except of course in Wt, where you can mark C++ functions for export to JavaScript. Which might seem trivial but It gives you a built-in abstraction layer if MS decides to be insolent and only support JScript or F# or something. From: Nikos Chantziaras To: i

Re: [Interest] Bringing Qt, C++ To The Web

On 18/01/13 13:41, Samuel Rødal wrote: No, NaCL provides sand-boxing as well and is thus a very safe alternative to downloading a native executable. Downloading and installing a browser plugin tends to be a much more stream-lined process too. I guess someone just needs to write a killer applicat

Re: [Interest] Bringing Qt, C++ To The Web

On 01/17/2013 05:00 PM, Nikos Chantziaras wrote: > On 17/01/13 17:51, Konstantin Tokarev wrote: >> >> >> 17.01.2013, 19:38, "Nikos Chantziaras" : >>> On 17/01/13 17:31, Pau Garcia i Quiles wrote: >>> On Thu, Jan 17, 2013 at 4:28 PM, Nikos Chantziaras >>>> wrote:

Re: [Interest] QNetworkAccessManager in a command line, non-eventloop application

On sexta-feira, 18 de janeiro de 2013 01.49.35, Scott Aron Bloom wrote: > I don't want to block Yet you're describing exactly a blocking situation: > I would like a background thread and have the request run in there, using > the QThreads event loop. The background thread runs an event loop, sur

Re: [Interest] Bringing Qt, C++ To The Web

On 18/01/13 11:35, Mandeep Sandhu wrote: > On Fri, Jan 18, 2013 at 2:46 PM, Konstantin Tokarev wrote: >> >> >> 18.01.2013, 12:44, "Mandeep Sandhu" : to know a minimum of 3 technologies, but more like 6: HTML, JS, CSS, MIME, >>> >>> MIME's a tech?!?! I thought it's just a standard used

Re: [Interest] Bringing Qt, C++ To The Web

18.01.2013, 13:35, "Mandeep Sandhu" : > On Fri, Jan 18, 2013 at 2:46 PM, Konstantin Tokarev wrote: > >>  18.01.2013, 12:44, "Mandeep Sandhu" :   to know a minimum of 3 technologies, but more like 6: HTML, JS, CSS, MIME, >>>  MIME's a tech?!?! I thought it's just a standard used in ema

Re: [Interest] Bringing Qt, C++ To The Web

On Fri, Jan 18, 2013 at 2:46 PM, Konstantin Tokarev wrote: > > > 18.01.2013, 12:44, "Mandeep Sandhu" : >>> to know a minimum of 3 technologies, but more like 6: HTML, JS, CSS, MIME, >> >> MIME's a tech?!?! I thought it's just a standard used in emails and >> HTTP headers to define the content typ

Re: [Interest] QNetworkAccessManager in a command line, non-eventloop application

On Friday 18 January 2013 10:02:24 Mandeep Sandhu wrote: > Just curious here, but why don't you want to run the event loop in the > main thread but only run it in a different thread? Probably because the environment it's going to be used in already utilizes its own event loop... I had a similar si

Re: [Interest] Bringing Qt, C++ To The Web

18.01.2013, 12:44, "Mandeep Sandhu" : >>  to know a minimum of 3 technologies, but more like 6: HTML, JS, CSS, MIME, > > MIME's a tech?!?! I thought it's just a standard used in emails and > HTTP headers to define the content type. It's also a common way to distinguish file types on Unix-like sy

Re: [Interest] QNetworkAccessManager in a command line, non-eventloop application

On Fri, Jan 18, 2013 at 7:19 AM, Scott Aron Bloom wrote: > -Original Message- > From: interest-bounces+scott.bloom=onshorecs@qt-project.org > [mailto:interest-bounces+scott.bloom=onshorecs@qt-project.org] On Behalf > Of Thiago Macieira > Sent: Thursday, January 17, 2013 5:27 PM >

Re: [Interest] Bringing Qt, C++ To The Web

> to know a minimum of 3 technologies, but more like 6: HTML, JS, CSS, MIME, MIME's a tech?!?! I thought it's just a standard used in emails and HTTP headers to define the content type. > SQL, .NET or Java or PHP, not to mention Linux/IIS server administration. > > The reason I puke is the number