Recherche avancée

Sur d’autres sites (4488)

• How to publish your plugin or theme on the Piwik Marketplace – Introducing the Piwik Platform

  25 septembre 2014, par Thomas Steur — Community, Development

  This is the next post of our blog series where we introduce the capabilities of the Piwik platform. Over the last weeks we have already introduced you to some of the basics on how to create plugins and themes. This time you’ll learn how to publish a plugin or theme on the Piwik Marketplace to share it with all Piwik users.

  What is the Piwik Marketplace ?

  The Marketplace is a showcase for all plugins and themes that can be used in Piwik. You can browse them either on a standalone website or in Piwik itself by going to Settings => Marketplace. There you can install and update them with just one click. Easy as that ! While some of those plugins are provided by Piwik or Piwik PRO most of them are created and maintained by our community. Everyone is very welcome to distribute plugins or themes on the Marketplace.

  Prerequisites

  To publish your plugin on the Marketplace you simply need to meet these requirements :

  • The plugin name is not already taken by another plugin
  • The code of the plugin is hosted in a public GitHub repository
  • The GitHub service “Piwik plugins” for this repository is enabled (Repository Settings => Webhooks & Services => Add Service)
  • Push permission for this repository
  • The plugin is free (as in not paid)
  • The license must be compatible with the GNU General Public License v3 or any later version

  There is also list of Rules for plugins.

  Best practices

  Before actually distributing your plugin we recommend to follow a couple of best practices to make sure your plugin looks good on the Marketplace and provides useful information for your future users. If you have used the console to generate a plugin the needed files were already created for you.

  Provide a good description

  Make sure there is a file named README.md in the root of your plugin. When preparing your plugin for the Marketplace we will search for four sections in this file : Description, FAQ, Changelog and Support. Each of those is optional but it is good practice to provide at least a section Description and Support by prefixing them with ## . Any content of your readme outside of those sections will not be displayed on the Marketplace.

  # Piwik Plugin Name
  
  
  
  ## Description
  
  
  
  Add your plugin description here.
  
  
  
  ## Support
  
  
  
  Please direct any feedback to hello@piwik.org. 
  
  If you experience any issues feel free to file an issue at https://github.com/piwik/piwik/issues .

  A good example can be seen in the README.md of the CustomAlerts plugin and the related CustomAlerts plugin page.

  Provide screenshots

  This will improve your appearance in the Marketplace a lot and users will be more likely install your plugin. It is as easy as placing “png” or “jpg” files in a folder named screenshots. The filename of each image will be shown in the UI with underscores replaced by a whitespace. This way you can provide a nice description. Have a look at the CustomAlerts plugin to see how it works.

  Provide contact details

  Your contact details are specified in the plugin.json file of your plugin root folder. Providing at least one author and a link to your homepage is required. If you do not have a website you can use a link to your GitHub profile. This helps your users contact you in case they want to thank you for your great work or if they have any problem with it. An example plugin.json looks like this :

  {
  
      "name": "MyPluginName",
  
      "homepage": "http://piwik.org",
  
      "authors": [
  
          {
  
              "name": "Piwik",
  
              "email": "hello@piwik.org",
  
              "homepage": "http://piwik.org"
  
          }
  
      ],
  
      "support": {
  
        "email": "hello@piwik.org",
  
        "issues": "https://github.com/piwik/piwik/issues",
  
        "forum": "http://forum.piwik.org",
  
        "wiki": "https://github.com/piwik/piwik/wiki",
  
        "irc": "#piwik-dev"
  
      } 
  
  }

  Choose a license

  Choosing the right license that works best for you and your users is important. To distribute a plugin via the Piwik Marketplace the license must be compatible with the GNU General Public License v3 or any later version. If you do not specify a license anywhere in your plugin, it is assumed your plugin uses GPLv3 or later. The license must be specified in the plugin.json file using the property license :

  {
  
      "name": "MyPluginName",
  
      "license": "GPL v3+"
  
  }

  Provide donation links

  You can define a donation link or email for PayPal, Flattr and Bitcoin in the plugin.json file. Users that love your work will then be able to donate you money directly from the plugin page.

  {
  
      "name": "MyPluginName"
  
      "donate": {
  
          "paypal": "sponsor@piwik.org",
  
          "flattr": "https://flattr.com/profile/piwik",
  
          "bitcoin": "1234567890"
  
      }
  
  }

  How to publish the first version of your plugin

  We are trying to make it as easy as possible for you to publish your plugin on the Marketplace. That’s why we don’t require any logins or packaging. To publish your plugin you only have to create a new tag of your plugin and within a minute your plugin will be ready to be installed on hundreds of thousands of Piwik installations.

  To tag your plugin you can use one of the following two suggestions :

  Using the command line

  git tag 0.1.0 && git push --tags

  Where “0.1.0” is the name of the tag. While you can use any tag name it is best practice to use the current version number as defined in the plugin.json file.

  Using GitHub UI

  To tag a new version via GitHub click on Releases => Draft a new release.

  

  Now you can enter a tag name (version) and press “Publish release” as shown in this screen. That’s it !

  

  How to provide an update for your plugin

  To provide an update you only have to increase the version number in the file plugin.json and create another tag as explained in the previous section. Your new Plugin update will be visible on the Marketplace within a minute or so. It might take a bit longer until the update appears in Piwik itself as each Piwik server only checks for updates every few hours.

  For a complete list of information go to our Distributing Your Plugin guide in the Piwik Developer Zone.

  If you have any feedback regarding our APIs or our guides in the Developer Zone feel free to let us know.

• How to print(show) video(or image) on mfc window with ffmpeg [on hold]

  3 septembre 2014, par user3867261

  I want to make a video editor that has functions like playing video (h.264), drawing lines and figures on frames and video.

  So I got c++ ffmpeg library, and example code for encoding h.264.

  But I don’t know how to display video and image on mfc window.

  How can I do this ?

  I want to develop simple h.264 player on my mfc-project.

• Compiling qt project with use of ffmpeg on x64 system

  5 juin 2013, par Srv19

  I have a qt project that uses some ffmpeg functionality, that i have compiled previously on windows (x86) and ubuntu. However, its x86 binaries do not work correctly on x64 windows machine. I have tried compiling it but have run into a strange problem.

  All ffmpeg functions i use are listed as unresolved exgternals ; and the most pecicular thing is, their names all ahve a leading underscore attached to them (so, avformat_close_input -> _avformat_close_input etc). To be sure, i have downloaded latest ffmpeg libraries for x64 machines and run them through a dependency walker - no leading underscores anywhere.

  How to fix this problem ?

  Here is my .pro file :

  #-------------------------------------------------
  
  #
  
  # Project created by QtCreator 2013-05-17T10:55:01
  
  #
  
  #-------------------------------------------------
  
  
  
  
  
  QT       += core gui
  
  
  
  greaterThan(QT_MAJOR_VERSION, 4): QT += widgets
  
  
  
  TARGET = LPR_Demo
  
  TEMPLATE = app
  
  # The application version
  
  VERSION = 1.0
  
  
  
  # Define the preprocessor macro to get the application version in our application.
  
  DEFINES += APP_VERSION=\\\"$$VERSION\\\"
  
  SOURCES += main.cpp\
  
          mainwindow.cpp \
  
      imgProcessor.cpp \
  
      qpicturelabel.cpp \
  
      aboutdialog.cpp \
  
      state.cpp \
  
      qt_videoreader.cpp \
  
      roidialog.cpp \
  
      recognitionresult.cpp \
  
      ffmpeg_reader.cpp \
  
      label_videoplayer.cpp
  
  
  
  HEADERS  += mainwindow.h \
  
      imgProcessor.h \
  
      qpicturelabel.h \
  
      aboutdialog.h \
  
      state.h \
  
      qt_videoreader.h \
  
      roidialog.h \
  
      recognitionresult.h \
  
      global.h \
  
      ffmpeg_reader.h \
  
      label_videoplayer.h
  
  
  
  FORMS    += mainwindow.ui \
  
      aboutdialog.ui \
  
      roidialog.ui
  
  LPRDIR = $$PWD/LPR
  
  win32: LIBS += -L$$LPRDIR/bin/ -lliblpr
  
  unix:LIBS += -L$$LPRDIR/bin -lLPR
  
  
  
  INCLUDEPATH += $$LPRDIR/include
  
  
  
  DEPENDPATH += $$LPRDIR/include
  
  
  
  INCLUDEPATH += $$PWD/
  
  DEPENDPATH += $$PWD/
  
  
  
  #OTHER_FILES += \
  
  #    ffmpeg.pri
  
  include(ffmpeg.pri)
  
  #LIBS += -lavformat -lavcodec -lavutil -lswscale
  
  
  
  RESOURCES += \
  
      lpr_Res.qrc
  
  
  
  win32 {
  
  dlls_to_move.path += $$OUT_PWD/bin
  
  
  
  dlls_to_move.files += $$LPRDIR/bin/liblpr.dll
  
  
  
  QTDIR=C:/Qt/4.8.4/
  
  
  
  CONFIG (debug, debug|release) {
  
  
  
  dlls_to_move.files += $$QTDIR/bin/QtCored4.dll \
  
      $$QTDIR/bin/QtGuid4.dll
  
  
  
  }
  
  CONFIG (release, debug|release) {
  
  
  
  dlls_to_move.files += $$QTDIR/bin/QtCore4.dll \
  
      $$QTDIR/bin/QtGui4.dll
  
  }
  
  img_format.path += $$OUT_PWD/bin/imageformats
  
  CONFIG (debug, debug|release) {
  
  
  
  img_format.files += $$QTDIR/plugins/imageformats/qgifd4.dll \
  
      $$QTDIR/plugins/imageformats/qicod4.dll \
  
      $$QTDIR/plugins/imageformats/qjpegd4.dll \
  
      $$QTDIR/plugins/imageformats/qmngd4.dll \
  
      $$QTDIR/plugins/imageformats/qsvgd4.dll \
  
      $$QTDIR/plugins/imageformats/qtgad4.dll \
  
      $$QTDIR/plugins/imageformats/qtiffd4.dll
  
  
  
  }
  
  CONFIG (release, debug|release) {
  
  
  
  img_format.files += $$QTDIR/plugins/imageformats/qgif4.dll \
  
      $$QTDIR/plugins/imageformats/qico4.dll \
  
      $$QTDIR/plugins/imageformats/qjpeg4.dll \
  
      $$QTDIR/plugins/imageformats/qmng4.dll \
  
      $$QTDIR/plugins/imageformats/qsvg4.dll \
  
      $$QTDIR/plugins/imageformats/qtga4.dll \
  
      $$QTDIR/plugins/imageformats/qtiff4.dll
  
  }
  
  
  
  ffmpeg_dll.path += $$OUT_PWD/bin
  
  
  
  ffmpeg_dll.files += $$FFMPEG_LIBRARY_PATH/avutil-*.dll \
  
      $$FFMPEG_LIBRARY_PATH/avcodec-*.dll \
  
      $$FFMPEG_LIBRARY_PATH/avformat-*.dll \
  
      $$FFMPEG_LIBRARY_PATH/swscale-*.dll
  
  
  
  main_exe.path += $$OUT_PWD/bin
  
  CONFIG (debug, debug|release) {
  
  
  
  main_exe.files += $$OUT_PWD/debug/LPR_Demo.exe
  
  
  
  }
  
  CONFIG (release, debug|release) {
  
  main_exe.files += $$OUT_PWD/release/LPR_Demo.exe
  
  
  
  }
  
  INSTALLS += dlls_to_move img_format ffmpeg_dll main_exe
  
  }
  
  
  
  unix {
  
  CONFIG (release, debug|release) {
  
      QMAKE_PRE_LINK += rm LPR_Demo_cmpr LPR_Demo$$escape_expand(\n\t)
  
      QMAKE_POST_LINK += upx -9 -oLPR_Demo_cmpr LPR_Demo$$escape_expand(\n\t)
  
      QMAKE_POST_LINK += cp -v -u LPR_Demo_cmpr $$OUT_PWD/../artifacts/examples/qt_demo/bin/unix
  
  }
  
  }

  and here is pri file for ffmpeg :

  # Include the configuration file below in the QT .pro file, and modify the path accordingly.
  
  
  
  
  
  # ##############################################################################
  
  # ##############################################################################
  
  # FFMPEG: START OF CONFIGURATION BELOW ->
  
  # Copy these lines into your own project
  
  # Make sure to set the path variables for:
  
  # 1) ffmpeg_reader,
  
  # 2) FFMPEG include path (i.e. where the directories libavcodec, libavutil, etc. lie),
  
  # 3) the binary FFMPEG libraries (that must be compiled separately).
  
  # Under Linux path 2 and 3 may not need to be set as these are usually in the standard include and lib path.
  
  # Under Windows, path 2 and 3 must be set to the location where you placed the FFMPEG includes and compiled binaries
  
  # Note that the FFMPEG dynamic librairies (i.e. the .dll files) must be in the PATH
  
  # ##############################################################################
  
  # ##############################################################################
  
  
  
  # ##############################################################################
  
  # Modify here: set FFMPEG_LIBRARY_PATH and FFMPEG_INCLUDE_PATH
  
  # ##############################################################################
  
  
  
  # Set FFMPEG_LIBRARY_PATH to point to the directory containing the FFmpeg import libraries (if needed - typically for Windows), i.e. the dll.a files
  
  win32:FFMPEG_LIBRARY_PATH = $$PWD/ffmpeg/lib
  
  
  
  unix: FFMPEG_LIBRARY_PATH = /usr/local/lib
  
  
  
  # Set FFMPEG_INCLUDE_PATH to point to the directory containing the FFMPEG includes (if needed - typically for Windows)
  
  win32:FFMPEG_INCLUDE_PATH = $$PWD/ffmpeg/include
  
  unix:FFMPEG_INCLUDE_PATH = /usr/local/include
  
  # ##############################################################################
  
  # Do not modify: FFMPEG default settings
  
  # ##############################################################################
  
  
  
  
  
  # Set list of required FFmpeg libraries
  
  #unix:LIBS += -L$$FFMPEG_LIBRARY_PATH
  
  unix:LIBS += -lavformat -lavcodec -lavutil -lswscale
  
  # Add the path
  
  win32:LIBS += -L$$FFMPEG_LIBRARY_PATH
  
  win32:LIBS += -lavformat -lavcodec -lavutil -lswscale
  
  INCLUDEPATH += $$FFMPEG_INCLUDE_PATH
  
  
  
  # Requied for some C99 defines
  
  DEFINES += __STDC_CONSTANT_MACROS
  
  
  
  # ##############################################################################
  
  # FFMPEG: END OF CONFIGURATION
  
  # ##############################################################################