BTW, does NeoBard need a MailHost - or does it have it's own SMTP functionality? It hasn't asked me for a server, and I can't see how it could know /which/ MailHost to use...
For all practicall reasons, I couldn't think of a situation where you'll access a remote SMTP server for mail services. So, NeoBoard comes with its own Mailer class which defaults to localhost, port 25. You don't need a Mailhost. Works only on a Unix platform, though. And my bad, up to 0.9.1, NeoBoard lacks the sendmail() method. Its parent project NeoPortal defines that method far up the hierarchy and I forgot to re-define it in the public version of NeoBoard. NeoPortal gets its SMTP host/port number from a getMailHost() method defaulting to localhost/25 in their absence. I'll re-implement it in the next version of NeoBoard to give options to users: Zope Mailhost or default localhost/25. Download version 0.9.2 in the meantime, a quick patch for that missing sendmail() method.
However, there are a few things that I /would/ like to be able to "get at", other than the raw message objects (I'd like to think I could work with these programmatically if not interactively, BTW). The most important is the document which "holds the board" - ideally, if this document were a DTML Method (Like Squishdot, which I have some experience with), I could then call this from my existing (DTML) page design...
Well, that issue I already discussed with another user on one of the boards I run at neoboard.net. NeoBoard's DTML's reside in the folder 'dtml' and can't be edited thru ZMI. I just didn't want an innocent user to break the product by directly editing DTML's. But, guess you guys really want to get at the DTML's. I'll give you options on this one two in the next version. Thanx for the feedback.
That bit I don't get - could you expand on that, please?
It's not recommended, but if you really need it, you can access a message object, say, "a_1" with the following URL assuming it's in a 'Test' board. http://yourhost/Test/a_1/manage That'll give you ZMI on that message object. But messing with message objects/external file objects directly might break the threading mechanism.
You seem to be coming along nicely <g> - I'm a stringer-togther of other's pearls, rather than a coder (oyster?), But I hope you have as much fun with it as I do.
Really, I came to love Zope. I spent months when I first wrote NeoBoard in Perl years back. Took a week porting it into PHP. And into Zope? Guess what? Took only two days! Zope had all I needed to make this product work. Everything was already there. I only brought ideas from NeoBoard PHP version, not a single line of code. Isn't that a miracle? Only Zope could have made it happen. For example, making threads work gives you a real headache when working in Perl or PHP. But, ZPublisher already gave me the solution before even I thought about the problem. I've never been happier coding anything:-) Regards, Wankyu Choi