CiviCRM Community Forums (archive)

Today's activity: 1. Post the blog post after reviewing with Joe Murray and then discuss about the mockup of configuration page
Tomorrow: Architecture of Voice Broadcast module

The schema will aim to support all elements of the mocked up UI, and make use either of the Mailings tables in core or their design patterns.

Today's activities:
A simple app based on Layered Architecture

Tomorrow Activities:
1. implement voip service provider as abstract interface
2. implement plivo and twilio voip service providers as instantiations of abstract interface
 3. create a tiny D8 module that registers a url to be executed
4. create a tiny civix extension that also executes same function when a particular url is hit

Today's activity:
D8 module is done.

Tomorrow's Activity:
TBA

Rain has created a very simple stub module for D8 to illustrate how he could do the calls for forms and persistence. Separately, he has created an extension to work with CiviCRM to do the same thing. The point is to allow both to interact with common functions for VoIP providers and VoIP functionality like sending a voice broadcast. That way there will be some common shared code between a Drupal only VOIP Drupal set of modules and a CiviCRM set of extensions for various voice applications.

Yesterday's Activities:
1. Implemented DOA classes of Call, voice and recipients. codes: https://github.com/eftakhairul/biz.jmaconsulting.voice/commits/master
2. Studied about Doctrine integration in extension as well as DB layer

Today's Activities:
1. I will implement Doctrine  and will convert all the tables in Doctrine entities.

Blocks?
1. Need to know how community implements doctrine connection param in CIVICRM

The issue is more how to send the recording of the message for a single call, according to Rain.

See https://www.plivo.com/docs/api/call/play/

Rain was planning to refactor the core CiviMail UI code so that it can run in the extension and display the appropriate fields for the extension. Joe and Rain agreed that it might be simpler for Rain to implement using AngularJS in an extension rather than trying to replicate core's use of State Machines, etc for the wizard. Rain will examine the 5.0 Saloon threads for discussion of multi-tab widgets for Symfony. Rain will play with getting one or two to work tomorrow. In particular, he will start by trying to get AngularJS running and creating 2 tabs in it with a few dummy fields.