Recherche avancée

Sur d’autres sites (12101)

• ASPSMS : a successful integration with Piwik

  3 octobre 2017, par Piwik Core Team — Development

  Have you ever wondered how an integration between a third party company and Piwik is possible ? What are the key factors for a good partnership ? This article describes our recent collaboration with a company for a mobile messaging integration.

  At Piwik, we are always looking for new functionalities to build and improve the work of our community members. ASPSMS, an innovative SMS Gateway & Messaging solutions provider got in contact with us in order to do just this.

  Why did we decide to partner with ASPSMS ?

  • Fast
  • Easy
  • Just works

  Those three words define the collaboration we had with ASPSMS and in the end everyone benefits.

  Stefan, one of our developers who did the integration into Piwik, says “Thanks to an easy to understand API the SMS integration was done in a couple of hours. We got SMS credits upfront for testing which helped a lot.”

  Using the ASPSMS integration, you can receive a daily or weekly SMS message listing the Key Performance Indicators of your website(s).

  ASPSMS is now part of Piwik through the Mobile messaging settings :

  

  As a company, how can I contribute to Piwik ?

  If, like ASPSMS, you are providing great services which can help Piwik final users take better decisions, do not hesitate to contact the Piwik core team.

  You can also start to develop your own, specific plugins, that you can freely publish on the Piwik marketplace.

  About ASPSMS

  VADIAN.NET AG is today one of the leading global providers of SMS solutions with more than 200,000 satisfied business clients. The product ASPSMS was launched in 2001. ASPSMS is a product of VADIAN.NET AG, a Swiss based Internet and Mobile Solutions provider.

  

  Learn more about ASPSMS.

• Evolution #4146 (Fermé) : Invalideur lors de la publication : facultatif

  26 septembre 2018, par cedric -

  Bon pour commencer la ligne pointée est pas la bonne :)
  https://core.spip.net/projects/spip/repository/entry/spip/ecrire/action/editer_objet.php#L118 dit que si on modifie un objet déjà publié, ça invalide le cache, et c’est normal !

  C’est dans https://core.spip.net/projects/spip/repository/entry/spip/ecrire/action/editer_objet.php#L409 que l’on invalide le cache au moment de la publication.

  Et je ne pense vraiment pas qu’il faille changer ça en y mettant des dérogations.
  Par contre, si dans formidable les réponses sont juste stockées en base pour utilisation dans le back-office sans publication côté public, pourquoi leur donner le statut ’publie’ ? Appelons un chat un chat ! Le statut "publie" ça veut bien dire "à caractère publique, affichable sur le site public".

  Dans le cas présent, si tes données ne sont pas publiques, tu les mets en ’modération a priori’ dans la configuration de formidable et elles seront en statut ’proposée’ ce qui corrige tout tes problèmes sans gérer de cas particulier et en gardant la cohérence de tout le fonctionnement de SPIP

• Record window from CMD or PowerShell [closed]

  9 octobre 2023, par Pingui

  How can one record a window e.g. from the Command Promt or PowerShell ?

  


  I tried the following CMD-command which in principle works, but it cuts off the window (even with increased video_size 1920x1080, which seems to have no effect at all) :

  


  "C:\[your_path_to]\ffmpeg.exe" -f gdigrab -i title="New Tab - Google Chrome" -framerate 30 -video_size 1920x1080 -c:v libx264 -preset ultrafast -t 5 output.mp4


  


  The goal would be something like the above, but...

  


  

  1. Ideally, the window should be found not by its window title, but by its process name (e.g. chrome.exe)

  


  2. The video should be automatically fitted to the window size (even if larger than 1920x1080)

  


  3. The video-name.mp4 and video duration (-t) should be handed dynamically as input variables

  


  4. If the video-name.mp4 already exists, it should be overwritten without asking

  


  5. The windw should be recorded even if not on top

  


  


  Any solution in CMD, PowerShell or whatever can be called by Window's ShellExecuteW function and passed video-name.mp4 and video duration as inputs would be fine.