On 11/9/09 6:30 AM, Craig Andrews wrote:
Presently, there is no way for a command (such as "reply" [new to 0.9]) to
process an attachment, which can lead to non-intuitive interactation.

For example, using the web interface, if I enter "reply @zach It is true!
I did see a cat using identi.ca!" and attach a picture of my cat at the
keyboard, the message will be sent as I expected, but the picture will not
be attached.

This problem impacts email more, I think.

Can you think of a way we can have commands be able to process attachments?

Yeah, I was talking with....... You? Zach? Both? somebody ;) the other day -- a big chunk of the notice posting code needs to be refactored; there's duplication of a lot of steps including attachment processing in several different channels, and there's a number of places where not all the steps get run.

Possibly encapsulating all the message processing steps into Command might make sense so they're available easily to all commands in all communication channels.

Each channel (web, mail, xmpp, etc) can provide a file attachment handler to grab the actual file from whatever source ($_FILES for web, mail attachments, etc), without duplicating all the surrounding code.

-- brion vibber (status.net)
_______________________________________________
StatusNet-dev mailing list
[email protected]
http://lists.status.net/mailman/listinfo/statusnet-dev

Reply via email to