Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
26 Sep 2014 at 14:36 UTC
Updated:
6 Mar 2015 at 09:14 UTC
Jump to comment: Most recent
Comments
Comment #1
Collins405 commentedComment #2
Collins405 commentedComment #3
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxchriscollins405234545...
We 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
Collins405 commentedFixed all automated formatting errors. Filed for re-review.
Comment #5
gaurav.pahuja commentedFixing GIT clone command.
Comment #6
gaurav.pahuja commentedCan you please let me know the major differences between your module and Responsive Tables?
https://www.drupal.org/project/responsive_tables
Comment #7
Collins405 commentedThe Responsive Tables module works by choosing a priority for columns, and then as the screen size is reduced, the columns with less priority are actually hidden, which isn't great, as you are actually hiding content from your mobile users.
With this module the first column is "pinned" to the left of the table, and all other columns are available in a scrollable table.
This means you never have to hide any information for mobile/tablet users.
A similar module is foo table , which handles responsive tables in a completely different way again.
I believe that either foo table, or the zurb libraries i have used are much better ways of handling responsive tables, rather than the responsive tables module.
Comment #8
Collins405 commentedComment #9
klausiPlease add the differences to the existing module to the project page, so that people can make an educted decision which module to use. See also https://www.drupal.org/node/997024
Comment #10
Collins405 commented@klausi Thanks, module page updated with similar modules, longer description, and project image.
Comment #11
darol100 commented@Collins405,
I ran some testing on your module using the coder module and I got this error.
Please add a comment block in you responsive-tables.js with some useful information and this should be solve.
Comment #12
darol100 commentedComment #13
Collins405 commentedThanks, have added @file doc to js files, and set to needs review again.
Comment #14
darol100 commentedSince you added a new block comments now you got this error.
FILE: /var/www/drupal-7-pareview/pareview_temp/js/responsive-tables.js
--------------------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
--------------------------------------------------------------------------------
5 | ERROR | There must be exactly one blank line after the file comment
--------------------------------------------------------------------------------
http://pareview.sh/pareview/httpgitdrupalorgsandboxchriscollins405234545...
Please correct this error.
Comment #15
Collins405 commentedAh of course, thanks mate. All sorted now
Comment #16
Collins405 commentedComment #17
darol100 commented@ChrisCollins405
IMHO, Please don't RTBC your own issues, see the workflow: https://www.drupal.org/node/532400.
I will revise it tonight and if everything is good I will change it back to RTBC.
Comment #18
darol100 commented@ChrisCollins405
According to Coder... You still have this error....
However, you have in your code the Block comment.
I did not see any other errors. So I will change it to RTBC.
Thank you for your contribution
Comment #19
kscheirerThis module certainly is very easy to use, and we're happy to promote it by itself, but we cannot grant "git vetted user" status for such a short module.
Comment #20
klausiOk let's do so - I don't think we need a maintainer response for that?
Comment #21
kscheirerThanks for your contribution, Collins405!
I promoted this to a full project, https://www.drupal.org/project/zurb_responsive_tables
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.
Comment #22
Collins405 commentedThanks guys. I certainly have plans to increase the amount of code in this module to add a config page to target specific tables. Will I need to resubmit the project for review once it has more than 120 lines/5 functions?