Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
4 Dec 2013 at 21:44 UTC
Updated:
1 Feb 2014 at 21:40 UTC
Jump to comment: Most recent
Comments
Comment #1
pere orga1) You should implement hook_uninstall() and remove all variables. Otherwise they will reside in the database after uninstalling.
2) You should make the git branch 7.x as the default if it is not already, and remove the 'master' branch.
3) You should prefix all functions and Drupal variables with 'icon_tabs', without underscores. You are creating a static variable called icon_tabs, I would call it icon_tabs_something.
4) I would try to keep lines short, I tend to use ? (ternary) conditionals only on very simple things, because otherwise I find the code is more difficult to follow (compared to an 'if/else'). When concatenating strings, for example, I would not use them.
5) I would state which browsers are supported in the README and module page.
6) You can see a more detailed an automated review of your code here: http://pareview.sh/pareview/httpgitdrupalorgsandboxfredparke2116761git
In the link above there are some links to the documentation. Unless there's a good reason to not do it, you should fix all issues reported there. You can run http://pareview.sh/ as many times as you want
Comment #2
freddybushboy commentedComment #3
PA robot commentedWe are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #4
freddybushboy commentedComment #5
leon kessler commented1) In icon_tabs_preprocess_html() you are adding the icon-contextual-links.css to every page, regardless of whether the user has access to contextual links and they actually appear on the page. You should do an additional check to see whether the css is required. At the very least, it could look like this:
2) Looks as though this module used to be called fred_tabs, there are still a few references to it. E.g. icon_tabs.module line 66
3) There are still Drupal coding errors (see http://pareview.sh/pareview/httpgitdrupalorgsandboxfredparke2116761git). However, these appear to be all from font-face declarations inside of css, so there is actually nothing that could be changed.
Comment #6
leon kessler commentedComment #7
freddybushboy commentedComment #8
pere orgaLooks good to me
Comment #9
freddybushboy commentedComment #10
freddybushboy commentedComment #11
freddybushboy commentedComment #12
freddybushboy commentedComment #13
freddybushboy commentedComment #14
irodriguez commentedpareview.sh found one error -
http://pareview.sh/pareview/httpgitdrupalorgsandboxfredparke2116761git
"./font/License.txt: ASCII English text, with no line terminators"
Comment #15
freddybushboy commentedWhoops, sorry about that - I added that file recently but forgot to recheck pareview. All fixed :)
Comment #16
welly commentedpareview.sh is throwing up a bunch of new errors in your CSS files.
I've installed the module and followed the instructions and all appears to work as described. Unable to find any issues with the functionality.
Cute module - I'd be interested to see where this goes!
Comment #17
freddybushboy commentedHey there, thanks for reviewing my module!
We actually noticed those pareview errors earlier (see #5: Support(https://drupal.org/comment/8243741#comment-8243741)) and deemed them to be fine/unavoidable as they are to do with the @font-face declaration in the CSS which is necessary for the functionality of the module.
Comment #18
irodriguez commentedAfter reviewing your module let me start by saying, awesome concept, I love icon fonts, I could definitely see myself using this module further down the line.
There are some small issues I found when I installed the module:
1. There is a typos on admin/config/user-interface/icon-tabs - vertically is misspelled as "Veritally stacked tabs"
2. "Vertically stacked tabs" does not take affect when the box is checked.
Also, I have a question...
Does the "Vertically stacked tabs" checkbox have to be dependent on the "Fred tabs" option? It would be nice to be able to stack the tabs vertically on their own.
Comment #19
freddybushboy commentedHey there, yeah thanks - icon fonts are great right!
I've fixed that typo - good spotting. So with the 'vertically stacked tabs' thing, I think the problem might be in my explanation of how this works - unless it truly is broken, in that case I will look into it.
The tabs only stack vertically once the screen is wider than (arbitrarily at this stage) 1260px. This only really makes sense on themes that use a centered layout with a max width. My reasoning behind this is that when the browser width is narrower than this width you wouldn't want the tabs to stack vertically because there would not be enough space between the edge of the main content and the browser. I should probably add the option to set the width this triggers at with a variable - I will look into it.
Unfortunately I don't think it would really be possible to apply this vertical style without the 'Fred Tabs' theme - as all of the base themes tend to apply their own styles to the tabs and it would be difficult/impossible for icon tabs to guess what these are and then use CSS to put them in place. The 'Fred Tabs' theme tries its best to override any styles that would likely be applied to the tabs by the base theme so it can be more consistent with it's styling. Also the vertical tabs option make a few stylistic choices such as adding CSS3 animations to hide/show text and so on so I feel these styles are best kept in 'Fred Tabs'.
I think if you really want to use a different style but still want the vertical functionality the best thing to do might be to use the 'Fred Tabs' theme and then just override certain styles. I usually adjust the tab colors to suit my site for example.
Comment #20
irodriguez commentedI also found a small issue with the text boxes on content/hello-form#overlay=admin/config/user-interface/icon-tabs. right now they're set to a width of 60. this makes them overflow outside of their container when shrinking the width of the browser.
also i cannot seem to make the tabs vertically aligned no matter how much shrink my browser width (using Firefox 26.0)
Comment #21
freddybushboy commentedI have added the option to set the width at which the tabs stack - it works fine for me on firefox and chrome. Note that its more about expanding your browser rather than shrinking as the tabs only stack once the window is wider than this width.
I have fixed the textbox layout issue on the module configuration page.
Comment #22
irodriguez commentedon line 104 you left dpm($vertical_width) active.
also i get the following errors when trying to go to the icon tabs admin page
Comment #23
freddybushboy commentedFixed
Comment #24
irodriguez commentedall fixed up, nice going. I think you're about there, as far as I'm concerned.
Comment #25
freddybushboy commentedGreat, thanks :)
Comment #26
klausiReview of the 7.x-1.x branch:
This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. You have to get a review bonus to get a review from me.
manual review:
But otherwise looks good to me. Usually you should not RTBC your own issues, but it seems like irodriguez was about to set this anyway, so ...
Thanks for your contribution, freddybushboy!
I updated your account so you can promote this to a full project and also create new projects as either a sandbox or a "full" project.
Here are some recommended readings to help with excellent maintainership:
You can find lots more contributors chatting on IRC in #drupal-contribute. So, come hang out and stay involved!
Thanks, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
Thanks to the dedicated reviewer(s) as well.