Recherche avancée

Sur d’autres sites (7837)

• Progress with rtc.io

  12 août 2014, par silvia

  At the end of July, I gave a presentation about WebRTC and rtc.io at the WDCNZ Web Dev Conference in beautiful Wellington, NZ.

  

  Putting that talk together reminded me about how far we have come in the last year both with the progress of WebRTC, its standards and browser implementations, as well as with our own small team at NICTA and our rtc.io WebRTC toolbox.

  

  One of the most exciting opportunities is still under-exploited : the data channel. When I talked about the above slide and pointed out Bananabread, PeerCDN, Copay, PubNub and also later WebTorrent, that’s where I really started to get Web Developers excited about WebRTC. They can totally see the shift in paradigm to peer-to-peer applications away from the Server-based architecture of the current Web.

  Many were also excited to learn more about rtc.io, our own npm nodules based approach to a JavaScript API for WebRTC.

  

  We believe that the World of JavaScript has reached a critical stage where we can no longer code by copy-and-paste of JavaScript snippets from all over the Web universe. We need a more structured module reuse approach to JavaScript. Node with JavaScript on the back end really only motivated this development. However, we’ve needed it for a long time on the front end, too. One big library (jquery anyone ?) that does everything that anyone could ever need on the front-end isn’t going to work any longer with the amount of functionality that we now expect Web applications to support. Just look at the insane growth of npm compared to other module collections :

  

  For those that – like myself – found it difficult to understand how to tap into the sheer power of npm modules as a font end developer, simply use browserify. npm modules are prepared following the CommonJS module definition spec. Browserify works natively with that and “compiles” all the dependencies of a npm modules into a single bundle.js file that you can use on the front end through a script tag as you would in plain HTML. You can learn more about browserify and module definitions and how to use browserify.

  For those of you not quite ready to dive in with browserify we have prepared prepared the rtc module, which exposes the most commonly used packages of rtc.io through an “RTC” object from a browserified JavaScript file. You can also directly download the JavaScript file from GitHub.

  

  So, I hope you enjoy rtc.io and I hope you enjoy my slides and large collection of interesting links inside the deck, and of course : enjoy WebRTC ! Thanks to Damon, JEeff, Cathy, Pete and Nathan – you’re an awesome team !

  On a side note, I was really excited to meet the author of browserify, James Halliday (@substack) at WDCNZ, whose talk on “building your own tools” seemed to take me back to the times where everything was done on the command-line. I think James is using Node and the Web in a way that would appeal to a Linux Kernel developer. Fascinating !!

• Evolution #2184 : Passer la dist en HTML5

  25 septembre 2017, par RastaPopoulos ♥

  Moi je propose plutôt de supprimer cette case à cocher "HTML5" : elle ne signifie absolument rien pour les non-devs. Les admins qui voient ça, soit ne comprennent rien du tout, soit ont juste entendu le buzzword, mais ne savent pas du tout ce que ça signifie en pratique.

  Le fait d’activer la génération de HTML5 par SPIP (pour les plugins, modèles, etc), c’est au jeu de squelettes de le décider : c’est LUI et lui seul qui définit les doctypes des squelettes.

  Donc cette activation devrait se faire dans le "options.php" des jeux de squelettes qui sont en HTML5 et uniquement là.

• lavf/http: Reset compressed header flag, fix http 302 request

  20 juillet 2017, par Jacek Jendrzej

  lavf/http: Reset compressed header flag, fix http 302 request
  Fixes ticket #6404.
  
  Fixes ticket #6666.
  Signed-off-by : Jacek Jendrzej <satbaby@kawaii.com>
  

  • [DH] libavformat/http.c