Recherche avancée

Sur d’autres sites (10650)

• Evolution #4283 : Mettre en place un raccourcis typo pour lié la page du site dans notre site

  8 mars 2020, par YannX Spip

  Meme si le vocable est moins parlant (surtout maintenant que la syndication est souvent omise...), il suffit de se souvenir
  du nom originel de la boucle (SYNDIC) et non (SITES),
  pour écrire [->syndic1]....

  Mais il est vrai que la documentation [1] n’est pas bien explicite ; en particulier j’ai été "enduit avec de l’erreur" en lisant la définition de
  - #URL_SYNDIC affiche l’adresse (URL) du fichier de syndication de ce site, qui est elle vraiement dérogatoire...
  - et revenir à une boucle (SYNDIC) dans les exemples aiderait aussi les utilisateurs à dépasser cette exception historique.

  En allant rechercher dans l’aide SPIP [2] on retrouve bien l’origine de cette erreur, qu’il conviendrait de corriger
  

  Auteurs, mots-clés, sites, images, documents :
  lien vers un auteur ou le même auteur
  lien vers un mot
  lien vers un site syndiqué

  Et, sauf problème de rupture de compatibilité (à pallier dans un plugin additionnel ?),
  il serait effectivement logique d’uniformiser le traitement des sites, pour revenir au langage commun...
  Serait-il suffisant de différentier les traitements de* #URL_SITEnn_id* et #URL_SITE (encore que le problème ne se pose que dans une boucle portant sur un objet editorial comprenant aussi un champ #URL_SITE ou #URL_SYNDIC.....

• error while install FFMPEG-PHP

  30 juillet 2016, par Box Lyrics

  I’m trying to install FFmpeg and FFMPEG-PHP .
  The installation of FFmpeg is success but when i try to install FFMPEG-PHP i get this error

      # make
  
  /bin/sh /root/ffmpeg_sources/ffmpeg-php-0.6.0/ffmpeg-php/libtool --mode=compile cc  -I. -I/root/ffmpeg_sources/ffmpeg-php-0.6.0/ffmpeg-php -DPHP_ATOM_INC -I/root/ffmpeg_sources/ffmpeg-php-0.6.0/ffmpeg-php/include -I/root/ffmpeg_sources/ffmpeg-php-0.6.0/ffmpeg-php/main -I/root/ffmpeg_sources/ffmpeg-php-0.6.0/ffmpeg-php -I/usr/include/php -I/usr/include/php/main -I/usr/include/php/TSRM -I/usr/include/php/Zend -I/usr/include/php/ext -I/usr/include/php/ext/date/lib  -DHAVE_CONFIG_H  -g -O2   -c /root/ffmpeg_sources/ffmpeg-php-0.6.0/ffmpeg-php/ffmpeg_movie.c -o ffmpeg_movie.lo
  
  libtool: compile:  cc -I. -I/root/ffmpeg_sources/ffmpeg-php-0.6.0/ffmpeg-php -DPHP_ATOM_INC -I/root/ffmpeg_sources/ffmpeg-php-0.6.0/ffmpeg-php/include -I/root/ffmpeg_sources/ffmpeg-php-0.6.0/ffmpeg-php/main -I/root/ffmpeg_sources/ffmpeg-php-0.6.0/ffmpeg-php -I/usr/include/php -I/usr/include/php/main -I/usr/include/php/TSRM -I/usr/include/php/Zend -I/usr/include/php/ext -I/usr/include/php/ext/date/lib -DHAVE_CONFIG_H -g -O2 -c /root/ffmpeg_sources/ffmpeg-php-0.6.0/ffmpeg-php/ffmpeg_movie.c  -fPIC -DPIC -o .libs/ffmpeg_movie.o
  
  /root/ffmpeg_sources/ffmpeg-php-0.6.0/ffmpeg-php/ffmpeg_movie.c:42:32: error: libavcodec/version.h: No such file or directory
  
  /root/ffmpeg_sources/ffmpeg-php-0.6.0/ffmpeg-php/ffmpeg_movie.c:76:1: warning: "MAX_STREAMS" redefined
  
  In file included from /root/ffmpeg_sources/ffmpeg-php-0.6.0/ffmpeg-php/ffmpeg_movie.c:43:
  
  /usr/include/libavformat/avformat.h:569:1: warning: this is the location of the previous definition
  
  /root/ffmpeg_sources/ffmpeg-php-0.6.0/ffmpeg-php/ffmpeg_movie.c: In function ‘php_get_dict_value’:
  
  /root/ffmpeg_sources/ffmpeg-php-0.6.0/ffmpeg-php/ffmpeg_movie.c:509: error: ‘AVDictionaryEntry’ undeclared (first use in this function)
  
  /root/ffmpeg_sources/ffmpeg-php-0.6.0/ffmpeg-php/ffmpeg_movie.c:509: error: (Each undeclared identifier is reported only once
  
  /root/ffmpeg_sources/ffmpeg-php-0.6.0/ffmpeg-php/ffmpeg_movie.c:509: error: for each function it appears in.)
  
  /root/ffmpeg_sources/ffmpeg-php-0.6.0/ffmpeg-php/ffmpeg_movie.c:509: error: ‘m_entry’ undeclared (first use in this function)
  
  /root/ffmpeg_sources/ffmpeg-php-0.6.0/ffmpeg-php/ffmpeg_movie.c: In function ‘zim_ffmpeg_movie_getPixelFormat’:
  
  /root/ffmpeg_sources/ffmpeg-php-0.6.0/ffmpeg-php/ffmpeg_movie.c:828: warning: assignment makes pointer from integer without a cast
  
  /root/ffmpeg_sources/ffmpeg-php-0.6.0/ffmpeg-php/ffmpeg_movie.c: In function ‘_php_get_codec_name’:
  
  /root/ffmpeg_sources/ffmpeg-php-0.6.0/ffmpeg-php/ffmpeg_movie.c:918: error:                          ‘AV_CODEC_ID_MPEG2TS’ undeclared (first use in this function)
  
  make: *** [ffmpeg_movie.lo] Error 1

  this is what i have execute

  #  git clone https://github.com/tony2001/ffmpeg-php.git
  
  #  cd ffmpeg-php
  
  #  make clean
  
  #  phpize 
  
  #  ./configure 
  
  #  make

  when i search for a solution i found this :
  If you get an error message like make : *** [ffmpeg_movie.lo] Error 1 open the ffmpeg_movie.c file and make the following changes :

  user@myVPS:~# vim ffmpeg_movie.c

  Change list_entry *le ; to zend_rsrc_list_entry *le ;
  Change list_entry new_le ; to zend_rsrc_list_entry new_le ;
  Change hashkey_length+1, (void *)&new_le, sizeof(list_entry), to hashkey_length+1, (void *)&new_le,sizeof(zend_rsrc_list_entry),

  but when i check the ffmpeg_movie.c i found that is already fixed with this changes.
  I can’t find the probleme

• 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 !!