Closed (won't fix)
Project:
Bartik
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 Jul 2010 at 11:19 UTC
Updated:
6 Jul 2010 at 13:27 UTC
Jump to comment: Most recent file
Comments
Comment #1
tlattimore commentedI agree, the comments should follow the standard that is documented. On it!
Comment #2
tlattimore commentedBlast it! Change the comments as requested, made a patch, than realized I hadn't check out the latest version of HEAD. Unfortunately I don't know if i'll have any other time to work on this. Un-assigning.
Comment #3
tlattimore commentedHere is a patch that makes the requested changes.
Comment #4
tlattimore commentedTagging
Comment #5
jensimmons commentedThe Drupal CSS coding standards are a draft, not a final for-sure. And most front-end developers I know do not follow them. Sadly, it seems the discussion of how to format CSS was taken over by PHP coders, and the professional CSS experts lost. I believe CSS should be formatted as CSS, not PHP. So that's why Bartik is formatted the way it is. Hopefully at some point the Drupal coding standard draft will be revisited and revised.
Comment #6
jarek foksa commentedJust like with file structure thing, using CSSDoc syntax makes a lot of sense to me because all other core modules and themes are already doing this. It's used in core not just for PHP files, but also for JavaScript and CSS.
Besides I don't think that it's very professional to type 40 dashes each time when you put a comment :P
Comment #7
jarek foksa commentedUhm... I didn't mind to change the status, I'm not deciding here what gets committed or not.
Comment #8
kevinquillen commentedI would agree with #6.
If this is going to be in the core, I would think that it shouldn't be any different from the rest of the structure/code of things in Drupal 7. Module submissions are pretty strict on following standards in the handbook.