
Recherche avancée
Autres articles (54)
-
La file d’attente de SPIPmotion
28 novembre 2010, parUne file d’attente stockée dans la base de donnée
Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...) -
Les vidéos
21 avril 2011, parComme les documents de type "audio", Mediaspip affiche dans la mesure du possible les vidéos grâce à la balise html5 .
Un des inconvénients de cette balise est qu’elle n’est pas reconnue correctement par certains navigateurs (Internet Explorer pour ne pas le nommer) et que chaque navigateur ne gère en natif que certains formats de vidéos.
Son avantage principal quant à lui est de bénéficier de la prise en charge native de vidéos dans les navigateur et donc de se passer de l’utilisation de Flash et (...) -
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
Sur d’autres sites (6332)
-
Piwik 3 Development Update #3 – Marketplace for Piwik Analytics
13 septembre 2016, par Piwik Core Team — Community, DevelopmentThis is our latest Piwik 3 development update where we present all changes that will be shipped with Piwik 3. Learn more about the exciting projects under progress in our Piwik 3 dev update #1 and dev update #2.
The Piwik Marketplace is the place where you can discover & download plugins to enrich the functionality of your Piwik, and themes to change the look and feel of your Piwik user interface. In preparation for our Piwik 3 release we have made several improvements to the Marketplace :
- Users can now view more information for a given plugin, such as a link to an online demo, a video demo, how to obtain support from the Plugin’s developer(s), and more.
- Users can now view which plugins are compatible with the most recent Piwik version, for example view which plugins are already compatible with Piwik 3.
- Plugin developers can now 1) promote their plugin better, 2) easily define requirement(s) for their plugins using composer.json version constraints (a best practise most developers already use) and 3) developers can define which files and directories should be excluded from the publicly available plugin zip packages.
These improvements will make it easier for you to discover new Piwik Analytics plugins to achieve your goals.
Marketplace now supports different Piwik versions
You can now filter plugins by Piwik version to see only plugins that are compatible with your Piwik.
When you browse the Marketplace in the Piwik app itself, you will automatically only see plugins and updates that are compatible with your Piwik.Better plugin preview
Plugin developers are able to display screenshots for their plugins, and now plugin developers can also specify a demo URL and a video in the “plugin.json” file. Adding a video to your plugin allows users to get a much better understanding of what your plugin does and how a theme looks.
Unified support page
In the past a developer had to define the text that was displayed on the support page. This often resulted in blank support pages or developers only showed an email address. With this new update, links and other support information are displayed in a standardised way as specified in the “support” section of the “plugin.json” file. A developer can now define links to an issue tracker, a wiki, the plugin’s source code and more.
License files
The license name on your plugin’s page is now clickable and can show the license text for your plugin. To define a license text for your plugin, create a file named
LICENSE
,LICENSE.md
orLICENSE.txt
.FAQ and Documentation
In the past a “FAQ” tab was displayed if such a section was present in the plugin’s readme file. This was hard to understand and sometimes ended up in long readme files. Now we pick up the FAQ content from a
docs/faq.md
file.For plugins developers who wish to provide a user guide(s), it is now possible to show a “documentation” tab to the plugin page by specifying a
docs/index.md
file.Changelog
When you define a file named
CHANGELOG
,CHANGELOG.md
orCHANGELOG.txt
in your plugin, we will show the content of this file in a tab “Changelog” on your plugin’s page. Before it was needed to specify the content of the changelog in the readme file.Exclude files from the plugin
If your plugin source code contains files that are not supposed to be present on a Piwik installation you can now choose to exclude files and directories from your plugin zip archive. When a user installs your plugin the excluded files won’t be there.
Migrating your plugin for Piwik 3
We recommend to all plugin developers to specify in the
plugin.json
file whether their plugin is compatible with Piwik 3 or not. If your plugin defines a “Changelog”, “Support” or “FAQ” section in theREADME.md
file we recommend to migrate this to the new structure. Read more about this in the migration guide.Until our next Piwik 3 dev update, Happy analysis !
-
How to restart the Ip Camera through ffmpeg or gstreamer ?
11 avril 2022, par HARSH BHATNAGARI am dealing with 550 IP camera , in which camera randomly power off due to power supply issue .
I need to restart the camera when the camera is online .


I have tried the IP ping concept , ffmpeg grabbing frame concept but the issue when we are integrating 550 camera IP ping concept it gives the False Positive and not able to restart the all camera whereas ffmpeg grabbing frame concept sometimes ffmpeg stuck in the terminal .

All testing code written in python language .
[ Note : i can't used the opencv for 550 camera ]
Please give me the suggestion how to deal with the problem .

-
7 Reasons to Migrate from Google Analytics to Matomo Now
15 mai 2022, par Erin