EVA

 Week 8: (31/05/2021) During our 1st review to the department we had specified that the "@" and "at" recognition was a bit challenging, so we modified the speech input method in such a way that if the user says the username part of the email address and upon ending his speech input the extension would append "@gmail.com" to the text. But what about other email clients? We are looking into how to interface with the user if he wants to change the client name of the email address. We also might change this whole method so be tuned in for that.  We also looked into gmail.js, A package which can used as an alternative to Gmail APIs for all CRUD operations, but we found few drawbacks such as It mainly requires the gmail window to be open for the functioning of the extension Slows down the load time of gmail window If you have too many functions specified you may get your gmail account suspended ( speaking from experience, do not recommend that, the account did g...

  Week 6: Built an extension that can call Gmail APIs to get information like id, unread emails count etc We logged those information on the console Found out that each email can have a different mime type like text/HTML and text/plain Implemented Artyom.js' command functionality into our extension    Week 7:   Used Artyom.js' command functions to switch between a subject box and a compose box in our popup We also could print the unread emails count on our extension's popup display Made our extension to update it's unread emails count for every 1 minute Retrieved text/plain mime type of an email   Next steps:  Iterate around with the commands function to see what suits best for our email operations   Commands interfering with the content in subject and body   Reading  attachments, Formatted contents, dealing with email threads. Noisy environment might pose a challenge for the speech synthesis of the user’s audio input.  

 Fifth Week Progress(10/05/2021): Added a textbox which can be used to store in all the textual content which the user wants to mail. Used Speech Recognition to recognize all the contents the user would speak out and convert it into a textual format. Used artyom.js throughout for speech synthesis  Started testing out the Commands feature available in the artyom library. Explored the speech synthesis package p5.speech.js to build a basic webpage which speaks out hardcoded text Made a few changes in the basic extension which used chrome.tts.speech to speak out hardcoded text   In the next week:   We will be integrating all of this an extension for testing purposes. We also will be testing out other stt and tts libraries to use in our project.