Recherche avancée

Sur d’autres sites (7209)

• How to add new pages and menu items to Piwik – Introducing the Piwik Platform

  11 septembre 2014, par Thomas Steur — Development

  This is the next post of our blog series where we introduce the capabilities of the Piwik platform (our previous post was How to create a widget). This time you’ll learn how to extend Piwik by adding new pages and menu items. For this tutorial you will need to have basic knowledge of PHP and optionally of Twig which is the template engine we use.

  What can be displayed in a page ?

  To make it short : You can display any corporate related content, key metrics, news, help pages, custom reports, contact details, information about your server, forms to manage any data and anything else.

  Getting started

  In this series of posts, we assume that you have already set up your development environment. If not, visit the Piwik Developer Zone where you’ll find the tutorial Setting up Piwik.

  To summarize the things you have to do to get setup :

  • Install Piwik (for instance via git).
  • Activate the developer mode : ./console development:enable --full.
  • Generate a plugin : ./console generate:plugin --name="MyControllerPlugin". There should now be a folder plugins/MyControllerPlugin.
  • And activate the created plugin under Settings => Plugins.

  Let’s start creating a page

  We start by using the Piwik Console to create a new page :

  ./console generate:controller

  The command will ask you to enter the name of the plugin the controller should belong to. I will simply use the above chosen plugin name “MyControllerPlugin”. There should now be two files plugins/MyControllerPlugin/Controller.php and plugins/MyControllerPlugin/templates/index.twig which both already contain an example to get you started easily :

  Controller.php

  class Controller extends \Piwik\Plugin\Controller
  {
      public function index()
      {
          return $this->renderTemplate('index', array(
               'answerToLife' => 42
          ));
      }
  }
  Télécharger

  and templates/index.twig

  {% extends 'dashboard.twig' %}
   
  {% block content %}
      <strong>Hello world!</strong>
      <br/>
   
      The answer to life is {{ answerToLife }}
  {% endblock %}
  Télécharger

  Note : If you are generating the Controller before Piwik 2.7.0 the example will look slightly different.

  The controller action index assigns the view variable answerToLife to the view and renders the Twig template templates/index.twig. Any variable assigned this way can then be used in the view using for example {{ answerToLife }}.

  Using a Twig template to generate the content of your page is actually optional : instead feel free to generate any content as desired and return a string in your controller action.

  As the above template index.twig is extending the dashboard template the Logo as well as the top menu will automatically appear on top of your content which is defined within the block content.

  

  How to display the page within the admin

  If you would like to add the admin menu on the left you have to modify the following parts :

  • Extend \Piwik\Plugin\ControllerAdmin instead of \Piwik\Plugin\Controller in the file Controller.php. In a future version of Piwik this step will be no longer neccessary, see #6151
  • Extend the template admin.twig instead of dashboard.twig
  • Define a headline using an H2-element

  {% extends 'admin.twig' %}
   
  {% block content %}
      <h2>Hello world!</h2>
      <br/>
   
      The answer to life is {{ answerToLife }}
  {% endblock %}
  Télécharger

  Note : Often one needs to add a page to the admin to make a plugin configurable. We have a unified solution for this using the Settings API.

  

  How to display a blank page

  If you would like to generate a blank page that shows only your content the template should contain only your markup as follows :

  <strong>Hello world!</strong>
  <br/>
   
  The answer to life is {{ answerToLife }}
  Télécharger

  Predefined variables, UI components, security and accessing query parameters

  In this blog post we only cover the basics to get you started. We highly recommend to read the MVC guide on our developer pages which covers some of those advanced topics. For instance you might be wondering how to securely access $_GET or $_POST parameters, you might want to restrict the content of your page depending on a user role, and much more.

  If you would like to know how to make use of JavaScript, CSS and Less have a look at our Working with Piwik’s UI guide.

  Note : How to include existing UI components such as a site selector or a date selector will be covered in a future blog post. Also, there are default variables assigned to the view depending on the context. A list of those variables that may or may not be defined is unfortunately not available yet but we will catch up on this.

  Let’s add a menu item to make the page accessible

  So far you have created a page but you can still not access it. Therefore we need to add a menu item to one of the Piwik menus. We start by using the Piwik Console to create a menu template :

  ./console generate:menu

  The command will ask you to enter the name of the plugin the menu should belong to. I will use again the above chosen plugin name “MyControllerPlugin”. There should now be a file plugins/MyControllerPlugin/Menu.php which contains an example to get you started easily :

  Menu.php

  class Menu extends \Piwik\Plugin\Menu
  {
      public function configureUserMenu(MenuUser $menu)
      {
          // reuse an existing category. 
          $menu->addManageItem('My User Item', $this->urlForAction('showList'));
   
          // or create a custom category
          $menu->addItem('My Custom Category', 'My User Item', $this->urlForDefaultAction());
      }
  }
  Télécharger

  This is only a part of the generated template since all the examples of the different menus are similar. You can add items to four menus :

  • configureReportingMenu To add a new item to the reporting menu which includes all the reports like “Actions” and “Visitors”.
  • configureAdminMenu To add a new item to the admin menu which includes items like “User settings” and “Websites”.
  • configureTopMenu To add a new item to the top menu which includes items like “All Websites” and “Logout”.
  • configureUserMenu To add a new item to the user menu which is accessible when clicking on the username on the top right.

  In this blog post we will add a new item to the user menu and to do so we adjust the generated template like this :

  class Menu extends \Piwik\Plugin\Menu
  {
      public function configureUserMenu(MenuUser $menu)
      {
          $menu->addManageItem('My User Item', $this->urlForAction($method = 'index'), $orderId = 30);
      }
  }
  Télécharger

  That’s it. This will add a menu item named “My User Item” to the “Manage” section of the user menu. When a user chooses the menu item, the “index” method of your controller will be executed and your previously created page will be first rendered and then displayed. Optionally, you can define an order to influence the position of the menu item within the manage section. Following this example you can add an item to any menu for any action. I think you get the point !

  

  Note : In Piwik 2.6.0 and before the above example would look like this :

  class Menu extends \Piwik\Plugin\Menu
  {
      public function configureUserMenu(MenuUser $menu)
      {
          $menu->addManageItem('My User Item', array($module = 'MyControllerPlugin', $action = 'index'), $orderId = 30);
      }
  }
  Télécharger

  How to test a page

  After you have created your page you are surely wondering how to test it. A controller should be usually very simple as it is only the connector between model and view. Therefore, we do usually not create unit or integration test for controllers and for the view less than ever. Instead we would create a UI test that takes a screenshot of your page and compares it with an expected screenshot. Luckily, there is already a section UI tests in our Automated tests guide.

  Publishing your Plugin on the Marketplace

  In case you want to share your page with other Piwik users you can do this by pushing your plugin to a public GitHub repository and creating a tag. Easy as that. Read more about how to distribute a plugin.

  Advanced features

  Isn’t it easy to create a page ? We never even created a file ! Of course, based on our API design principle “The complexity of our API should never exceed the complexity of your use case.” you can accomplish more if you want : You can make use of Vanilla JavaScript, jQuery, AngularJS, Less and CSS, you can reuse UI components, you can access query parameters and much more.

  Would you like to know more about this ? Go to our MVC (Model-View-Controller) and Working with Piwik’s UI guides in the Piwik Developer Zone.

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

• Nomenclature #4626 (Nouveau) : Renommer le menu "Squelettes"

  13 janvier 2021, par RastaPopoulos ♥

  Un petit pavé en début d’année, comme ça peut-être qu’en décembre on aura un début d’idée de quoi faire. :D

  Constat : dans mon expérience, 100% des gens à qui on apprend à utiliser éditorialement SPIP, admins et rédacs donc, n’ont strictement aucune fichue idée de ce que veut dire "Suqelettes", ni quel est le rapport avec le contenu qu’il y a à l’intérieur. Passer du temps à devoir expliquer un terme qui n’aura jamais aucun sens dans leurs activités quotidiennes est une perte de temps pour tout le monde, et 3 mois plus tard illes l’auront oublié vu que ça n’a de rapport avec rien dans leur vie d’admins/rédacs.

  Le fait de faire une référence à l’histoire technique de SPIP, ça ne parle qu’aux devs/intégrateurices : fort peu de gens par rapport à la masse des admins et rédacs qui vont l’utiliser au quotidien.

  Quand on se retire, en tant que devs/ingégrateurices, alors en gros 99% des utilisateurices de l’interface d’admin sont des gens qui ne savent rien du tout de comment c’est techniquement derrière, et même pour beaucoup qui n’ont jamais choisi spécialement ce CMS, et même allons plus loin : assez souvent qui ne savent même pas quel est le CMS utilisé !

  Et point important : ces gens ne devraient avoir aucune obligation de le savoir pour utiliser pourtant comme il faut l’interface.

  Si on leur apprend, parce que nous on aime SPIP et qu’on est enthousiaste à raconter son histoire et comment il marche, c’est super. Mais ça ne doit PAS être une obligation pour comprendre l’interface du premier coup.

  Mon idée (toute relative, c’est pour démarrer quoi) : revenir à des choses simples et couramment utilisées. Il n’y a aucun intérêt spécial à vouloir être original quand on parle quand même du menu principal d’admin.

  Le fait de changer l’intitulé, va forcément changer légèrement le sens, donc quelques plugins qui s’insèrent dedans devront possiblement être déplacés ailleurs. Mais il me semble que ça restera très à la marge, et que la majorité ça correspond toujours. Ça ne doit pas bloquer pour changer. Donc :
  - Mise en page
  - Présentation
  - …

  Dans WP il y a une entrée principale "Apparence", mais ce n’est justement pas notre cas : il faut un terme plus large, qui couvre à la fois les choix graphiques (changer ou configurer un thème, choisir la boite modale…) et les choix de structuration générale, de navigation (Compositions, Menus…).

  Dans ma tête "Mise en page" est pour le moment le terme le plus vaste qui me vient à l’esprit, et qui regroupe plusieurs notions à la fois, pas juste l’apparence graphique. S’il y a mieux tant mieux, du moment que ça regroupe bien ces différentes notions. L’autre jour sur spip-dev Laurent (c-real) disait surcharger avec ce terme aussi pour ses utilisateurices.

  On ne trouvera sûrement jamais le mot parfait à 100%, mais ça sera toujours 1000 fois mieux que "Squelettes" qui vraiment, après 10 ans à devoir l’expliquer en permanence, ne signifie rien pour personne à part nous.

• Android : Select from images extracted with FFMPEG

  21 juillet 2017, par Tix

  I’m currently able to extract images(frames) from a video, and display all the extracted images using the code below, how do i make it so that the displayed images could be selected by user and passed as a bitmap to another activity ?

  FFMPEG Compiled using

  compile ’com.writingminds:FFmpegAndroid:0.3.2’

  Complex Command used to get the frames/images

  String[] complexCommand = "-y", "-i", yourRealPath, "-an", "-framerate", "60", "-vf", "select=’gte(n,45)’", "-vsync", "0", dest.getAbsolutePath() ;

  Main Activity

          /**
  
           * Command for extracting images from video
  
           */
  
          private void extractImagesVideo(int startMs, int endMs) {
  
              File moviesDir = Environment.getExternalStoragePublicDirectory(
  
                      Environment.DIRECTORY_PICTURES
  
              );
  
  
  
              String filePrefix = "extract_picture";
  
              String fileExtn = ".jpg";
  
              String yourRealPath = getPath(MainActivity.this, selectedVideoUri);
  
  
  
              File dir = new File(moviesDir, "VideoEditor");
  
              int fileNo = 0;
  
              while (dir.exists()) {
  
                  fileNo++;
  
                  dir = new File(moviesDir, "VideoEditor" + fileNo);
  
  
  
              }
  
              dir.mkdir();
  
              filePath = dir.getAbsolutePath();
  
              File dest = new File(dir, filePrefix + "%03d" + fileExtn);
  
  
  
  
  
              Log.d(TAG, "startTrim: src: " + yourRealPath);
  
              Log.d(TAG, "startTrim: dest: " + dest.getAbsolutePath());
  
  
  
              String[] complexCommand = {"-y", "-i", yourRealPath, "-an", "-r", "1/2", "-ss", "" + startMs / 1000, "-t", "" + (endMs - startMs) / 1000, dest.getAbsolutePath()};
  
  
  
              execFFmpegBinary(complexCommand);
  
  
  
          }
  
  
  
       /**
  
           * Executing ffmpeg binary
  
           */
  
          private void execFFmpegBinary(final String[] command) {
  
              try {
  
                  ffmpeg.execute(command, new ExecuteBinaryResponseHandler() {
  
                      @Override
  
                      public void onFailure(String s) {
  
                          Log.d(TAG, "FAILED with output : " + s);
  
                      }
  
  
  
                      @Override
  
                      public void onSuccess(String s) {
  
                          Log.d(TAG, "SUCCESS with output : " + s);
  
                          if (choice == 1 || choice == 2 || choice == 5 || choice == 6 || choice == 7) {
  
                              Intent intent = new Intent(MainActivity.this, PreviewActivity.class);
  
                              intent.putExtra(FILEPATH, filePath);
  
                              startActivity(intent);
  
                          } else if (choice == 3) {
  
                              Intent intent = new Intent(MainActivity.this, PreviewImageActivity.class);
  
                              intent.putExtra(FILEPATH, filePath);
  
                              startActivity(intent);
  
                          } else if (choice == 4) {
  
                              Intent intent = new Intent(MainActivity.this, AudioPreviewActivity.class);
  
                              intent.putExtra(FILEPATH, filePath);
  
                              startActivity(intent);
  
                          } else if (choice == 8) {
  
                              choice = 9;
  
                              reverseVideoCommand();
  
                          } else if (Arrays.equals(command, lastReverseCommand)) {
  
                              choice = 10;
  
                              concatVideoCommand();
  
                          } else if (choice == 10) {
  
                              File moviesDir = Environment.getExternalStoragePublicDirectory(
  
                                      Environment.DIRECTORY_MOVIES
  
                              );
  
                              File destDir = new File(moviesDir, ".VideoPartsReverse");
  
                              File dir = new File(moviesDir, ".VideoSplit");
  
                              if (dir.exists())
  
                                  deleteDir(dir);
  
                              if (destDir.exists())
  
                                  deleteDir(destDir);
  
                              choice = 11;
  
                              Intent intent = new Intent(MainActivity.this, PreviewActivity.class);
  
                              intent.putExtra(FILEPATH, filePath);
  
                              startActivity(intent);
  
                          }
  
                      }

  PreviewImageActivity

      public class PreviewImageActivity extends AppCompatActivity {
  
  
  
          private static final String FILEPATH = "filepath";
  
              @Override
  
              protected void onCreate(@Nullable Bundle savedInstanceState) {
  
                  super.onCreate(savedInstanceState);
  
                  setContentView(R.layout.activity_gallery);
  
                  getSupportActionBar().setDisplayHomeAsUpEnabled(true);
  
                  getSupportActionBar().setDisplayShowHomeEnabled(true);
  
                  TextView tvInstruction=(TextView)findViewById(R.id.tvInstruction) ;
  
  
  
                  GridLayoutManager lLayoutlLayout = new GridLayoutManager(PreviewImageActivity.this, 4);
  
                  RecyclerView rView = (RecyclerView)findViewById(R.id.recycler_view);
  
                  rView.setHasFixedSize(true);
  
                  rView.setLayoutManager(lLayoutlLayout);
  
                  String filePath = getIntent().getStringExtra(FILEPATH);
  
                  ArrayList<string> f = new ArrayList<string>();
  
  
  
  
  
  
  
     File dir = new File(filePath);
  
              tvInstruction.setText("Images stored at path "+filePath);
  
              File[] listFile;
  
  
  
                  listFile = dir.listFiles();
  
  
  
  
  
  
  
              for(File e:listFile)
  
              {
  
                  f.add(e.getAbsolutePath());
  
              }
  
  
  
              PreviewImageAdapter rcAdapter = new PreviewImageAdapter( f);
  
              rView.setAdapter(rcAdapter);
  
  
  
  
  
          }
  
      @Override
  
      public boolean onOptionsItemSelected(MenuItem item) {
  
          // handle arrow click here
  
          if (item.getItemId() == android.R.id.home) {
  
              finish(); // close this activity and return to preview activity (if there is any)
  
          }
  
  
  
          return super.onOptionsItemSelected(item);
  
      }
  
  }
  
  </string></string>

  PreviewImageAdapter

  public class PreviewImageAdapter extends RecyclerView.Adapter {
  
  
  
      private ArrayList<string> paths;
  
  
  
      public PreviewImageAdapter( ArrayList<string> paths) {
  
          this.paths = paths;
  
      }
  
  
  
      @Override
  
      public MyViewHolder onCreateViewHolder(ViewGroup parent, int viewType) {
  
          View itemView = LayoutInflater.from(parent.getContext())
  
                  .inflate(R.layout.item_gallery, parent, false);
  
  
  
          return new MyViewHolder(itemView);
  
      }
  
  
  
      @Override
  
      public void onBindViewHolder(MyViewHolder holder, int position) {
  
          Bitmap bmp = BitmapFactory.decodeFile(paths.get(position));
  
          holder.ivPhoto.setImageBitmap(bmp);
  
      }
  
  
  
      @Override
  
      public int getItemCount() {
  
          return paths.size();
  
      }
  
  
  
      public class MyViewHolder extends RecyclerView.ViewHolder {
  
          private ImageView ivPhoto;
  
  
  
          public MyViewHolder(View itemView) {
  
              super(itemView);
  
  
  
              ivPhoto = (ImageView) itemView.findViewById(R.id.ivPhoto);
  
          }
  
      }
  
  
  
  }
  
  </string></string>