Hello,
jQuery Custom Scrollbar is an official jQuery plugin (http://plugins.jquery.com/custom-scrollbar/), actively maintained.
I created a module with this library embed (which can still be overrided by sites/all/library/jquery-custom-scrollbar if found). As you can see on the screenshot it gives three configuration options to choose pages where the lib files are loaded, selectors for scrollable elements and predefined skins.
I followed most of Drupal coding standard but I did not passed a pareview yet. However I think the module is usable in its current state.
Thanks in advance !
---
With the module enabled, when you go to 'admin/config/user-interface/jquery-custom-scrollbar' it should be self explanatory.
---
Project page: https://drupal.org/sandbox/zenmaster/2151303
GIT Repository : git clone --branch 7.x-1.x http://git.drupal.org/sandbox/ZenMaster/2151303.git jquery_custom_scrollbar
B2F - module contributor, co-maintener of scald_flickr, ajax_chat and maintener of DBDD (Drupal Behavior Driven Development).
---
Reviews of other projects
https://drupal.org/node/2150243#comment-8295525
https://drupal.org/commenta/8487095#comment-8487095
https://drupal.org/comment/8487135#comment-8487135
| Comment | File | Size | Author |
|---|---|---|---|
| #19 | JQUERY_CUSTOM_Scrollbar_coder.png | 61.99 KB | gobinathm |
| jcs config screenshot.png | 58.21 KB | b2f |
Comments
Comment #1
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxZenMaster2151303git
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 #2
drupaldev@assyst commentedGIT repository path updated.
Comment #3
ram4nd commentedIt's a small module, I can't find anything big wrong with it.
Comment #4
b2f commentedThanks for the review ram4nd !
-) I removed the library from the module
-) gathered translatable string in one variable where needed
-) used arguments for translatable strings variables
-) fixed remaining coding standard issues with pareview.sh
-) fixed minor bugs
I updated and improved the README.txt file and project's page accordingly. I will tag the release as 7.x-1.0 stable when you will mark the project as "Reviewed & tested by the community".
Comment #5
swarad07Manual Review
Apart from this there is not much I can see wrong in the module. Once the above is rectified this can be set to RTBC.
Cheer,
Swarad
Comment #6
swarad07Comment #7
b2f commentedHello swarad07, thanks for the review.
I added and tested the .install with variable_del for each used variables. pareview.sh still good.
Comment #8
b2f commentedComment #9
ram4nd commentedComment #10
b2f commented4 new commits.
Comment #11
b2f commentedComment #12
amreana commentedOverall i like the module, seems clean and simple.
I'd move the jquery-custom-scrollbar/drupal-integration-example link from the admin page from where it is now to a new line so it's more accessible
something like:
Demo Page
Comment #13
klausiThat does not sound like an application blocker, any other issues that you found?
Comment #14
amreana commentedManual Review:
Right now the module only checks for the libraries folder
$library = libraries_get_path('jquery-custom-scrollbar');
but you could add a check for the files required by the module also for:
jquery_custom_scrollbar.js
jquery_custom_scrollbar.css
Comment #15
b2f commentedIt's been a while, I have been busy at work lately. Just fixed the last issue. Anything else ?
Comment #16
b2f commentedComment #17
b2f commentedComment #18
b2f commentedComment #19
gobinathmComment #20
gobinathmComment #21
PA robot commentedClosing due to lack of activity. Feel free to reopen if you are still working on this application (see also the project application workflow).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #22
b2f commented@amreana:
-> I moved the demo to the bottom of the config page and improved the help messages, and improved the doc. It seems even cleaner now.
@gobinathm
* pareview.sh errors are fixed (I kept the string literals warning to the possible minimum)
* Git default branch set
* README.txt corrected
* coder issue adressed
Thanks for reviews.
Comment #23
pushpinderchauhan commentedAssigning to myself for next review.
Comment #24
pushpinderchauhan commentedAutomated Review
Best practice issues identified by pareview.sh / drupalcs / coder. Yes, http://pareview.sh/pareview/httpgitdrupalorgsandboxzenmaster2151303git reported some minor issues that need to be address.
Manual Review
case JQUERY_CUSTOM_SCROLLBAR_CONFIG_PATH:, it should becase 'admin/help#jquery_custom_scrollbar':. Why this help string broken across lines, also$hvariable name not convincing here. You can keep this into a single line and simply return it.Why you defining constant variables, comment needed?
Pages (one per line)but not in case I putnode/4. Can't we implement this for both cases as other drupal modules also work in similar way. Better to to look at the function drupal_match_path which will make your implementation a little easier. It would also help to resolve my other concern :)&$pageparam, See https://api.drupal.org/api/drupal/modules%21system%21system.api.php/func....Some form elements missing default value for variable_get();, adding default value would be good something like
variable_get('jquery_custom_scrollbar_pages', ' ');The library is found in sites/all/library/jquery-custom-scrollbar, should besites/all/libraries/jquery-custom-scrollbar.drupal_set_message(check_plain($err), 'error', FALSE);, @dir, would probably be a better choice, since @ does a check_plain for you. As there is no value coming from user input, don'think there is need of check_pain().drupal_set_message(filter_xss($link), 'error', FALSE);, as there is no value coming from user input, even don't any dynamic value populating in this message.;) at line 16.The starred items (*) are fairly big issues and warrant going back to Needs Work. Items marked with a plus sign (+) are important and should be addressed before a stable project release. The rest of the comments in the code walkthrough are recommendations.
Removing review bonus tag, you can add it again if you have done another 3 reviews of other projects.
Comment #25
PA robot commentedClosing due to lack of activity. If you are still working on this application, you should fix all known problems and then set the status to "Needs review". (See also the project application workflow).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #26
spheresh commentedIt is a useful module. I think work must go on
I added a little patch fot it https://www.drupal.org/node/2398505#comment-9462109
Comment #27
klausiThe maintainer did not respond to issue raised by @er.pushpinderrana yet, so this application is closed until we hear back from the maintainer.
Comment #28
b2f commentedHey, thanks for the support spheresh. At least someone is interested for this to get out of sandbox... I'll fix these issues soon then I'll merge your mobile detect module patch in the stable release.
Comment #29
b2f commentedToday I pushed some commits to adress er.pushpinderrana's issues:
hook_help Fixed
The permission already is "administer site configuration".
I used constants to keep lines short and easier to read, it also make it a little easier to update these text if needed. Anyway, it is not a bad practice especially with the JQUERY_CUSTOM_SCROLLBAR prefix avoiding name clashes...
Done, Thanks for that is a nice improvement.
Ok
Ok
Ok
jquery_custom_scrollbar_page_build(): Using #attached is preferred over drupal_add_js(). See https://api.drupal.org/api/drupal/developer!topics!forms_api_reference.h...
The #attached attribute is not officially available for render arrays other than form, as far as I know because it's not in the doc. However there is a new hook_process_attached for Drupal 8, not 7. So I'll stick to drupal_add_js.
Ok !
Back to reviews, I'm setting this to "Reviewed & tested by the community", first because we had it in prod for almost a year now, then amreana and spheresh provided positive feedbacks and I improved it, fixed a lot of minor issues to the point where it seems ridiculous to add more, most of it wasn't an application blocker anyway I fixed it.
Thanks in advance.
Comment #30
pushpinderchauhan commentedAssigning to myself for next review, which will hopefully be tonight.
Comment #31
pushpinderchauhan commentedAutomated Review
Best practice issues identified by pareview.sh / drupalcs / coder. Yes reported some minor issues that can be false.
Review of the 7.x-1.x branch (commit df4b7aa):
Manual Review
In general, using #attached is preferred over drupal_add_js().
But that are not critical application blockers, otherwise I think this is RTBC.
Nothing major jumped out at me when I read `git diff 16c3809..`. Assigning to mpdonadio for a second look if he has time.
Comment #32
mpdonadioReview of the 7.x-1.x branch (commit 16c3809):
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
jquery_custom_scrollbar_settings(), avoid breaking translatable strings scross lines. It makes translation harder. Also elsewhere.
(+) Your JS behavior should use the context that gets passed in to make it AJAX friendly. I think you may also need a .once() on this for the same reason.
In jquery_custom_scrollbar_page_build(), drupal_get_path() is preferred to get the module path.
Avoid !placeholders unless you are *positive* they need to be unsanitized.
Not a huge fan of setting variables, and then using these as the first argument to t(). This is not a common pattern in Drupal.
Think of ways you can validate jquery_custom_scrollbar_selectors. Not sure if this will be 100% possible, though.
Not seeing any blocking issues.
Comment #33
mpdonadioThanks for your contribution, B2F!
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.
Comment #34
b2f commentedThanks ! Happy new year 2015 to all following this thread.