Slidedeck Module enables you to increase the user experience by giving you the jquery slide effect. This module wrappes the jquery slidedeck plugin within. Thus it provides admin interface to add more slidedeck widgets and for each slidedeck we can choose set of blocks as slide deck content.
It also provides an option to choose the skin for the widgets.
Installation:
1. Copy the slidedeck module directory to your modules directory
2. Enable module thorugh modules admin interface (admin/modules).
Usage:
1. Create new slidedeck widget block through Admin > Structure > Slidedeck > Add Slidedeck
2. On the add slidedeck form, give title and choose the slidedeck skin.
3. The slidedeck contents are blocks, add what blocks you need to include as a slidedeck content.
4. If you don't find the block you require, add block and select here.
5. Once slidedeck is created, it will create a block.
6. Visit Admin > Structure > Blocks and add your slidedeck block to the region you wish.
Custom Slidedeck Skins:
This module is shipped with 3 different skins for slide deck. If you want to have new look for your slidedeck, you can add your own skin by following below steps.
1. Create your custom skin css file by copying the skin css files from this module at path skins folder.
2. This module provides a hook called hook_slidedeck_skin_alter. Implement this hook as below
hook_slidedeck_skin_alter(&$skins) {
$skins['skin_key'] = array(
'path' => drupal_get_path('theme', 'your_theme') . '/slidedeck_cust_skin.css', // this is the skin file path
'value' => 'Blue and Black 700px'), // This is the label which will appear on the add slidedeck form
);
}
3. Choose your custom skin for the slidedeck and save.
Git Repository: git clone --branch 7.x-1.x gopagoninarsing@git.drupal.org:sandbox/gopagoninarsing/1316868.git slidedeck
Project: http://drupal.org/sandbox/gopagoninarsing/1316868
Version: Drupal 7
| Comment | File | Size | Author |
|---|---|---|---|
| #19 | drupalcs-result.txt | 1.3 KB | klausi |
| #14 | drupalcs-result.txt | 5.84 KB | klausi |
| #3 | slidedeck-1319760-3.patch | 614 bytes | dineshcooper |
Comments
Comment #1
dineshcooper commentedI looked through the module
- In the info file you can drop the line - ; $Id$
That was necessary for CVS, but is no longer needed for Git.
I ran the module through Coder and that comes out clean.
I installed the module and found the following:
- The message after installing shows html code and some arbitrary link text
<a href="/drupal7/admin/structure/slidedeck">Structure > Simple Tweet</a>- After saving a new slidedeck I get the error message
Deprecated function: Function eregi() is deprecated in slidedeck_validate() (line 243 of modules\slidedeck\slidedeck.module)
(I am running PHP5.3.5 - eregi() is deprecated as of PHP 5.3.0)
- When viewing the slidedeck, it is there and seems to function fine but the following error messages show up
Strict warning: Only variables should be passed by reference in slidedeck_block_content() (line 104 of modules\slidedeck\slidedeck.module).
Strict warning: Creating default object from empty value in slidedeck_block_content() (line 115 of modules\slidedeck\slidedeck.module).
Strict warning: Creating default object from empty value in slidedeck_block_content() (line 115 of modules\slidedeck\slidedeck.module).
Set this back to "needs review" once you have made the changes and I will test again.
Comment #2
gopagoninarsing commentedHi,
Thanks for the review.Fixed all the mentioned changes and pushed to sandbox.
Thanks,
gopagoninarsing.
Comment #3
dineshcooper commentedYou get a PHP Strict standards warning on line 117 of slidedeck.module - I have attached a patch file to solve that issue.
Other than that looks good to me, coder review still comes up clean.
Comment #4
klausiIt appears you are working in the "master" branch in git. You should really be working in a version specific branch. The most direct documentation on this is Moving from a master branch to a version branch. For additional resources please see the documentation about release naming conventions and creating a branch in git.
Review of the master branch:
This automated report was generated with PAReview.sh, your friendly project application review script. Please report any bugs to klausi.
manual review:
Comment #5
gopagoninarsing commentedHi
Thanks for the patch.Applied and its working fine.
Thanks,
gopagoninarsing.
Comment #6
gopagoninarsing commentedHi,
Thanks for the review.All mentioned review points are completed.
Thanks,
gopagoninarsing.
Comment #7
klausiReview of the 7.x-1.x branch:
This automated report was generated with PAReview.sh, your friendly project application review script. Please report any bugs to klausi.
manual review:
Comment #8
gopagoninarsing commentedHi,
One again thanks for the review.All the reviews points given are completed and pushed to 7.x-1.x branch.
Thanks,
gopagoninarsing.
Comment #9
klausiReview of the 7.x-1.x branch:
This automated report was generated with PAReview.sh, your friendly project application review script. Please report any bugs to klausi.
manual review:
Comment #10
gopagoninarsing commentedHi,
Thanks for the review.Worked on the mentioned review points and pushed to 7.x-1.x branch.
Thanks,
gopagoninarsing.
Comment #10.0
elc commentedMistakenly mentioned it as drupal 6 it is for drupal 7.
Comment #11
elc commentedThere's no chance of user input in this to have a need to filter_xss .. it should simply be calling the url() function.
but can be broken up (and some of the lines compacted strung together) to give something like this, which break things up into logical units and makes it a tad easier to read. No point storing values you don't ever use either.
This is also much like the hook_schema stuff. It's not really needed, but it does make reading the code and maintaining the code in the long run a much simpler task. Do you remember how code you wrote a few years ago works when you look at it now?
slidedeck_block_content and slidedeck_block_view functions look like they should be combined. There's no logic in block_view, just some statements and then it calls the other function.
You also theme the output of the block before returning it - simply return a render array with the #theme set so that other modules can manipulate the contents of the block before it is rendered.
Just also spotted that you're forcing the "lite" version. You should also perhaps check for the non-lite version if the lite one is missing? Is that even practical?
Comment #11.0
elc commentedchanged the branch command
Comment #12
gopagoninarsing commentedHi
Added all review changes mentioned.
When we download the free version of slidedeck plugin from http://www.slidedeck.com it giving us only the lite version.
As we are using Emacs and it provides newline (\n) at the end of each line by default.So please provide the file for which issue is coming.
Thanks,
gopagoninarsing.
Comment #13
gopagoninarsing commentedChanging Priority.
Comment #14
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. Go and review some other project applications, so we can get back to yours sooner.
manual review:
Comment #15
gopagoninarsing commentedHi,
Thanks klausi for the review. Fixed all mentioned review changes and updated.
Thanks,
gopagoninarsing.
Comment #16
elc commentedLooks great and pretty much ready for RTBC. There is one blocker though which is the file permissions of the files in the git repository. Not all the files are +x any more, but most of them still are.
The non-blockers are just coding suggestions. The descriptions on the schema is part of the Coding Standards though.
blockers
non-blockers
Again, looks good.
Comment #17
gopagoninarsing commentedHi ELC,
Thanks for the review.Changed the file permissions and mentioned non-blockers changes and updated.
Thanks,
gopagoninarsing.
Comment #18
elc commentedLooks good enough to eat off.
Your git commit messages and git identity need a bit of help in the future - Please refer to Commit messages - providing history and credit about giving yourself some credit and properly formatting commit messages.
Comment #19
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. Go and review some other project applications, so we can get back to yours sooner.
manual review:
But that are just minor issues, so ...
Thanks for your contribution, gopagoninarsing! Welcome to the community of project contributors on drupal.org.
I've granted you the git vetted user role which will let you promote this to a full project and also create new projects as either sandbox or "full" projects depending on which you feel is best.
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.
As you continue to work on your module, keep in mind: Commit messages - providing history and credit and Release naming conventions.
Comment #20.0
(not verified) commentedadded code tag