Hi!
Together with Ivan we have been looking for an easy way to send notifications. We first thought about sending email directly from Pharo, but apparently it is not easy to send email. Anyone has experience with this? We then thought about emitting twitts, but there is a need to authorize the client. Anyone has experience? Maybe producing a RSS could do the thing? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. |
> Together with Ivan we have been looking for an easy way to send notifications.
> We first thought about sending email directly from Pharo, but apparently it is not easy to send email. Anyone has experience with this? As long as your SMTP doesn't require encryption this is simple: Use MailSender that comes with every Pharo image. Seaside provides some objects on top of that, so that you don't have to assemble the message by hand. > We then thought about emitting twitts, but there is a need to authorize the client. Anyone has experience? Twitter requires OAuth, which requires an SSL capable HTTP client. > Maybe producing a RSS could do the thing? Again, simple with Seaside, but any XML library can do it. Lukas -- Lukas Renggli www.lukas-renggli.ch |
> As long as your SMTP doesn't require encryption this is simple: Use
> MailSender that comes with every Pharo image. Seaside provides some > objects on top of that, so that you don't have to assemble the message > by hand. Ok, we will check >> We then thought about emitting twitts, but there is a need to authorize the client. Anyone has experience? > > Twitter requires OAuth, which requires an SSL capable HTTP client. Does this mean this cannot be done now in Pharo? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. |
It can be done in Pharo using CloudforkSSO. See http://blog.doit.st Jan. > |
Thanks,
Alexandre On 6 May 2011, at 15:59, Jan van de Sandt wrote: > > On May 6, 2011 8:45 PM, "Alexandre Bergel" <[hidden email]> wrote: > > > > > As long as your SMTP doesn't require encryption this is simple: Use > > > MailSender that comes with every Pharo image. Seaside provides some > > > objects on top of that, so that you don't have to assemble the message > > > by hand. > > > > Ok, we will check > > > > >> We then thought about emitting twitts, but there is a need to authorize the client. Anyone has experience? > > > > > > Twitter requires OAuth, which requires an SSL capable HTTP client. > > > > Does this mean this cannot be done now in Pharo? > > It can be done in Pharo using CloudforkSSO. See http://blog.doit.st > > Jan. > > > > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. |
alex drop some notes in a file if you see what I mean :)
Stef On May 6, 2011, at 11:02 PM, Alexandre Bergel wrote: > Thanks, > > Alexandre > > > On 6 May 2011, at 15:59, Jan van de Sandt wrote: > >> >> On May 6, 2011 8:45 PM, "Alexandre Bergel" <[hidden email]> wrote: >>> >>>> As long as your SMTP doesn't require encryption this is simple: Use >>>> MailSender that comes with every Pharo image. Seaside provides some >>>> objects on top of that, so that you don't have to assemble the message >>>> by hand. >>> >>> Ok, we will check >>> >>>>> We then thought about emitting twitts, but there is a need to authorize the client. Anyone has experience? >>>> >>>> Twitter requires OAuth, which requires an SSL capable HTTP client. >>> >>> Does this mean this cannot be done now in Pharo? >> >> It can be done in Pharo using CloudforkSSO. See http://blog.doit.st >> >> Jan. >> >>> >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > |
Administrator
|
In reply to this post by abergel
I cleaned up Pharo's mail code a little. Issue 5051: [ENH]: Clean up Mail code http://code.google.com/p/pharo/issues/detail?id=5051 Added simpified API, for example: message := MailMessage from: 'sender@domain.com' to: { 'recipient@domain.com'. 'recipient2@domain.com' } about: 'Very Important Subject' asFollows: 'Hi, how are you?'. message sendOn: 'mail.domain.com'. Added some tests to MailMessage
Cheers,
Sean |
Cool :-)
Alexandre On 2 Dec 2011, at 16:08, Sean P. DeNigris wrote: > > Alexandre Bergel-7 wrote >> >> We first thought about sending email directly from Pharo, but apparently >> it is not easy to send email. > > I cleaned up Pharo's mail code a little. > > Issue 5051: [ENH]: Clean up Mail code > http://code.google.com/p/pharo/issues/detail?id=5051 > > Added simpified API, for example: > message := MailMessage > from: '[hidden email]' > to: { '[hidden email]'. '[hidden email]' } > about: 'Very Important Subject' > asFollows: 'Hi, how are you?'. > message sendOn: 'mail.domain.com'. > > Added some tests to MailMessage > > -- > View this message in context: http://forum.world.st/Send-a-notification-tp3503711p4148595.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. |
Free forum by Nabble | Edit this page |