Evan,

I work with Keith Erskine at Padpaw. I'm looking into building an sms plugin.

I created a simple plugin just to try out the process (I responded to the StartNoticeSave event and made it send the message via sms using Padpaw). It was pretty easy to do and I like the plugin concept because its modular/clean. I know we'd definitely need some additional events to do a full sms plugin but I'm not sure whether we can do everything we want as a plugin.

For example, I'm currently investigating how to implement the sms "opt in" process required by the carriers. I'm not sure whether we can do that strictly as a plugin. You have code in place to add a phone number for text by email. It has its own confirmation process that is email/web based. If you gave me an event that would give me the phone number, I could us it to initiate our sms opt in process. That would work but I think, ideally, we would replace the existing process with an sms/phone based confirmation. Otherwise, it might be awkward/confusing.

I also have a question regarding the addition of database tables. It looks like objects that inherit from Memcached_Dataobject match the database tables and inherit the database access from the base class. If we were to add a database table, could we create a corresponding object derived from Memcached_Dataobject and leverage that code?

I'd appreciate any suggestions you have that might help.

Alison



----- Original Message ----- From: "Evan Prodromou" <[email protected]>
To: <[email protected]>
Sent: Wednesday, April 29, 2009 9:01 PM
Subject: [Laconica-dev] Pluginization


I'd like to set a goal for the 0.9.x release (July, probably) that all optional functionality (XMPP, Twitter, Facebook, SMS) be built as plugins.

Is that reasonable? I think we'll have to develop new events to make it work (including some events for ooffline queues), and some offline scripts (like the XMPP receiving script) would have to be outside of plugins, but otherwise I think it would be the right thing to do.

-Evan

_______________________________________________
Laconica-dev mailing list
[email protected]
http://mail.laconi.ca/mailman/listinfo/laconica-dev

_______________________________________________
Laconica-dev mailing list
[email protected]
http://mail.laconi.ca/mailman/listinfo/laconica-dev

Reply via email to