Recherche avancée

Sur d’autres sites (15485)

• Piwik 3 Development Update #3 – Marketplace for Piwik Analytics

  13 septembre 2016, par Piwik Core Team — Community, Development

  This 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 or LICENSE.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 or CHANGELOG.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 the README.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 !

• Headless Selenium not Recording Video

  12 mai 2015, par TIMBERings

  I’m using the Headless gem to create a headless session using xvfb and to record the session using ffmpeg. I’m not able to save the video created by the headless gem. I’m including the relevant snippets of my code and the output.

  Code

  $LOGGER.info("----------Starting test: #{@test_name}----------")
  
  
  
  if Utilities.linux? && ENV['DRIVER'] != 'sauce'
  
    @headless = Headless.new ({dimension: '1600x1200x16',
  
                      pid_file_path: "#{Utilities.get_root_directory}/tmp/headless_ffmpeg_#{@display}.pid",
  
                      tmp_file_path: "#{Utilities.get_root_directory}/tmp/headless_ffmpeg_#{@display}.mov",
  
                      log_file_path: "#{Utilities.get_root_directory}/tmp/headless_ffmpeg_#{@display}.txt"})
  
    @headless.start
  
    @headless.video.start_capture
  
    $LOGGER.info 'Creating headless session.'
  
  end
  
  $browser = DefaultWatir.initiate_browser(@test_name)
  
  
  
  if Utilities.linux? && ENV['DRIVER'] != 'sauce'
  
    $LOGGER.info "Starting video recording"
  
    @headless.video.start_capture
  
  end
  
  
  
  .........          .........
  
  ......... TEST RUN .........
  
  .........          .........
  
  
  
  $LOGGER.info "----------Ending test: #{@test_name}----------"
  
   puts "\n\n"
  
  
  
  $browser.close if $browser
  
  save_video if @headless
  
  
  
  def video_path
  
    return "#{Utilities.get_root_directory}/video/#{@test_name}_#{Time.now.to_s.gsub(' ', '-')}"
  
  end
  
  
  
  def save_video
  
    if Utilities.linux?  && ENV['DRIVER'] != 'sauce'
  
      unless self.instance_variable_get(:@exception).nil? && !$has_errors
  
        saved_video_path = video_path
  
        Dir.mkdir("#{Utilities.get_root_directory}/video") unless Dir.exists?("#{Utilities.get_root_directory}/video")
  
        $LOGGER.info "Video path = #{saved_video_path}"
  
        begin
  
          $LOGGER.info 'before save'
  
          @headless.video.stop_and_save(saved_video_path)
  
          $LOGGER.info 'after save'
  
        rescue ex
  
          $LOGGER.info 'Video save had exception.'
  
          puts ex.message
  
          puts ex.backtrace.join("\n\t")
  
        end
  
        $LOGGER.info "Video saved at: #{saved_video_path}"
  
      else
  
        @headless.video.stop_and_discard
  
      end
  
      @headless.destroy
  
    end
  
  end

  Output

  [INFO - 2015-03-06 21:58:37 +0000] - ----------Starting test : Example Test----------

  [INFO - 2015-03-06 21:58:37 +0000] - Creating headless session.

  [INFO - 2015-03-06 21:58:40 +0000] - Starting video recording

  [INFO - 2015-03-06 22:02:04 +0000] - ----------Ending test : Example Test----------

  INFO - 2015-03-06 22:02:05 +0000] - Video path = /var/lib/jenkins/workspace/end_to_end_firefox/selenium-tests/video/PoolPlayToSingleEliminationOneDivision_2015-03-06-22:02:05-+0000

  [INFO - 2015-03-06 22:02:05 +0000] - before save

  [INFO - 2015-03-06 22:02:05 +0000] - after save

  [INFO - 2015-03-06 22:02:05 +0000] - Video saved at : /var/lib/jenkins/workspace/end_to_end_firefox/selenium-tests/video/PoolPlayToSingleEliminationOneDivision_2015-03-06-22:02:05-+0000

• What's the best way to package FFMPEG for distribution ?

  5 mai 2021, par Fernando Ortega

  I need to make FFMPEG available to external clients (in their local machine) so they can use some of the code I'm providing to them.

  


  This is just needed for Windows 10 at the moment.

  


  I know there are pre-built FFMPEG binaries, is it enough for me to provide that or do I need to build/compile it myself ?

  


  Note : I do not need to make any changes to the ffmpeg code.

  


  I'd also love to know if there is specific license/legal information I need to provide within my software ?

  


  Thanks in advace !