I Want to unsuscribeMSN Messenger : discutez en direct avec vos amis ! 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: http://mojo.skazat.com/cgi-bin/dada/mail.cgi/archive/dadadev ...Continue Reading

Re: [dadadev] RE: CSS height/alignment bug Yep,   definitely better....   Alfred *Van:* Shane Clintberg [mailto:shaneclintberg@PROTECTED] *Verzonden:* dinsdag 26 juli 2005 15:50*Aan:* alfred@PROTECTED*Onderwerp:* [dadadev] RE: CSS height/alignment bug Alfred wrote: I'm not sure this is an CSS issue, but can something be done about the misalignment of the fields on the main [admin] screen I've solved half the problem: the vertical alignment is fixed in rev. 1.8 of "list_popup_lo ...Continue Reading

RE: [dadadev] any and all CSS bugs, suggestions and snippets welcomed Alfred wrote:   I'm not sure this is an CSS issue, but can something be done about the misalignment of the fields on the main [admin] screen   I've solved half the problem: the vertical alignment is fixed in rev. 1.8 of "list_popup_login_form.tmpl", available at: <http://cvs.sourceforge.net/viewcvs.py/mojomail/dada_mail_stable/dada/DADA/Template/templates/list_popup_login_form.tmpl> Post: mailto:dadadev@PROTECTED Unsu ...Continue Reading

RE: [dadadev] any and all CSS bugs, suggestions and snippets welcomed Yup, this is exactly the sort of thing I'm looking for. Thanks!   Keep 'em coming if you got 'em,   -S. ----- Original Message ----- *From:* Alfred Vink I'm not sure this is an CSS issue, but can something be done about the misalignment of the fields on the main screen. If the 2 fields and the button would have the same height and be aligned vertically it would look much better in Post: mailto:dadad ...Continue Reading

> I quickly put together some coding style docs up in the "developers" > directory in CVS. Great idea -- thanks very much for this! I'll take a closer look at the doc soon...but based on just a quick glance, here are my initial, very fleeting thoughts: * Yup, DEV -- or maybe nothing at all until we're *sure* we need it -- is much better. [FYI: My reason for using DEVCOMMENT personally is that it's a pain to type, it's redundant, and it's more bloated than necessary...which *ensures* that I only use i ...Continue Reading

> Although a hack, doesn't IE allow you to put conditional statement  > comments in css?   Yup, ...but it's a particularly ugly and wordy hack, so I'd personally hesitate to use it for a non-essential purpose in a default stylesheet. Here's roughly what it would look like...   input { border:1px solid black; } , if applied only to text and password controls, would end up reading: /* for CSS3 (NN, FF, Moz): */ input[type="text"], input[type="password"] {    ...Continue Reading

I quickly put together some coding style docs up in the "developers" directory in CVS. It'll show up in a few hours here: http://cvs.sourceforge.net/viewcvs.py/mojomail/dada_mail_stable/ dada/extras/developers/ And I've copied it below - only a skeleton at the moment: NAME Programming Code Styling for Dada Mail! DESCRIPTION This document is to help in understanding how Dada Mail is written. =pod Perl All code must run under the -T (taint) flag. xHTML Must be valid CSS Must be valid Java ...Continue Reading

Justin wrote: > I made some slight > changes to the default_css.css file and didn't commit these changes. > Now, when I update Dada Mail from CVS, it won't update this file >This type of issue is bound to happen a > lot as we start working on the same files at the same time. As you know, I'm new to this CVS thing myself...but Sourceforge's introductory info suggests that during *regular* use, conflicts are actually rarer than one might first expect, ...and that, with its robust conflict-resolution too ...Continue Reading

Thus sayeth Alfred Vink, at 4:15 PM on 7/25/05: >http://www.alfsoft.com/cgi-bin/dada/mail.cgi?flavor=admin Ah, so the problem is just with the admin screen. ...Continue Reading

> Does this sound like a good commenting convention to add into our > devs' > "best practices"? Or is it better left as just my thing, ...or left > out > altogether? That's fine I think, although most comments in the code are going to be for developers, so it may be redundant: It may be easier to recognize that a comment, *is* a comment, and then state what it's for (optionally) For example, I've also started to use the, "TODO" comment, for things I haven't quite finished ...Continue Reading