
Recherche avancée
Autres articles (26)
-
Submit enhancements and plugins
13 avril 2011If you have developed a new extension to add one or more useful features to MediaSPIP, let us know and its integration into the core MedisSPIP functionality will be considered.
You can use the development discussion list to request for help with creating a plugin. As MediaSPIP is based on SPIP - or you can use the SPIP discussion list SPIP-Zone. -
Emballe médias : à quoi cela sert ?
4 février 2011, parCe plugin vise à gérer des sites de mise en ligne de documents de tous types.
Il crée des "médias", à savoir : un "média" est un article au sens SPIP créé automatiquement lors du téléversement d’un document qu’il soit audio, vidéo, image ou textuel ; un seul document ne peut être lié à un article dit "média" ; -
Other interesting software
13 avril 2011, parWe don’t claim to be the only ones doing what we do ... and especially not to assert claims to be the best either ... What we do, we just try to do it well and getting better ...
The following list represents softwares that tend to be more or less as MediaSPIP or that MediaSPIP tries more or less to do the same, whatever ...
We don’t know them, we didn’t try them, but you can take a peek.
Videopress
Website : http://videopress.com/
License : GNU/GPL v2
Source code : (...)
Sur d’autres sites (5086)
-
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 !
-
Anomalie #2580 : les icones de l’espace privé sont pas belles et trop petites
20 octobre 2014, par cedric -Status quo...
-
automatically convert all video to mp4 h264 [on hold]
23 août 2013, par XiabiliI am a debian user and I have a lot of videos (wmv, flv, mp4 ... more than 100gb) on my server.
The problem is that the most of these videos are with mpeg4 and these codec is not supported by our Wowza server (basic License).
That is way we want to convert all these videos into H264 format.
So I need a script that converts videos recursively in the folders and if possible remove the old files after the converting.
I need your experience ! Thanks a lot !
Regards
Bili