Installation clear as mud

A patch for the README file might be useful, but in the meantime, the instructions on http://drupal.org/node/1516558 (for the API module, which also uses Grammar parser) might be helpful to you.

I just looked at the latest README file from this project.... I would suggest the attached patch for the installation section to clarify some installation details.

Nancy, I am sorry you find this unclear. To run Coder Upgrade, you need to download these projects:
- coder
- libraries (2.x)
- grammar_parser_lib

and download this "library":
- grammar_parser

Projects go in something like "sites/all/modules" and the library in "sites/all/libraries." From the modules page on your site, enable the coder_upgrade module (it does not require coder or coder_review) and that should trigger enabling its two dependent modules. Do not "enable" the grammar_parser "library" (it should not be an option if you place it in the proper directory).

All this to say, it may be time for you to begin using Drush. (What reason do you have for not?) Download the coder project, copy the coder_upgrade.make file to the "sites/all" directory, and execute "drush make --yes --no-core coder_upgrade.make" and you will have all the dependencies in their proper places.

How exactly is this so "clear as mud" compared to any other project with dependencies? You discover all of the dependencies, download them, and enable them. The "trick" here is the grammar parser is used as a library (like JS code) and, as such, placed in a libraries directory and not "enabled" as a module.

Using drush is much easier than you doing it manually. How many projects provide the convenience of a make file?

The original issue is a question about Coder Upgrade, not the parser. As such, this issue belongs in the Coder queue. Deferring a project change for the moment.

Jennifer, regarding your suggested wording, please note the use of the words "use" versus "install" in the original text. I find your changes less clear in regards to these words. In particular, you use the word "install" in two ways: use or utilize, and where to copy the files (the install part).

Good point. How's this?

Whoops. Got another patch in there with the readme patch. :)

By that reasoning, the Libraries API project "sounds like" a library and would go in sites/all/libraries, too.

Thanks for your input. What seems clear to one may indeed be muddy to another.

Changing status. Hopefully, if others get stuck in the mud, then they will find this issue (and its comments will remove the murkiness).

yup, i agree with Nancy.. parser_lib sure sounds like it would be the lib.

Wow, even after reading like 30 minutes I'm still extremely confused. First of all, I still haven't figured out the difference between grammar_parser and the grammar_parser_lib module. Do I need both of them? In the README file there are very confusing descriptions:

• "install it ... in a modules directory" - what does "install" mean here? Later it is said, that it shouldn't be enabled ("as a module", what is that, again?) So does "install" mean: copy it to the modules directory (like sites/all/modules/)?
• "download the Grammar Parser library" - ok, but from where? The module hast that same name
• "From the modules page on your site, enable this module .... Do not enable the Grammar Parser library" - ???

My conclusions are so far that, in order to use Coder Upgrade, I need to ...

• Install the Libraries API module (2.x).
• Download the project grammar_parser_lib, extract it, and place it in sites/all/modules. But do not enable the module.
• Download the project grammar_parser, extract it, place it in sites/all/libraries so that grammar_parser.module lives in sites/all/libraries/grammar_parser/grammar_parser.module.
• Install the Coder module and enable the Coder Upgrade module.

Edit: After clearing the cache, the error message on admin/config/development/coder/upgrade disappeared: "Install version 7.x-1.x of the Grammar Parser library code (from here) in a libraries directory such as "sites/all/libraries." For easy installation, use the drush make file in the Grammar Parser Library project." So I guess it works now.