The enclosed patch includes codestyle improvements for all children modules of Panels.
Inspired by the coder module, these mostly concern the documentation standards (such as missing periods or a missing @file block).
However, I did not change the string concatenation format as this standard has changed anyway and we don't want to change it forth and back.
Also I consistently split out '

' and '

' from t()-calls, where this was not yet done.
In panels_view.module the comments inconsistently referred to either 'panel view' or 'view pane'. I consistently changed this to the latter as we anyway want to move there. Accordingly I changed some occurrences of 'panel mini' to 'mini panel'.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Pancho’s picture

Oops, should have commented that out... I meant < p > and < /p >.

sdboyer’s picture

Great...but...could you reroll the patch? Sorry, too many commits...

Pancho’s picture

FileSize
32.06 KB

Sure, here we go...

Btw: Rerolled this patch from within the panels project. Usually, patches made from a too high level are no problem, with the Eclipse option "Ignore leading path name segments", but if this is better, I'll always try to do it this way...

sun’s picture

Status: Needs review » Reviewed & tested by the community
FileSize
35.78 KB

Fixed switch statements and string concatenations in implementations of hook_help().
Other than that, looks good!

Pancho’s picture

Ooops, thanks for fixing this... :)

sun’s picture

Advanced code clean-up using coder_format, and extensive review of all fixes.

I will probably have no time to re-roll this patch, so either commit it now, or leave it ugly.

@sdboyer: I think you want to apply the patch this time... ;) (missing fixes in panels_views.install are included)

sdboyer’s picture

dear.freakin.god.lol.

Yeah, applying the patch will definitely be preferable here. I didn't even notice the spacing issue when I manually rewrote panels_views.install...was too embarrassed about all the little bugs in beta4 to pay close attention, I think :)

sun’s picture

Assigned: Pancho » sun
FileSize
219.11 KB

Please note that patch in #6 probably breaks all existing patches in the queue. However, having a consistent coding-style that adheres to Drupal's Coding Standards is the key for fast and community-driven development.

Re-rolled, since #262956: Fatal error for mini panels layout settings has been committed.

sdboyer’s picture

Status: Reviewed & tested by the community » Fixed

OK, with very few exceptions, this patch has been APPLIED ;) and committed.

I totally didn't know that putting single-line comments alone on the line before the code they refer to is a drupal coding standard...

sdboyer’s picture

Note - I worked from the one in #6, no worries; I accounted for the differences as needed.

sun’s picture

Re: #9 inline comments: There is no coding standard for them yet. It depends on the context whether they are clean. I thought I left most inline comments as they were, but there were some cases where a full sentence followed an already long line of code. See related discussion.

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.