Re: [Pharo-users] Postmark email library

[Stéphane Ducasse]

I did not get a minute to look at it.
Did you try on your side?

Stef
On Aug 30, 2013, at 1:51 PM, Stéphane Ducasse  wrote:

> 
> On Aug 30, 2013, at 9:45 AM, vmusulainen  wrote:
> 
>> Sure!
>> 
>> I use pharo 2.0 (21.0)
>> 
>> Attempt 1.
>> 
>> Use http://ss3.gemstone.com/ss/postmark.html at "Getting the code/Gofer"
>> 
>> Gofer new
>>   repository: 'http://ss3.gemstone.com/ss/postmark';
>>   package: 'ConfigurationOfPostMark';
>>   package: 'PostMark-Core';
>>   package: 'PostMark-Tests';
>>   load
> 
> this is the configurationOfPostmark that have the responsibility of loading 
> the other packages and projects it needs.
> I will try to have a look but on Smalltalkhub
> 
> Stef
> 
>> 
>> DoIt at workspace
>> 
>> Result: Expection "ByteString  doesNotUnderstand: #goferReferences"
>> 
>> Attempt 2.
>> 
>> Use http://ss3.gemstone.com/ss/postmark.html at "Getting the code/Monticello
>> Registration"
>> Add repository => select package "PostMark-Core-FrancoisStephany.11", press
>> "Load"
>> 
>> Result:
>> "This package depends on the following classes:
>> JsonObject
>> You must resolve these dependencies before you will be able to load these
>> definitions: 
>> PMEmail
>> addAttachment:content:contentType:
>> addAttachmentAndCompress:archiveName:
>> attachAndCompressFile:
>> attachFile:
>> 
>> Select Proceed to continue, or close this window to cancel the operation."
>> 
>> Attempt 3.
>> see http://ss3.gemstone.com/ss/postmark.html/Wiki
>> 
>> Gofer it
>> url: 'http://ss3.gemstone.com/ss/postmark';
>> package: 'ConfigurationOfPostMark';
>> load.
>> (Smalltalk at: #ConfigurationOfPostMark) project stableVersion load.
>> 
>> DoIt at workspace
>> 
>> Result: "The symbolic version #stable is not defined in
>> ConfigurationOfPostMark for the current platform."
>> 
>> 
>> 
>> --
>> View this message in context: 
>> http://forum.world.st/Postmark-email-library-tp4254680p4705729.html
>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>> 
> 
> 

Re: [Pharo-users] Postmark email library

[vmusulainen]

I try loading from smalltalkhub.com with same results.

Ant at smalltalkhub.com wrong link to external site 
(http://articles.tulipemoutarde.be/send-email-from-pharo-with-postmark) -
wrong
http://tulipemoutarde.be/2011/12/29/send-email-from-pharo-with-postmark.html
- right



--
View this message in context: 
http://forum.world.st/Postmark-email-library-tp4254680p4705887.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] Postmark email library

[Stéphane Ducasse]

I will give a try later.
And see how we can fix it.
Did you try to load the JSON configuration first?

Stef

On Aug 31, 2013, at 9:47 AM, vmusulainen  wrote:

> I try loading from smalltalkhub.com with same results.
> 
> Ant at smalltalkhub.com wrong link to external site 
> (http://articles.tulipemoutarde.be/send-email-from-pharo-with-postmark) -
> wrong
> http://tulipemoutarde.be/2011/12/29/send-email-from-pharo-with-postmark.html
> - right
> 
> 
> 
> --
> View this message in context: 
> http://forum.world.st/Postmark-email-library-tp4254680p4705887.html
> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
> 

Re: [Pharo-users] Postmark email library

[Marcus Denker]

On Aug 31, 2013, at 11:14 AM, Stéphane Ducasse  
wrote:

> I will give a try later.
> And see how we can fix it.
> Did you try to load the JSON configuration first?
> 

We are using PostMark in the ESUG registration app… so it should work.

You need to load JSON, though.

(we should update the config)

Postmark is actually *very* *very* interesting for sending mail… you outsource
all the haste of being blacklisted and things like that.

The downside is that it costs money: $1.50 per 10.000 mails.

> Stef
> 
> On Aug 31, 2013, at 9:47 AM, vmusulainen  wrote:
> 
>> I try loading from smalltalkhub.com with same results.
>> 
>> Ant at smalltalkhub.com wrong link to external site 
>> (http://articles.tulipemoutarde.be/send-email-from-pharo-with-postmark) -
>> wrong
>> http://tulipemoutarde.be/2011/12/29/send-email-from-pharo-with-postmark.html
>> - right
>> 
>> 
>> 
>> --
>> View this message in context: 
>> http://forum.world.st/Postmark-email-library-tp4254680p4705887.html
>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>> 
> 
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [Pharo-users] voyage/mongo randomly wrong OIDs

[Sabine Knöfel]

Hi Esteban,

yes, Mongo is not very communicative ;-)

I replaced OID>>nextOID  with my own RKAOIDGenerator

nextOID
^self value: (RKAOIDGenerator getNextOID)

instead of

nextOID
^self value: (UUIDGenerator default makeSeed)


RKAOIDGenerator uses Time>>primMillisecondClock at startup and adds +1 each
time I getNextOID as you suggested.

This works fine. It seems to be much much much faster than the existing
solution.

[4000 timesRepeat: [UUIDGenerator default makeSeed]] timeToRun==>> 5817
[4000 timesRepeat: [RKAOIDGenerator getNextOID]] timeToRun ==> 1 (!!)

Perhaps a solution like this would be a better solution for all because it
is faster and guarantees unique IDs?

Sabine





On Fri, Aug 30, 2013 at 5:58 PM, EstebanLM [via Smalltalk] <
ml-node+s1294792n4705827...@n4.nabble.com> wrote:

> Hi,
>
> One idea (not sure if it will work)
>
> You can take
>
> Time primUTCMicrosecondsClock
>
> when system start, then increase it sequentially.
> most probably that will ensure uniqueness while providing fast ids.
>
> but of course, that depends, you need to check in your system.
>
> I'm thinking on provide different ID generators for Voyage, and let people
> plug what is more convenient for them.
>
> (all of this happens because, unlike other db drivers, mongo does not
> answer the inserted id :( )
>
> Esteban
>
> On Aug 30, 2013, at 5:41 PM, Sabine Knöfel <[hidden 
> email]>
> wrote:
>
> > So, I will wait and till then, use the solution of Jan.
> > Thank you, Jan for the file in.
> > Sabine
> >
> >
> >
> > --
> > View this message in context:
> http://forum.world.st/voyage-mongo-randomly-wrong-OIDs-tp4705396p4705821.html
>
> > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
> >
>
>
>
>
> --
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://forum.world.st/voyage-mongo-randomly-wrong-OIDs-tp4705396p4705827.html
>  To unsubscribe from voyage/mongo randomly wrong OIDs, click 
> here
> .
> NAML
>




--
View this message in context: 
http://forum.world.st/voyage-mongo-randomly-wrong-OIDs-tp4705396p4705898.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] Postmark email library

[vmusulainen]

Stéphane Ducasse wrote
> Did you try to load the JSON configuration first?

Yep, but which package consist need classes? I ask it at first post.


Wow, I found JSON package at smalltalkhub.com.

I first load JSON package from smalltalkhub.com and postmark package
successfully loaded.
Good, thank you.

I resume my notes:

1. Wrong reference to external site with example of usage postmark
http://articles.tulipemoutarde.be/send-email-from-pharo-with-postmark -
incorrect
http://tulipemoutarde.be/2011/12/29/send-email-from-pharo-with-postmark.html
- correct

2. At smalltalkhub.com exists two projects 
a. PharoExtras/Postmark - correct project with packages
b. PharoExtras/postmark - emp[ty project without packages

I understand that you have little time, can I do something to help fix it?

Vladimir Musulainen




--
View this message in context: 
http://forum.world.st/Postmark-email-library-tp4254680p4705900.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] Postmark email library

[vmusulainen]

Marcus Denker-4 wrote
> Postmark is actually *very* *very* interesting for sending mail… you
> outsource
> all the haste of being blacklisted and things like that.

Yes, you are right.
I write shop engine and should use postmark for sending order to customers
and managers. 



--
View this message in context: 
http://forum.world.st/Postmark-email-library-tp4254680p4705902.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] Postmark email library

[Stéphane Ducasse]

I will have a look and update the configuration. 

On Aug 31, 2013, at 11:23 AM, Marcus Denker  wrote:

> 
> On Aug 31, 2013, at 11:14 AM, Stéphane Ducasse  
> wrote:
> 
>> I will give a try later.
>> And see how we can fix it.
>> Did you try to load the JSON configuration first?
>> 
> 
> We are using PostMark in the ESUG registration app… so it should work.
> 
> You need to load JSON, though.
> 
> (we should update the config)
> 
> Postmark is actually *very* *very* interesting for sending mail… you outsource
> all the haste of being blacklisted and things like that.
> 
> The downside is that it costs money: $1.50 per 10.000 mails.
> 
>> Stef
>> 
>> On Aug 31, 2013, at 9:47 AM, vmusulainen  wrote:
>> 
>>> I try loading from smalltalkhub.com with same results.
>>> 
>>> Ant at smalltalkhub.com wrong link to external site 
>>> (http://articles.tulipemoutarde.be/send-email-from-pharo-with-postmark) -
>>> wrong
>>> http://tulipemoutarde.be/2011/12/29/send-email-from-pharo-with-postmark.html
>>> - right
>>> 
>>> 
>>> 
>>> --
>>> View this message in context: 
>>> http://forum.world.st/Postmark-email-library-tp4254680p4705887.html
>>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>>> 
>> 
>> 
> 

Re: [Pharo-users] voyage/mongo randomly wrong OIDs

[Stéphane Ducasse]

Sabine 
what we could do is to propose a "subclass of UUID" and to group several UUID 
generators.
Like that with a couple of classes, we could get a better eco system where 
people can pick the one they want.

stef

On Aug 31, 2013, at 11:49 AM, Sabine Knöfel  wrote:

> Hi Esteban,
> 
> yes, Mongo is not very communicative ;-)
> 
> I replaced OID>>nextOID  with my own RKAOIDGenerator 
> 
> nextOID
>   ^self value: (RKAOIDGenerator getNextOID)
> 
> instead of
> 
> nextOID
>   ^self value: (UUIDGenerator default makeSeed)
> 
> 
> RKAOIDGenerator uses Time>>primMillisecondClock at startup and adds +1 each 
> time I getNextOID as you suggested.
> 
> This works fine. It seems to be much much much faster than the existing 
> solution.
> 
> [4000 timesRepeat: [UUIDGenerator default makeSeed]] timeToRun==>> 5817
> [4000 timesRepeat: [RKAOIDGenerator getNextOID]] timeToRun ==> 1 (!!)
> 
> Perhaps a solution like this would be a better solution for all because it is 
> faster and guarantees unique IDs?
> 
> Sabine
> 
> 
> 
> 
> 
> On Fri, Aug 30, 2013 at 5:58 PM, EstebanLM [via Smalltalk] <[hidden email]> 
> wrote:
> Hi, 
> 
> One idea (not sure if it will work) 
> 
> You can take 
> 
> Time primUTCMicrosecondsClock 
> 
> when system start, then increase it sequentially. 
> most probably that will ensure uniqueness while providing fast ids. 
> 
> but of course, that depends, you need to check in your system. 
> 
> I'm thinking on provide different ID generators for Voyage, and let people 
> plug what is more convenient for them. 
> 
> (all of this happens because, unlike other db drivers, mongo does not answer 
> the inserted id :( ) 
> 
> Esteban 
> 
> On Aug 30, 2013, at 5:41 PM, Sabine Knöfel <[hidden email]> wrote: 
> 
> > So, I will wait and till then, use the solution of Jan. 
> > Thank you, Jan for the file in. 
> > Sabine 
> > 
> > 
> > 
> > -- 
> > View this message in context: 
> > http://forum.world.st/voyage-mongo-randomly-wrong-OIDs-tp4705396p4705821.html
> 
> > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. 
> >
> 
> 
> 
> 
> If you reply to this email, your message will be added to the discussion 
> below:
> http://forum.world.st/voyage-mongo-randomly-wrong-OIDs-tp4705396p4705827.html
> To unsubscribe from voyage/mongo randomly wrong OIDs, click here.
> NAML
> 
> 
> View this message in context: Re: voyage/mongo randomly wrong OIDs
> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] Postmark email library

[Stéphane Ducasse]

> Stéphane Ducasse wrote
>> Did you try to load the JSON configuration first?
> 
> Yep, but which package consist need classes? I ask it at first post.
> 
> 
> Wow, I found JSON package at smalltalkhub.com.
> 
> I first load JSON package from smalltalkhub.com and postmark package
> successfully loaded.
> Good, thank you.


I will fix the configruation and ask you to try.

> 
> I resume my notes:
> 
> 1. Wrong reference to external site with example of usage postmark
> http://articles.tulipemoutarde.be/send-email-from-pharo-with-postmark -
> incorrect
> http://tulipemoutarde.be/2011/12/29/send-email-from-pharo-with-postmark.html
> - correct
> 
> 2. At smalltalkhub.com exists two projects 
> a. PharoExtras/Postmark - correct project with packages
> b. PharoExtras/postmark - emp[ty project without packages
> 
> I understand that you have little time, can I do something to help fix it?
To help me please read the metacello chapter!
of Pharo By example two (deep into pharo) 
so that next time you can manage/ maintain/extend the configruation of  
Postmark.

I do not need postmark but I want it to be available for people. Now this is 
better if people needed it can take of what they use. 

Stef

> 
> Vladimir Musulainen
> 
> 
> 
> 
> --
> View this message in context: 
> http://forum.world.st/Postmark-email-library-tp4254680p4705900.html
> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
> 

Re: [Pharo-users] Postmark email library

[vmusulainen]

Stéphane Ducasse wrote
> I will fix the configruation and ask you to try.

I found another dependency:

Method PMInterface>>send: uses class GRPharoUtf8Codec. This class exists in
package "Grease-Pharo-Core" (Seaside framework). 





--
View this message in context: 
http://forum.world.st/Postmark-email-library-tp4254680p4705915.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] Postmark email library

[Stéphane Ducasse]

thanks!
misdeclaring dependencies is the source of future hell :)
I just deleted the wrong repository and I'm having a look now.

Stef

On Aug 31, 2013, at 1:55 PM, vmusulainen  wrote:

> Stéphane Ducasse wrote
>> I will fix the configruation and ask you to try.
> 
> I found another dependency:
> 
> Method PMInterface>>send: uses class GRPharoUtf8Codec. This class exists in
> package "Grease-Pharo-Core" (Seaside framework). 
> 
> 
> 
> 
> 
> --
> View this message in context: 
> http://forum.world.st/Postmark-email-library-tp4254680p4705915.html
> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
> 

Re: [Pharo-users] Postmark email library

[Stéphane Ducasse]

Grease is handled by the configuration.
So this is already that :)


> thanks!
> misdeclaring dependencies is the source of future hell :)
> I just deleted the wrong repository and I'm having a look now.
> 
> Stef
> 
> On Aug 31, 2013, at 1:55 PM, vmusulainen  wrote:
> 
>> Stéphane Ducasse wrote
>>> I will fix the configruation and ask you to try.
>> 
>> I found another dependency:
>> 
>> Method PMInterface>>send: uses class GRPharoUtf8Codec. This class exists in
>> package "Grease-Pharo-Core" (Seaside framework). 
>> 
>> 
>> 
>> 
>> 
>> --
>> View this message in context: 
>> http://forum.world.st/Postmark-email-library-tp4254680p4705915.html
>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>> 
> 
> 

Re: [Pharo-users] Postmark email library

[Stéphane Ducasse]

So i worked and now can you try on a Pharo2.0 image the following




Gofer new
repository: 'http://smalltalkhub.com/mc/PharoExtras/Postmark/main' ;
package: 'ConfigurationOfPostMark';
load.


(ConfigurationOfPostMark project version: '1.0') load: 'Tests'



Stef

Re: [Pharo-users] voyage/mongo randomly wrong OIDs

[Sven Van Caekenberghe]

On 31 Aug 2013, at 13:47, Stéphane Ducasse  wrote:

> Sabine 
> what we could do is to propose a "subclass of UUID" and to group several UUID 
> generators.
> Like that with a couple of classes, we could get a better eco system where 
> people can pick the one they want.
> 
> stef

I just made my own, called NeoUUIDGenerator, 
http://www.smalltalkhub.com/#!/~SvenVanCaekenberghe/Neo/packages/Neo-UUID

@Sabine

IMHO what I think a local counter does not, is give you uniques over different 
machines, images, instances - that is why there is also the concept of node 
identification.

In my implementation I combine the millisecond clock, a small random number, a 
counter and a node id. The node id is based on several elements, it should be 
different when running multiple images.

This is a hack, not something that I can prove mathematically. But it can't be 
worse than pure random. I think the speed is also acceptable:

| generator |
generator := NeoUUIDGenerator new.
[ generator next ] bench. '408,000 per second.'

| generator |
generator := UUIDGenerator new.
[ generator generateBytes: UUID nilUUID forVersion: 4 ] bench. '13,300 per 
second.'

Sven

> On Aug 31, 2013, at 11:49 AM, Sabine Knöfel  wrote:
> 
>> Hi Esteban,
>> 
>> yes, Mongo is not very communicative ;-)
>> 
>> I replaced OID>>nextOID  with my own RKAOIDGenerator 
>> 
>> nextOID
>>  ^self value: (RKAOIDGenerator getNextOID)
>> 
>> instead of
>> 
>> nextOID
>>  ^self value: (UUIDGenerator default makeSeed)
>> 
>> 
>> RKAOIDGenerator uses Time>>primMillisecondClock at startup and adds +1 each 
>> time I getNextOID as you suggested.
>> 
>> This works fine. It seems to be much much much faster than the existing 
>> solution.
>> 
>> [4000 timesRepeat: [UUIDGenerator default makeSeed]] timeToRun==>> 5817
>> [4000 timesRepeat: [RKAOIDGenerator getNextOID]] timeToRun ==> 1 (!!)
>> 
>> Perhaps a solution like this would be a better solution for all because it 
>> is faster and guarantees unique IDs?
>> 
>> Sabine
>> 
>> 
>> 
>> 
>> 
>> On Fri, Aug 30, 2013 at 5:58 PM, EstebanLM [via Smalltalk] <[hidden email]> 
>> wrote:
>> Hi, 
>> 
>> One idea (not sure if it will work) 
>> 
>> You can take 
>> 
>> Time primUTCMicrosecondsClock 
>> 
>> when system start, then increase it sequentially. 
>> most probably that will ensure uniqueness while providing fast ids. 
>> 
>> but of course, that depends, you need to check in your system. 
>> 
>> I'm thinking on provide different ID generators for Voyage, and let people 
>> plug what is more convenient for them. 
>> 
>> (all of this happens because, unlike other db drivers, mongo does not answer 
>> the inserted id :( ) 
>> 
>> Esteban 
>> 
>> On Aug 30, 2013, at 5:41 PM, Sabine Knöfel <[hidden email]> wrote: 
>> 
>> > So, I will wait and till then, use the solution of Jan. 
>> > Thank you, Jan for the file in. 
>> > Sabine 
>> > 
>> > 
>> > 
>> > -- 
>> > View this message in context: 
>> > http://forum.world.st/voyage-mongo-randomly-wrong-OIDs-tp4705396p4705821.html
>> 
>> > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. 
>> >
>> 
>> 
>> 
>> 
>> If you reply to this email, your message will be added to the discussion 
>> below:
>> http://forum.world.st/voyage-mongo-randomly-wrong-OIDs-tp4705396p4705827.html
>> To unsubscribe from voyage/mongo randomly wrong OIDs, click here.
>> NAML
>> 
>> 
>> View this message in context: Re: voyage/mongo randomly wrong OIDs
>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
> 

Re: [Pharo-users] Postmark email library

[vmusulainen]

Stéphane Ducasse wrote
> Gofer new
>   repository: 'http://smalltalkhub.com/mc/PharoExtras/Postmark/main' ;
>   package: 'ConfigurationOfPostMark';
>   load.
> (ConfigurationOfPostMark project version: '1.0') load: 'Tests'


MessageNotUnderstood: ByteString>>goferReferences



--
View this message in context: 
http://forum.world.st/Postmark-email-library-tp4254680p4705934.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] Postmark email library

[Stéphane Ducasse]

> Gofer new
>   url: 'http://smalltalkhub.com/mc/PharoExtras/Postmark/main' ;
>   package: 'ConfigurationOfPostMark';
>   load.
> (ConfigurationOfPostMark project version: '1.0') load: 'Tests'

Stef

Re: [Pharo-users] Voyage: image freeze/VOMongoError: Lazy reference not found

[Esteban A. Maringolo]

I've been bitten by this too.
This is when the "image" concept get counterproductive if you didn't
commit all your code changes. :-/

Esteban A. Maringolo

Re: [Pharo-users] Voyage: image freeze/VOMongoError: Lazy reference not found

[Sabine Knöfel]

Hi Esteban,

til now, it did not come back to me.
Can you reproduce it with a fresh image?
Btw I am saving my image now each hour or so...

Sabine


On Sat, Aug 31, 2013 at 5:46 PM, Esteban A. Maringolo [via Smalltalk] <
ml-node+s1294792n4705953...@n4.nabble.com> wrote:

> I've been bitten by this too.
> This is when the "image" concept get counterproductive if you didn't
> commit all your code changes. :-/
>
> Esteban A. Maringolo
>
>
>
> --
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://forum.world.st/Voyage-image-freeze-VOMongoError-Lazy-reference-not-found-tp4703739p4705953.html
>  To unsubscribe from Voyage: image freeze/VOMongoError: Lazy reference not
> found, click 
> here
> .
> NAML
>




--
View this message in context: 
http://forum.world.st/Voyage-image-freeze-VOMongoError-Lazy-reference-not-found-tp4703739p4705960.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] Voyage: image freeze/VOMongoError: Lazy reference not found

[Esteban A. Maringolo]

2013/8/31 Sabine Knöfel :
> Hi Esteban,
>
> til now, it did not come back to me.
> Can you reproduce it with a fresh image?

The image freezed, but fortunately with a LOT of patience I was able
to type a character every once in a while. So I could write an
smalltalk expression that after being evaluated opened a debugger and
caused the image to get responsive again.

The expression was a last resort in order to "cause" another error
that could give me the control back.

VOLazyProxy allInstances do: [:each | each become: String new ]

It worked.

> Btw I am saving my image now each hour or so...

I'm not used to do it, I trust in the changes file, the problem is
that I saved the image with the offending proxy.

The problem was a modification of a document in a collection. I did a
mongo upsert that changed it, and apparently Voyage didn't know how to
handle it.

Regards!

Re: [Pharo-users] Postmark email library

[vmusulainen]

It's work fine!

Tested on clean image of pharo 2.0.

Thank you!



--
View this message in context: 
http://forum.world.st/Postmark-email-library-tp4254680p4705969.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] Postmark email library

[Stéphane Ducasse]

> It's work fine!

Excellent.

> Tested on clean image of pharo 2.0.
> 
> Thank you!

Now you have to read the metacello chapter ;D and have success coding in Pharo.
And if you see glitches or space for improvements in Postmark, please do not 
hesitate.

> 
> --
> View this message in context: 
> http://forum.world.st/Postmark-email-library-tp4254680p4705969.html
> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>