I'm strongly against
- fields are prefixed with m
- parameters are prefixed with p
- local variables are prefixed with l
Just a personal opinion, I feel that it clutters the code.
Mathias
----- Original Message -----
From: "Fabrizio Giustina" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, August 31, 2003 12:11 AM
Subject: [displaytag-devel] goin on
Hi all
I'm back from holidays, ready to go on with the project. I'm happy to
see display09 has got some votes :)
So, first of all:
+1 on trimming the dev list, too many ghosts there
code conventions: I will post a doc with the code conventions I followed
and an associated checkstyle setting.
Actually the conventions are following the Sun standard plus:
- { is on a new line (c style)
- fields are prefixed with m
- parameters are prefixed with p
- local variables are prefixed with l
- lines are 120 chars wide
Well, these are my company standards, no problem on changing them if
there is a valid reason :)
+1/2 on backward compatible css: I think adding a way to globally
customize css classes names is anyway a good thing but it's better to
leave the new css classes by default.
Rename branch, beta tag, release:
I agree to rename the branch to display02, I don't have experience on
using beta tags on sourceforce, so I don't know if this could be a
problem.
Instead of renaming the actual branch, thought, I'd like to upload it as
a new module: I have just finished to migrate the build process to maven
and this has required to change a lot the current directory structure.
So rather then deleting and re-adding most of the files I think it's
better to remove the old module and start with a new -final- one.
I know it's not a good thing moving files or creating new modules
loosing he cvs history but maven is really great! I moved the
documentation to the maven xdoc format and fixed most of the problem
reported by the various reports (cycles detected by jdepend are fixed)
If there are no objections I will upload the new module TOMORROW. After
that, I will need some help to check, fix and improve the documentation
before a release: it should not take so much to complete it, let's plan
it in a couple of weeks?
fabrizio
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
displaytag-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
displaytag-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/displaytag-devel