
Recherche avancée
Autres articles (111)
-
Multilang : améliorer l’interface pour les blocs multilingues
18 février 2011, parMultilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela. -
HTML5 audio and video support
13 avril 2011, parMediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
For older browsers the Flowplayer flash fallback is used.
MediaSPIP allows for media playback on major mobile platforms with the above (...) -
ANNEXE : Les plugins utilisés spécifiquement pour la ferme
5 mars 2010, parLe site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)
Sur d’autres sites (10664)
-
How to correctly setup Linker in Eclipse IDE 4.8.0M4 for ffmpeg development (Ubuntu)
28 janvier 2018, par boergiI am using Eclipse IDE 4.8.0M4 on Ubunto 16.04. I try to compile the code from a FFmpeg tutorial on GitHUB : (https://github.com/leandromoreira/ffmpeg-libav-tutorial/blob/master/0_hello_world.c). For setting up FFmpeg in Eclipse i used this guide :(https://trac.ffmpeg.org/wiki/Setup_Eclipse_IDE_for_FFmpeg_(Linux)).
The header files and libaries are all in the folder /home/git/ffmpeg. (e.g. avcodec.h and libavcodec.a is in the folder /home/git/ffmpeg/libavcodec). Included libs : -lavcodec -lpostproc -lz -llzma -lrt -lavfilter -lswresample -lavdevice -lswscale -lavutil -lavformat
Console output :
12:34:30 **** Incremental Build of configuration Debug for project ffmpeg_test ****
make all
Building target: ffmpeg_test
Invoking: GCC C Linker
gcc -L/home/git/ffmpeg/libavcodec -L/home/git/ffmpeg/libavformat -o "ffmpeg_test" ./src/simpletest.o -lavcodec -lpostproc -lz -llzma -lrt -lavfilter -lswresample -lavdevice -lswscale -lavutil -lavformat
./src/simpletest.o: In function `main':
/home/boergi/eclipse-workspace/ffmpeg_test/Debug/../src/simpletest.c:141: undefined reference to `avcodec_parameters_to_context'
/home/boergi/eclipse-workspace/ffmpeg_test/Debug/../src/simpletest.c:163: undefined reference to `av_packet_alloc'
/home/boergi/eclipse-workspace/ffmpeg_test/Debug/../src/simpletest.c:194: undefined reference to `av_packet_free'
./src/simpletest.o: In function `decode_packet':
/home/boergi/eclipse-workspace/ffmpeg_test/Debug/../src/simpletest.c:214: undefined reference to `avcodec_send_packet'
/home/boergi/eclipse-workspace/ffmpeg_test/Debug/../src/simpletest.c:225: undefined reference to `avcodec_receive_frame'
collect2: error: ld returned 1 exit status
makefile:30: recipe for target 'ffmpeg_test' failed
make: *** [ffmpeg_test] Error 1
12:34:31 Build Finished (took 519ms)I found out that "int avcodec_parameters_to_context(AVCodecContext *codec, const AVCodecParameters *par)" is defined in utils.c (also in the /libavcodec folder), but i don’t know what can i do to get this running.
boergi@Ubuntu-b:~/git/ffmpeg$ ffmpeg -version
ffmpeg version N-89895-g7723750 Copyright (c) 2000-2018 the FFmpeg developers
built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.5) 20160609
configuration:
libavutil 56. 7.100 / 56. 7.100
libavcodec 58. 9.100 / 58. 9.100
libavformat 58. 5.101 / 58. 5.101
libavdevice 58. 0.101 / 58. 0.101
libavfilter 7. 11.101 / 7. 11.101
libswscale 5. 0.101 / 5. 0.101
libswresample 3. 0.101 / 3. 0.101 -
5 questions you should ask yourself before defining a custom alert in Matomo
24 janvier 2018, par InnoCraftIn Matomo, you can create Custom Alerts to automatically be notified of important changes on your website or app. They are a great way to save time, but they also spam your mailbox quickly. Defining good custom alerts takes therefore time and requires some preparations. Here are recommendations on what you should focus on to only get the right alerts at the right time.
There are several questions you should ask yourself before you define a custom alert :
- Do you really want to be alerted ? If the answer is no, then do not use this feature.
- What is the level of this alert ? Not important, interesting, highly critical… if it is not highly critical, do not define an alert for this. Probably the emailing report or custom reports feature will be a better fit.
- How would you like to be alerted ? SMS, email, sound, homing pigeon (unfortunately we do not support this feature at that time). If you are looking at your emails once a week, then defining a daily email alert won’t make sense.
- How would you like the alert to be named ? Give your alert the most explicit name, that’s the first information you will see when you get alerted.
- What will be the next step once the alert is triggered ? If you cannot find any action once the alert is triggered, then probably an alert doesn’t make sense.
Once those questions are answered, you can start configuring custom alerts. There are many alerts you can define but as just mentioned, which alerts you should create always depends on your goals and what is critical to you, or your business. Let’s look at some custom alerts that we see quite often.
No visit
One of the easiest custom alert to define. You probably want to be alerted if your website did not receive any visit. As this alert is highly critical, you will want to receive an e-mail, even an SMS. This alert will trigger only if the number of visits is below 1 on a daily basis :
Here the action we will take is to have a look at the website in order to see if it is still live. If the site still works, we will look at the tracking code in order to see if the website is still correctly tracked or not.
Convinced of this custom alert ? Let’s look at another example.
Target achieved
Let’s say you gave a goal to one of your employee to reach a specific threshold in terms of conversions. You can then define a custom alert in order to inform you when the threshold has been reached.
You can simply do this with an alert saying “Target achieved by Franck” where number of conversions equals the number of actions you defined with him. It takes you only a minute to define something you would have missed otherwise.
Here the actions we can think of are either to congratulate Franck or to ask him what is going wrong if the target is not achieved.
Did you know that you can also take advantage of Matomo premium features to define custom alerts ? Let’s see one of them.
Lost SEO ranking
If you are using the Search Engine Keyword Performance premium feature, there are really interesting combinations you can use to create custom alerts.
For example, you can be notified when a specific keyword lost or reached a position :You will be alerted when your website is losing some positions within the search engine results for specific keywords. Here the action we could take is to investigate why we lost a position on Google for this keyword.
There are many custom alert combinations waiting for you out there. Why not giving them a try ? If you have any questions, feel free to ask them on the Matomo forums.
The post 5 questions you should ask yourself before defining a custom alert in Matomo appeared first on Analytics Platform - Matomo.
-
Q&A : An interview with Matomo founder, Matthieu Aubry