Recherche avancée

Sur d’autres sites (11301)

• FATE’s New Look

  4 août 2010, par Multimedia Mike — FATE Server

  The FATE main page exposes a lot of data. The manner in which it is presented has always been bounded by my extremely limited web development abilities. I wrestled with whether I should learn better web development skills first and allow that to inform any improved design, or focus on the more useful design and invest my web development learning time towards realizing that design.

  Fortunately, Mans solved this conundrum with an elegantly simple solution :

  
  
  

  The top of the page displays a status bar that illustrates — at a glance — how functional the codebase is. The web page source code identifies this as the failometer. It took me a few seconds to recognize what information that status bar was attempting to convey ; maybe it could use a succinct explanation.

  Mini-Book Review
  
  Before Mans took over, I thought about this problem quite a bit. I needed inspiration for creating a better FATE main page and aggregating a large amount of data in a useful, easily-digested form. Looking around the web, I see no shortage of methods for visualizing data. I could start shoehorning FATE data into available methods and see what works. But I thought it would be better to take a step back and think about the best way to organize the data. My first clue came awhile ago in the form of an xkcd comic : Blogofractal. Actually, the clue came from the mouseover text which recommended Edward Tufte’s "The Visual Display of Quantitative Information".

  
  
  

  I ordered this up and plowed through it. It’s an interesting read, to be sure. However, I think it illustrates what a book on multimedia and compression technology would look like if authored by yours truly— a book of technical curiosities from epochs past that discusses little in the way of modern practical application. Tufte’s book showed me lots of examples of infographics from decades and even centuries past, but I never concisely learned exactly how to present data such as FATE’s main page in a more useful form.

  Visualization Blog
  More recently, I discovered a blog called Flowing Data, authored by a statistics Ph.D. candidate who purportedly eats, sleeps, and breathes infographics. The post 11 Ways to Visualize Changes Over Time : A Guide offers a good starting point for creating useful data presentations.

  I still subscribe to and eagerly read Flowing Data. But I might not have as much use for data visualization now that Mans is on FATE duty.

• Anomalie #3418 : Les tables des plugins ne s’installent pas

  6 avril 2015, par Franck Dalot

  SPIP 3.1.0-alpha [21970]
  Test chez ovh sur un mutualisé, je ne sais si je suis sur ce cluster, mais de toute façon, ils doivent être tous pareil http://cluster015.ovh.net/infos

  Aucun prefix des tables particulier
  Les plugin était toujours agenda et Mini Calendrier

  *SQLite 3*++

  5.6.6 en mode prod = tables absente, mais présente dans une sauvegarde
  5.5.22 en mode prod = tables absente, mais présente dans une sauvegarde
  5.4.38 en mode prod = ok
  5.3.29 en mode prod = tables absente, mais présente dans une sauvegarde

  5.6.6 en mode dev = tables absente, mais présente dans une sauvegarde
  5.5.22 en mode dev = tables absente, mais présente dans une sauvegarde
  5.4.38 en mode dev = ok
  5.3.29 en mode dev = tables absente, mais présente dans une sauvegarde

  *SQLite 2*++
  5.3.29 en mode prod = tables absente, mais présente dans une sauvegarde
  Il y a une erreur qui s’affiche dans l’espace privé dès que j’y rentre :
  Numero : 1, message : Array, squelette : ecrire/public/composer.php, boucle : calculer_select() sql_select() ; , ligne : 876

  Par contre, je sais qu’elle est absente via ecrire/ ?exec=vertebres car quand j’essai de la lire via firefox, alors cela me sort :
  SQLiteManager : Error in opening file spip.sqlite - either the file is encrypted or corrupt
  Exception Name : NS_ERROR_FILE_CORRUPTED
  Exception Message : Component returned failure code : 0x8052000b (NS_ERROR_FILE_CORRUPTED) [mozIStorageService.openUnsharedDatabase]

  A savoir par contre que je peux parfaitement lire la sauvegarde via firefox

  5.3.29 en mode dev = Installation problématique, cela me sort des :
  Warning : sqlite_query() [function.sqlite-query] : near "ORDER" : syntax error in /ecrire/req/sqlite_generique.php on line 2703
  Http 302
  Si je clique sur le lien (il a un problème d’accent) l’installation se fait quand même, mais il y beaucoup de Warning... et toujours l’erreur dans le squelette

  Warning : sqlite_query() [function.sqlite-query] : near "ORDER" : syntax error in /home/liendami/www/spip3/spip/ecrire/req/sqlite_generique.php on line 2703
  Warning : sqlite_query() [function.sqlite-query] : no such column : auteurs.imessage in /home/liendami/www/spip3/spip/ecrire/req/sqlite_generique.php on line 2703
  Après linstallation des plugins, si je vais dans exec=sauvegarder
  Warning : sqlite_query() [function.sqlite-query] : no such table : spip_evenements in /home/liendami/www/spip3/spip/ecrire/req/sqlite_generique.php on line 2703
  Warning : sqlite_query() [function.sqlite-query] : no such table : spip_evenements_participants in /home/liendami/www/spip3/spip/ecrire/req/sqlite_generique.php on line 2703
  Cela me fait bien la sauvegarde, mais d’autres warning apparaisent pendant
  Sinon, c’est identique au mode "production"

  J’ai refais des 2 tests en MySQL (php 5.6.6 et php 5.4.38) en mode dev pour vérifier si les sauvegardes étaient avec ou sans les tables du plugin (je n’avais pas fait cette vérif avant)
  Dans les deux cas, il y avait les tables dans les sauvegardes
  Alors qu’elles étaient :
  Absente dans la bdd en 5.6.6
  Présente dans la bdd en 5.4.38

• On WebP and Academic Exercises

  2 octobre 2010, par Multimedia Mike — General

  Yesterday, Google released a new still image format called WebP. To those skilled in the art, this new format will be recognizable as a single VP8 golden frame with a 20-byte header slapped on the front (and maybe a little metadata thrown in for good measure). We have a MultimediaWiki page and a sample ready to go.

  Further, I submitted a patch to ffmpeg-devel for FFmpeg’s img2 handling system to decode these files. FFmpeg should support processing these files soon… if anyone cares. This leads into…

  The Point, or Lack Thereof
  Since yesterday’s release, I have read a whirlwind of commentary about this format, much of it critical and of the “what’s the point ?” variety. For my part, I can respect academic exercises, a.k.a., just trying random stuff to see if you can make it work. That’s pretty much this blog’s entire raison d’être. But WebP transcends mere academic exercise ; Google seems to be trying to push it as a new web standard. I don’t see how the format can go anywhere based on criticisms raised elsewhere — e.g., see Dark Shikari’s thoughtful write-up — which basically boil down to WebP not solving any real problems, technical, legal, or otherwise.

  How did WebP come to be ? I strongly suspect some engineers noticed that JPEG is roughly the same as an MPEG-1 intraframe, so why not create a new still frame format based on VP8 intraframes ? Again, I can respect that thinking– I have pondered how a still image format would perform if based on VP3/Theora or Sorenson Video 1.

  Technically
  Google claims a significant size savings for WebP vs. standard JPEG. Assuming that’s true (and there will be no shortage of blog posts to the contrary), it will still be some time before WebP support will find its way into the majority of the web browser population.

  But this got me thinking about possible interim solutions. A website could store images compressed in both formats if it so chose. Then it could serve up a WebM image if the browser could support it, as indicated by the ‘Accept’ header in the HTTP request. It seems that a website might have to reference a generic image name such as <img src="some-picture.image"> ; the web server would have to recognize the .image extension and map it to either a .jpg or a .webp image depending on what the browser claims it is capable of displaying.

  Leftovers
  I appreciate that Dark Shikari has once again stuck his neck out and made a valiant — though often futile — effort to educate the internet’s masses. I long ago resigned myself to the fact that many people aren’t going to understand many of the most basic issues surrounding multimedia technology (i.e., moving pictures synchronized with audio). But apparently, this extends to still image formats as well. It was simultaneously humorous and disheartening to see commenters who don’t even understand the application of, e.g., PNG vs. JPEG : Ahem, “We already have a great replacement for jpg : .PNG”. Coupled with the typical accusations of MPEG tribalism, I remain impressed D. Shikari finds the will to bother.

  Still, I appreciate that the discussion has introduced me to some new image formats of which I was previously unaware, such as PGF and JPEG XR.