commit: horde problem.php horde/docs CHANGES imp compose.php mailbox.php message.php imp/lib IMP.php horde/lib MIME.php horde/lib/MIME Message.php Structure.php

[chuck@horde.org]

chuck       2001/01/08 14:52:43 PST

  Modified files:
    .                    problem.php 
    docs                 CHANGES 
    .                    compose.php mailbox.php message.php 
    lib                  IMP.php 
    lib                  MIME.php 
  Added files:
    lib/MIME             Message.php Structure.php 
  Log:
  This should more or less complete the MIME revamp, at least with respect to
  the Horde code. There's probably cleanup that could still happen, but most
  of it is contained in IMP now (which is good). The Horde MIME classes have
  one dependancy on imap_rfc822_write_address(), which will be fixed once we
  have Mail_RFC822::writeAddress(). Other than that there are no references to
  IMP or imap or the imap functions in them.
  
  I've broken out MIME_Structure (for dealing with the structure of MIME
  messages) and MIME_Message (for creating MIME emails). MIME_Part lives
  inside of MIME/Message.php, since it's pretty intrinsically tied to
  MIME_Message::.
  
  If we wanted to, we could look into having MIME_Structure return an array of
  MIME_Part:: objects instead of our custom hashes. This would be more robust
  and organized, but would probably entail breaking out MIME_Part and making
  it it's own file (which would be included by both MIME_Message and
  MIME_Structure). Actually, the more I think about it, the more this sounds
  like a decent idea... what do people think?
  
  Revision  Changes    Path
  2.52      +8 -9      horde/problem.php
  1.102     +3 -0      horde/docs/CHANGES
  2.246     +69 -65    imp/compose.php
  2.233     +10 -10    imp/mailbox.php
  2.187     +6 -5      imp/message.php
  1.117     +14 -10    imp/lib/IMP.php
  1.51      +3 -3      horde/lib/MIME.php