I am confused.<div><br></div><div>I have some changes to MailMessage (a Pharo class) and WAEmailMessage (a Seaside class) and an extension to MailMessage (the method MailMessage&gt;&gt;seasideEmailMessage:from:to:subject:) that I would like to contribute. These changes allow multi-part MIME messages to be created and sent from a Seaside web applicationfo -- r example messages with an HTML part and a plain text part.</div>
<div><br></div><div>Following the instructions at�<a href="http://code.google.com/p/pharo/wiki/HowToContribute">http://code.google.com/p/pharo/wiki/HowToContribute</a>, I am installing my changes into Pharo 1.2 in preparation for creating a Monticello package for PharoInbox. Here are my problems:</div>
<div><br></div><div>1. One of the steps is &quot;File in your changes and test.&quot; I have test classes derived from Sunit. Pharo 1.2 core doesn&#39;t seem to include Sunit. Should I test manually and not include the Sunit tests in the package I submit?</div>
<div><br></div><div>2. I assume the MailMessage extension described above belongs in a Seaside update. Is this true?</div><div><br></div><div>3. The Seaside changes cannot load without first loading the Pharo changes since the multi-part message is created using Pharo&#39;s MailMessage . How is this kind of dependency handled? Should I wait for a Seaside distribution on a version of Pharo that includes my changes before submitting the Seaside package? It seems like this could take a long time.</div>
<div><br></div><div>4. Should I make this a Seaside-only package and extend Pharo&#39;s MailMessage in that package?</div><div><br></div><div>Any advice will be appreciated.</div><div><br></div><div>Cheers,</div><div>TF</div>
<div><br></div><div><br></div><meta http-equiv="content-type" content="text/html; charset=utf-8">