Author Topic: EOS New Mail Management Class - Nomad  (Read 1238 times)

0 Members and 1 Guest are viewing this topic.

David M. Graham

  • Administrator
  • Sr. Member
  • *****
  • Offline Offline
  • Posts: 380
  • Karma: 12
    • View Profile
    • osCommerce University
Re: EOS New Mail Management Class - Nomad
« Reply #2 on: November 19, 2008, 07:39:32 AM »
Recently, I sent my integration of the English language translation of the Nomad Mime Mail class to its author -  .

He has accepted this work as a contribution to the Nomad project, and it may be seen at his website using this link:

http://www.developarts.com/nomad_mimemail_doc_en


The Nomad Mime Mail Class Project pages can be found at:

http://www.developarts.com/nomad_mimemail

and on www.phpclasses.org here:

Nomad Mime Mail Class Project on phpclasses.org


I'm very happy to see a successful start to meeting our commitment to participate in Open Source development in a collaborative way.

David
« Last Edit: November 25, 2008, 01:49:31 PM by inetbiz »

David M. Graham

  • Administrator
  • Sr. Member
  • *****
  • Offline Offline
  • Posts: 380
  • Karma: 12
    • View Profile
    • osCommerce University
EOS New Mail Management Class - Nomad
« Reply #1 on: November 05, 2008, 09:46:42 AM »
In the course of clearing the way for discount management and other changes, we find it necessary to move the email management into more centralized position in the code structure. 

This offers us an opportunity to update the email management functionality at the lowest levels of the code, and we are doing so.  Changes to the distribution license by the original author make it advisable to replace the aging osCommerce email class. Our choice is the Nomad Mime Mail class.

Among the activities we will be doing as we roll this out is updating the translated English documentation to improve the vernacular a bit, and rolling it back into their projects HTML format.  This will be contributed back to them and made available to our development community.

We expect to continue in this manner, making sure that component documentation is readily available to promote consistent usage of API features by all developers.  As I get the documentation rolled out, I'll post more here.