| 
     
      
      
      From: Nick C. <ni...@cl...> - 2003-02-06 23:08:00
      
     
   | 
On Thu, Feb 06, 2003 at 11:59:49AM -0500, Wizard wrote: > I was hoping to include NMSTreq.pm from Nick's TFMail for the email > notification feature of NMSBoard. There's nothing about emails in NMStreq - it's a CGI.pm wrapper, a config file reader and a templating engine all munged into a single module. > Should I include it in my libs structure or is there some way in which we > can create a symlink in the CVS tree? For now, I think, copy and paste the bits you want. Once everything has settled down a bit we can look at factoring out a common superclass if there's a lot of duplicated code. > Where should it be? > CGI::NMS::NMSTreq? I don't think NMSTreq should go in CGI::NMS, it's too much of a mixture of things. I would move the bits of it you want to CGI::NMS::Script::NMSBoard::SomeThing or suchlike. > CGI::NMS::Scripts::Common::NMSTreq? To me, that says it's part of the Common.pl CGI script. > CGI::NMS::Scripts::NMSTreq? ... and that would be for the NMSTreq.pl CGI script. > I may also include some other common stuff as well, but I have to look > first. If I do find other code that I can steal, Should I create a > package? a module? just paste it? I would just copy and paste for now, see what you end up with. -- Nick  |