BEFORE BIDDING, PLEASE READ THE REQUIREMENTS! (it only takes a few minutes - thank you)
As part of a Chrome extension, I need a navigation skeleton (it shouldn't be polished, but fully functional) accomplishing the following user journey (see attached video for a visual demo of what you need to build).
1. Open an HTML file in a new popup window
2. Open Google Calendar in a new tab of the popup window
3. Setup Calendar
4. Monitor manually created calendar events
5. Come back to the original page with the extracted events
To consider your bid, PLEASE keep your messages short and relevant, and ONLY provide time and money estimates for the specs outlined above. If you really need to, add RELEVANT comments related to the project below that. "Copy-pasted" personal descriptions will be completely disregarded and rated 1 star. Thank you for respecting my time!
After being awarded the project, you would start from a working 'backbone' project, having all the setup required in terms of packaging and running the extension, including hot-reloading on Save (webpack|babel|jest|etc), so you can focus on building the functionality, not setup.
Deliverable: working source code + a short screen-sharing session (30 minutes) explaining how I can use and maintain the result.
Same specs, in full details:
- when visiting a certain page (a Udemy video course page or a Youtube video page, for instance),
- a background script of the extension opens a Modal dialog using Bootstrap 4 Modals (this must be non-blocking, so that the page is allowed to continue to run while the User interacts with the modal dialog)
- this modal has a button, 'Option #1', which opens a popup window (also from the background script, which I believe is required by the Chrome API)
- the popup window displays an HTML file ([login to view URL]) which uses Bootstrap 4 elements, including a button: 'Calendar'
- on click, the 'Calendar' button opens Google Calendar for the User, in a new tab of the same popup window, and switches to that tab
- any required permissions/authorization must be handled if needed, so that the User ends up connected to their own GCalendar account
- on this page (GCal), a new content script becomes active, which inserts a button in the page with the text '10 events' (this is simpler then presented in the video) and:
- saves the currently default calendar (so that we can restore it later)
- ensures a new, empty calendar (e.g. 'extension-calendar-123') is created and
- made 'default', so that any new calendar events the user creates are part of this 'fresh' calendar
- Monitor all created calendar events on this page and store them in an array
- update the button to reflect the number of created events (you don't need to deal with the calendar event objects in any way)
- When the User clicks this button,
- we restore the previously default calendar
- print all created events to the console,
- close the Calendar tab and
- return to the popup window ([login to view URL]) with a callback, giving access to all created Calendar events (the array of objects you created)
PS: If you have any questions, I would be more than happy to answer them all in the private chat, but only AFTER you make the effort to read and answer the optional questions below (to filter out the usual spam...) - Thank you!
1. number of real extensions you (or the person who will directly work on my project) have personally developed so far (not just following online tutorials)
2. approximate number of months actively developing JS apps
Hi, I will consider reading the whole description if you at least ping me otherwise it'll not be so meaningful, I'm respecting your time just two lines proposal... if agree with that, pls, ping... Thanks