Recherche avancée

Médias (91)

Autres articles (40)

  • Les tâches Cron régulières de la ferme

    1er décembre 2010, par

    La gestion de la ferme passe par l’exécution à intervalle régulier de plusieurs tâches répétitives dites Cron.
    Le super Cron (gestion_mutu_super_cron)
    Cette tâche, planifiée chaque minute, a pour simple effet d’appeler le Cron de l’ensemble des instances de la mutualisation régulièrement. Couplée avec un Cron système sur le site central de la mutualisation, cela permet de simplement générer des visites régulières sur les différents sites et éviter que les tâches des sites peu visités soient trop (...)

  • Emballe médias : à quoi cela sert ?

    4 février 2011, par

    Ce 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" ;

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

Sur d’autres sites (4132)

  • configure : remove libdl dependency from libndi_newtek

    10 octobre 2017, par Marton Balint
    configure : remove libdl dependency from libndi_newtek
    

    We are not using dynamic loading for libndi.

    Reviewed-by : James Almer <jamrial@gmail.com>
    Signed-off-by : Marton Balint <cus@passwd.hu>

    • [DH] configure
  • How to check for DLL/SO before calling JNA Native.loadLibrary to avoid UnsatisfiedLinkError

    4 septembre 2013, par user1305332

    I'm loading a native library (ffmpeg) using JNA but I need to check if the DLL/SO file exists before actually calling Native.loadLibrary(). FFMPEG may not always be installed in the system (it's a seperate download).

    Native.loadLibrary() throws an ERROR which you can not trap with a try {} catch {}.

    How do I check if the library (DLL or SO) exists before actually calling loadLibrary() ?
    Would I have to just parse the PATH environment variable and check myself ? I would have to check against Windows and Linux and ensure the correct 32/64bit .dll or .so is installed ???

    I wish loadLibrary just returned a null pointer or threw an exception, not an error (bad design).

  • configure : _deps : validate, reduce sensitivity

    28 août 2018, par Avi Halachmi (:avih)
    configure : <fflib>_deps : validate, reduce sensitivity
    

    - Allow to add deps in any order rather than "in linking order".
    - Expand deps chains as required rather than just once.
    - Validate that there are no cycles.
    - Validate that [after expansion] deps are limited to other fflibs.
    - Remove expectation for a specific output order of unique().

    Previously when adding items to <fflib>_deps, developers were
    required to add them in linking order. This can be awkward and
    bug-prone, especially when a list is not empty, e.g. when adding
    conditional deps.

    It also implicitly expected unique() to keep the last instance of
    recurring items such that these lists maintain their linking order
    after removing duplicate items.

    This patch mainly allows to add deps in any order by keeping just
    one master list in linking order, and then reordering all the
    <fflib>_deps lists to align with the master list order.

    This master list is LIBRARY_LIST itself, where otherwise its order
    doesn't matter.

    The patch also removes a limit where these deps lists were expanded
    only once. This could have resulted in incomplete expanded lists,
    or forcing devs to add already-deducable deps to avoid this issue.

    Note : it is possible to deduce the master list order automatically
    from the deps lists, but in this case it's probably not worth the
    added complexity, even if minor. Maintaining one list should be OK.

    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>

    • [DH] configure