July 24th 2006 PDT
That sounds good, and would surely make it easier to read. On 24 Jul 2006 07:21:06 -0000, Dada Mail (Justin Simoni)* < dada@PROTECTED> wrote:On Jul 23, 2006, at 9:55 AM, Joe Rizza wrote: --Post: <mailto:dadadev@PROTECTED>Unsubscribe: <http://mojo.skazat.com/cgi-bin/dada/mail.cgi/u/dadadev/ >List Information: <http://mojo.skazat.com/cgi-bin/dada/mail.cgi/list/dadadev>Archive: < ...Continue Reading
July 24th 2006 PDT
On 24 Jul 2006 07:17:13 -0000 "Dada Mail \(Justin Simoni\)" wrote: > On Jul 23, 2006, at 12:45 AM, Andreas Grau wrote: > > I vote for leaving it *in* the file. It is part of the documentation, > > OK - one vote for leaving it in :) :) > > > Personlly, I can't see why it should be difficult to wait with > > changing until one sees a =cut. People obviously read the file and then > > *spontaneously* decide to change the file. > > Well, the problem is, if you don' ...Continue Reading
July 24th 2006 PDT
On Jul 23, 2006, at 8:30 PM, wrote: ...Continue Reading
July 24th 2006 PDT
On Jul 23, 2006, at 9:55 AM, Joe Rizza wrote: ...Continue Reading
July 24th 2006 PDT
On Jul 23, 2006, at 12:45 AM, Andreas Grau wrote: > > I vote for leaving it *in* the file. It is part of the documentation, > pod's are invented and used for reason, and people wanting to dig > deeper into things need it. OK - one vote for leaving it in :) > Personlly, I can't see why it should be difficult to wait with > changing > until one sees a =cut. People obviously read the file and then > *spontaneously* decide to change the file. Difficult ? Yes ! Difficult > people ! ;-) Well, ...Continue Reading
July 24th 2006 PDT
Hello Everyone, 2.10.10 alpha 1 has been released. Here are the direct links to download: *tar.gz: http://prdownloads.sourceforge.net/mojomail/dada-2_10_10_alpha_1.tar.gz?download * zip: http://prdownloads.sourceforge.net/mojomail/dada-2_10_10_alpha_1.zip?download This release *only* contains bug fixes (described below) and contains no new features - making this a pretty solid, but fairly untested-in- the-wild release. I'm releasing it as an alpha not because I don't think it's a stable release, just that ...Continue Reading
July 23rd 2006 PDT
Here is a Logical idea which may make everyone happy My main concern is that the Bigger the page, the more cpu time is used even if most of the page is commented, the cpu still needs to read line by line to verify this. Please read ALL of this before commenting. What not have a seperate Online HTLM File (or even off-line HTML file) eg (V = version | X = version number) www.xyz.com/kb/DadaVX.htm Sort of like this www.xyz.com/kb/DadaV2-10-9.htm etc etc Then, IN THE act ...Continue Reading
July 23rd 2006 PDT
I have mixed feelings. It's great to have some comments in the code, but because it is somewhat distracting to have the "pod" tags in the file, I typically have the generated HTML sitting on the side when I am editing the file. I can see the advantage to putting the "pod" tags in the file, but when you generate a separate document, it should be written differently from the comments in the code. Would be nice if there was a way to have the best of both worlds, without the extra work. On 23 Jul 2006 0 ...Continue Reading
July 23rd 2006 PDT
Hi Justin and all, I vote for leaving it *in* the file. It is part of the documentation, pod's are invented and used for reason, and people wanting to dig deeper into things need it. As an alternative, you can probably deliver a stripped version *and* the full version, call them Config-dist-short.pm and Config-dist-long.pm and have people copy either to Config.pm Personlly, I can't see why it should be difficult to wait with changing until one sees a =cut. People obviously read the file and then *spontaneously* dec ...Continue Reading
July 22nd 2006 PDT
Hey guys/gals, I have an idea, I thought I'd first ask you all for an opinion about: Currently, the Config.pm file has embedded documentation, that gets run through a translator, to make pretty HTML files like this: http://mojo.skazat.com/support/documentation/Config.pm.html Here's more information on how/what the embedded docs are/work: http://www.ayni.com/perldoc/perl5.8.0/pod/perlpod.html Some people have voiced that the embedded documentation actually makes reading the Config.pm file *harder*, since it ...Continue Reading
Start a new thread, email: dadadev@dadamailproject.com
This is the developer discussion mailing list for Dada Mail.
If you are just looking for support Dada Mail, consult the message boards at:
https://forum.dadamailproject.com
Documentation for Dada Mail:
Specifically, see the Error FAQ:
https://dadamailproject.com/d/FAQ-errors.pod.html
To post to this list, send a message to:
mailto:dadadev@dadamailproject.com
All subscribers of this list may post to the list itself.
Topics that are welcome:
Dada Mail is on Github:
https://github.com/justingit/dada-mail/
If you would like to fork, branch, send over PRs, open up issues, etc.
This Privacy Policy is for this mailing list, and this mailing list only.
Email addresses collection through this mailing list are used explicitly to work within this email discussion list.
We only collect email addresses through our Closed-Loop Opt-In system.
We don't use your email address for any other purpose.
We won't be sharing your email address with any other entity.
Unsubscription can be done at any time. Please contact us at: justin@dadamailproject.com for any help regarding your subscription, including removal from the mailing list.
All mailing list messages sent from us will include a subscription removal link, which will allow you to remove yourself from this mailing list automatically, and permanently.
All consent to use your email address for any other purpose stated at the time of the mailing list subscription will also be revoked upon mailing list removal.