privly / privly-opera Goto Github PK

Modify options.html so that when the background process sends the login result, it's displayed in the following manner:

1. If success: Show success alert message and close tab.
2. Else: Display the error message around the login form itself.

Alerts can get annoying.

We need a way of throttling injection of iframes when pages have thousands of Privly-type links. This could destroy browser performance.

All strings are hardcoded as of now.
Replace them with strings stored in opera.widgets.preferences object.

The current layout and colors have been selected without much thought. A cleaner interface for popup.html and the settings page is needed.

After Opera moved to WebKit, they adopted the same extension framework as Chromium. Thus, the Opera extension is now developing on a branch of the Privly-Chrome repository.

Since Opera doesn't currently support a ContextMenu API, I have a basic plan that involves clicking the extension button on the toolbar to post content to Privly.
If that doesn't work, figure out alternatives.

As of now it just has a login form. Make it look better with Icon placement and CSS styling.

1. Add Logout button on Preferences Page.
2. Port Firefox version of logoutFromPrivly() in background.js to Opera.

We need an easy way to activate and deactivate the extension without accessing Opera's extension settings. The simplest way to implement this functionality is to control when the content script is injected (privly.js), but we could also send messages to the content script after it is loaded.
The toggle button could be placed inside popup.html .

I updated Privly.js to not inject links that are within editable nodes. This fixes an apparently major issue with the newest version of gmail, as well as other sites using the Closure library.

Currently, strings are hardcoded.
Add localization support when extension is able to post content to Privly