Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
Besides the obvious spacing and comments (and the installation profile on the Drupal 6 version), was there anything you saw in particular that could cause problems?
I'd like to get the code up to all standards, but wanted to get out a dev release so that I could draw some testers.
Major problem was spacing. However, what is also bad is that you need to follow doxygen coding standards; also, the you should unset $help_text after you're done with it; also, the way you are hard-coding the headers is bad, you should use theme('page'... Remember to always use an indent of two space, no tabs, no trailing spaces, no spaces on blank lines. There should never be any tabs in your code. Also, after commas should be spaces. In fact, just run the coder module over your module and clean it up.
I've uploaded a new version with most of what the coder module suggests, except a couple minor items. I think the tabs would have been the most difficult thing for folks curious about the code, and they've been removed. It was using Dreamweaver as a code editor that was causing that little problem. ;)
I will keep the coding standards in mind in future updates.
Comments
Comment #1
chrisshattuck commentedI appreciate the comment, cwgordon,
Besides the obvious spacing and comments (and the installation profile on the Drupal 6 version), was there anything you saw in particular that could cause problems?
I'd like to get the code up to all standards, but wanted to get out a dev release so that I could draw some testers.
Thanks!
Chris
Comment #2
chrisshattuck commentedComment #3
cwgordon7 commentedMajor problem was spacing. However, what is also bad is that you need to follow doxygen coding standards; also, the you should unset $help_text after you're done with it; also, the way you are hard-coding the headers is bad, you should use theme('page'... Remember to always use an indent of two space, no tabs, no trailing spaces, no spaces on blank lines. There should never be any tabs in your code. Also, after commas should be spaces. In fact, just run the coder module over your module and clean it up.
Comment #4
chrisshattuck commentedThanks for the tips, cwgordon,
I've uploaded a new version with most of what the coder module suggests, except a couple minor items. I think the tabs would have been the most difficult thing for folks curious about the code, and they've been removed. It was using Dreamweaver as a code editor that was causing that little problem. ;)
I will keep the coding standards in mind in future updates.
Thanks again,
Chris
Comment #5
chrisshattuck commentedComment #6
cwgordon7 commentedOk, it's much, much better, but a couple of things still:
Spaces after comments, like such:
When concatenating strings, leave no spaces between the dot and strings, but one space between the dot and everything else. For example:
Comment #7
chrisshattuck commentedSuper Nav is now standards compliant. :)
Thanks for the ppush, cwgordon!
Chris
Comment #8
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.