Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Developing U++ » U++ Developers corner » Porting Upp to SDL first ? (cause of MacOSX & framebuffer)
Re: Porting Upp to SDL first ? (cause of MacOSX & framebuffer) [message #30235 is a reply to message #29900] Fri, 17 December 2010 12:16 Go to previous messageGo to previous message
zsolt is currently offline  zsolt
Messages: 698
Registered: December 2005
Location: Budapest, Hungary
Contributor
mirek wrote on Sun, 28 November 2010 12:51

unodgs wrote on Sun, 28 November 2010 06:27


That's a really really great news. Can't wait to try it in action. That would save me a lot of time. I could simply avoid creating web version of my app. Gtk guys use canvas and javascript - seems to be a good choice.


Unfortunately, javascript appears to be to weak for RDP-like stream...

We would need at least Java to get what we want.

Plus, perhaps this technology will help in similar cases where Terminal services is usable, but would have big problem when your web latency is too high (just like with TS).



What about HTML5 Canvas and the full duplex WebSocket API in HTML5 Javascript?

See ThinVNC as an example.

[Updated on: Fri, 17 December 2010 12:23]

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: U++ video control to come soon
Next Topic: Rainbow Framebuffer - theide running
Goto Forum:
  


Current Time: Mon May 06 19:55:27 CEST 2024

Total time taken to generate the page: 0.01540 seconds