Re: MHonArc v2.5.4 Released

On May 4, 2002 at 12:30, "Edward Wildgoose" wrote: > > A solution is to leverage server-side include (SSI) capabilities and > > customizing the page layout via MHonArc resources. I.e. I can get > > something like your demo without any coding. > Ohh, what a clever idea. I hadn't thought of tha

Re: MHonArc v2.5.4 Released

> > Hmmm. From this, it appears that the message pages are really not needed. > What you really want is just one "big" page containing the contents > of your messages. > Yep, although it is quite nice to be able to have a link to just the story, as well as the whole page. A nice-to-have though

Re: MHonArc v2.5.4 Released

(I'm cc the list since I think my response may be helpful to others. I hope you do not mind since the thread started on the list.) On May 4, 2002 at 00:05, "Edward Wildgoose" wrote: > > BTW, an alternative approach is to never store message preview data > > in the database but to always extrac

Re: MHonArc v2.5.4 Released

On May 3, 2002 at 09:06, "Edward Wildgoose" wrote: > Just an idea with regards to the previous threads. Would it be > sensible/efficient/possible to use this to expand the $NOTE$ automatically > to include the body of each email? Ah, you caught the motivation behind the additional API callbacks

Re: MHonArc v2.5.4 Released

Just an idea with regards to the previous threads. Would it be sensible/efficient/possible to use this to expand the $NOTE$ automatically to include the body of each email? Is this the right way to go about it, or is it best for me to try and work this modification into the code elsewhere? Ed

MHonArc v2.5.4 Released

* Added more API callback functions: $CBDbPreLoad Right before database file is loaded. $CBDbPreSave Right before database file is written. $CBDbSave When data has been written. $CBRawMessageBodyRead After message body is