search

google-code-backups / lifepress

Automatically exported from code.google.com/p/lifepress
Other
0 stars 0 forks source link

Plugin API #11

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
I'd like Lifepress to have a plugins API that:

1. Ensures plugin compatibility by keeping the interfaces (semi-)static while 
allowing us to make whatever changes are necessary behind-the-scenes

2. Allows users to activate and de-activate plugins

3. Increases modularity

This is something I'd really like to discuss, mostly because we really won't 
be able to change the API's until the next major version (unless we go 
rolling release), otherwise we'll alienate potential plugin devs, so we're 
going to want smart, well-engineered, and easy to use API's (Think BeOS)

As a side note I'd like to point out that I don't mean that we can't add 
API's but altering the way published API's function is a bad idea for a minor 
version update.

Original issue reported on code.google.com by killpack99 on 12 Feb 2010 at 9:41

GoogleCodeExporter commented 8 years ago

Original comment by killpack99 on 15 Mar 2010 at 7:47

GoogleCodeExporter commented 8 years ago 
In "Add Feed" should be a list of the existing plugins that handles lifepress 
(flickr,facebook,twitter,etc) or a 
generic RSS plugin.

Example: List where I select Foursquare, I add my email and password (account 
information) that is stored under 
sql and then the plugin can get this information and talk to FourSquare API to 
get the latest item.

Original comment by djbl...@gmail.com on 16 Mar 2010 at 3:31

GoogleCodeExporter commented 8 years ago 
Agreed, I'll get started on documenting/implementing the Plugins API as soon as 
I 
finish with the Admin Dash issues (13 & 19)

Original comment by killpack99 on 16 Mar 2010 at 4:31

GoogleCodeExporter commented 8 years ago

Original comment by carsten....@gmail.com on 17 May 2010 at 9:28