Sha256: 47c9c30d98d16a1f604a75db416f2117b5f5e098ed4436282fa8f5d169152c61
Contents?: true
Size: 1.6 KB
Versions: 22
Compression:
Stored size: 1.6 KB
Contents
How to create an Application Generator ====================================== 1. Create a new RubyGem (using newgem or hoe) or you can use an existing one. 2. Run the generator: script/generate application_generator foobar 3. Using the generated test class, assert what directories, files, classes etc should be generated. 4. Add these files into the app_genearators/foobar/templates folder. Your files can use ERb (that is, <%= ... %>). 5. Specify who the files in /templates are copied/templated at generation time within app_generators/foobar/foobar_generators.rb 's #manifest method. Use m.file for files to copy over. Use m.template for files containing ERb. Create attr_reader accessors for any variables your templates need access to. 6. Run unit tests. 7. If your application generator uses other generators (m.dependency "gen-name", [arg1, arg2], :option1 => 'value') then you must add this into the generated bin/foobar file. For example, if you wanted to use a rubygems and/or merb generator, then replace the use_application_sources! call in bin/foobar: RubiGen::Base.use_application_sources! :rubygems, :merb Without this, RubiGen will not be able to find your dependent generators. 8. Update your Manifest.txt with the new files (if you are using Hoe; using newgem? it uses Hoe; so you need to do this) 9. Build and install your RubyGem locally. Run: rake install_gem 10. Test your foobar application to ensure that it connects to the generator correctly and generates files. 11. Done. You will see this message again after running the generator and by using the -h/--help option.
Version data entries
22 entries across 22 versions & 2 rubygems
Version | Path |
---|---|
rubigen-1.3.4 | rubygems_generators/application_generator/USAGE |
rubigen-1.4.0 | rubygems_generators/application_generator/USAGE |